From: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Srinivas Kandagatla <srini@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Rao Mandadapu <quic_srivasam@quicinc.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH v1 2/2] soundwire: qcom: add EE-aware register layout and cpu selection
Date: Mon, 15 Jun 2026 18:35:16 +0530 [thread overview]
Message-ID: <a94a6676-8ae9-43ea-a4c2-7e3de92b20e7@oss.qualcomm.com> (raw)
In-Reply-To: <0030e12e-96b7-4a22-a3b4-1b42bd32f39e@kernel.org>
On 6/9/2026 1:18 AM, Krzysztof Kozlowski wrote:
> On 08/06/2026 19:53, Mohammad Rafi Shaik wrote:
>> Some Qualcomm SoundWire masters expose interrupt, FIFO and status
>> registers in EE-specific register windows on v2.0 and newer hardware.
>>
>> Add support for selecting the SoundWire execution environment from DT
>> and use it to program the correct register window for the active EE.
>> The driver now reads the EE value from the new
>
> No, it does not. "now" means before the commit, you are making the
> changes - see submitting patches.
>
Sorry for the confusion. I will update the commit description properly
in the next revision.
>> qcom,swr-master-ee-val property, with qcom,ee as a fallback for
>> backward compatibility.
>
> And where did you document qcom,ee and why do you need fallback in the
> first place? For downstream DTS? We do not support anything from
> downstream here.
Regarding the qcom,swr-master-ee-val property and the mention of qcom,ee
as a fallback: that was a mistake in the description. There is no
fallback being added, so it is not appropriate to mention it here. I
will correct this in the next version.
Thanks & regards
Rafi.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2026-06-15 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 17:53 [PATCH v1 0/2] soundwire: qcom: add support for EE-aware register layout Mohammad Rafi Shaik
2026-06-08 17:53 ` [PATCH v1 1/2] dt-bindings: soundwire: qcom: add qcom,swr-master-ee-val property Mohammad Rafi Shaik
2026-06-08 19:46 ` Krzysztof Kozlowski
2026-06-15 12:37 ` Mohammad Rafi Shaik
2026-06-09 8:17 ` Srinivas Kandagatla
2026-06-15 12:44 ` Mohammad Rafi Shaik
2026-06-08 17:53 ` [PATCH v1 2/2] soundwire: qcom: add EE-aware register layout and cpu selection Mohammad Rafi Shaik
2026-06-08 19:48 ` Krzysztof Kozlowski
2026-06-15 13:05 ` Mohammad Rafi Shaik [this message]
2026-06-09 8:53 ` Srinivas Kandagatla
2026-06-29 4:33 ` Mohammad Rafi Shaik
2026-06-09 8:17 ` [PATCH v1 0/2] soundwire: qcom: add support for EE-aware register layout Konrad Dybcio
2026-06-29 4:36 ` Mohammad Rafi Shaik
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=a94a6676-8ae9-43ea-a4c2-7e3de92b20e7@oss.qualcomm.com \
--to=mohammad.rafi.shaik@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.dev \
--cc=quic_srivasam@quicinc.com \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
--cc=vkoul@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
all inboxes | Powered by JetHome®