From: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
To: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>,
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 1/2] dt-bindings: soundwire: qcom: add qcom,swr-master-ee-val property
Date: Mon, 15 Jun 2026 18:14:33 +0530 [thread overview]
Message-ID: <40d9d0d9-978d-426c-b463-c05faae1fad5@oss.qualcomm.com> (raw)
In-Reply-To: <7bcddc82-f46f-4366-a4cb-453a213f8bd4@oss.qualcomm.com>
On 6/9/2026 1:47 PM, Srinivas Kandagatla wrote:
>
>
> On 6/8/26 6:53 PM, Mohammad Rafi Shaik wrote:
>> Add documentation for the qcom,swr-master-ee-val Device Tree property
>> used by Qualcomm SoundWire masters to describe the execution-environment
>> value for interrupt routing.
>>
>> This property allows platform DTs to specify the EE value used to direct
>
> this sounds wrong, this should never be platform specific, this is SoC
> specific.
>
Agreed, this is SoC-specific and should not be described as
platform-specific. I will update the description accordingly.
>> SoundWire master interrupts to the appropriate CPU target.
>
> Why should this come from DT, driver should be able to make a choice
> based on SoC compatible string.
>
Currently, the driver uses a version-specific compatible string rather
than a SoC-specific one, so it cannot reliably infer this information.
That is why the configuration is being provided through DT.
This is a hardware requirement specific to the Shikra SoC. The DT entry
was added to retrieve the EE value required for this configuration.
Thanks & Regards,
Rafi.
>
>
> --srini
>
>
>>
>> Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
>> ---
>> .../devicetree/bindings/soundwire/qcom,soundwire.yaml | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml b/Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml
>> index 9447a2f37..5b06cc1a5 100644
>> --- a/Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml
>> +++ b/Documentation/devicetree/bindings/soundwire/qcom,soundwire.yaml
>> @@ -215,6 +215,12 @@ properties:
>> maximum: 4
>> - const: 0xff
>>
>> + qcom,swr-master-ee-val:
>> + $ref: /schemas/types.yaml#/definitions/uint8-array
>> + description:
>> + Execution-environment value used to route SoundWire master
>> + interrupts to CPU0 or CPU1.
>> +
>> label:
>> maxItems: 1
>>
>
next prev parent reply other threads:[~2026-06-15 12:44 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 [this message]
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
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=40d9d0d9-978d-426c-b463-c05faae1fad5@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=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=srinivas.kandagatla@oss.qualcomm.com \
--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®