From: Vinod Koul <vkoul@kernel.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Srinivas Kandagatla <srini@kernel.org>,
Rao Mandadapu <quic_srivasam@quicinc.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH v2 0/2] soundwire: qcom: Add Shikra soundwire support
Date: Sat, 03 Oct 2026 10:21:24 +0200 [thread overview]
Message-ID: <179101568482.158974.17009994282078059427.b4-ty@kernel.org> (raw)
In-Reply-To: <20260910-shikra_soundwire_support-v2-0-f98c9a6ea1e1@oss.qualcomm.com>
On Thu, 10 Sep 2026 11:50:13 +0530, Mohammad Rafi Shaik wrote:
> This series adds support for the Shikra SoundWire controller.
>
> Unlike existing Qualcomm platforms, Shikra assigns the SoundWire master
> controller to EE0 instead of EE1. On SoundWire v2.0 and later hardware,
> FIFO, and status registers are banked per Execution Environment (EE),
> making the register layout dependent on the EE assignment.
>
> [...]
Applied, thanks!
[1/2] dt-bindings: soundwire: qcom: add qcom,shikra-soundwire compatible
commit: a936b634dd62a414a3da6517fac11f02117ffd7e
[2/2] soundwire: qcom: add EE-aware register layout for Shikra
commit: b27be5a85ed3c11b51de189218d7a78b0972af4d
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-10-03 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 6:20 [PATCH v2 0/2] soundwire: qcom: Add Shikra soundwire support Mohammad Rafi Shaik
2026-09-10 6:20 ` [PATCH v2 1/2] dt-bindings: soundwire: qcom: add qcom,shikra-soundwire compatible Mohammad Rafi Shaik
2026-09-11 8:36 ` Krzysztof Kozlowski
2026-09-10 6:20 ` [PATCH v2 2/2] soundwire: qcom: add EE-aware register layout for Shikra Mohammad Rafi Shaik
2026-09-10 6:34 ` sashiko-bot
2026-10-03 8:21 ` Vinod Koul [this message]
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=179101568482.158974.17009994282078059427.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mohammad.rafi.shaik@oss.qualcomm.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=quic_srivasam@quicinc.com \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
--cc=yung-chuan.liao@linux.intel.com \
/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