From: Vinod Koul <vkoul@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL]: Soundwire subsystem updates for v6.8-rc1
Date: Thu, 18 Jan 2024 22:26:46 +0530 [thread overview]
Message-ID: <ZalYTgul-JeuE9sX@matsya> (raw)
[-- Attachment #1: Type: text/plain, Size: 2492 bytes --]
Heya Linus,
Hope your network gets restored soon. Here is the pull request for
Soundwire subsystem. Please pull to recieve one core update and couple of
qcom driver updates.
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-6.8-rc1
for you to fetch changes up to becfce5233a78956654f36555f1b9187f8d11d56:
soundwire: amd: drop bus freq calculation and set 'max_clk_freq' (2023-12-18 18:02:10 +0530)
----------------------------------------------------------------
soundwire updates for 6.7
- Core: add concept of controller_id to deal with clear Controller/Manager
hierarchy
- bunch of qcom driver refactoring for qcom_swrm_stream_alloc_ports(),
qcom_swrm_stream_alloc_ports() and setting controller id to hw master id
----------------------------------------------------------------
Bard Liao (1):
soundwire: generic_bandwidth_allocation use bus->params.max_dr_freq
Krzysztof Kozlowski (4):
soundwire: qcom: drop unneeded qcom_swrm_stream_alloc_ports() cleanup
soundwire: qcom: move sconfig in qcom_swrm_stream_alloc_ports() out of critical section
soundwire: stream: constify sdw_port_config when adding devices
soundwire: fix initializing sysfs for same devices on different buses
Pierre-Louis Bossart (1):
soundwire: bus: introduce controller_id
Srinivas Kandagatla (1):
soundwire: qcom: set controller id to hw master id
Vinod Koul (1):
soundwire: amd: drop bus freq calculation and set 'max_clk_freq'
drivers/soundwire/amd_manager.c | 12 ++++++--
drivers/soundwire/bus.c | 4 +++
drivers/soundwire/debugfs.c | 2 +-
drivers/soundwire/generic_bandwidth_allocation.c | 8 ++---
drivers/soundwire/intel_auxdevice.c | 3 ++
drivers/soundwire/master.c | 2 +-
drivers/soundwire/qcom.c | 39 +++++++++++++-----------
drivers/soundwire/slave.c | 12 ++++----
drivers/soundwire/stream.c | 10 +++---
include/linux/soundwire/sdw.h | 10 +++---
sound/soc/intel/boards/sof_sdw.c | 4 +--
11 files changed, 62 insertions(+), 44 deletions(-)
Thanks
--
~Vinod
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2024-01-18 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 16:56 Vinod Koul [this message]
2024-01-19 1:24 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZalYTgul-JeuE9sX@matsya \
--to=vkoul@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®