Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Prasad Kumpatla <quic_pkumpatl@quicinc.com>
To: Luca Weiss <luca.weiss@fairphone.com>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: <cros-qcom-dts-watchers@chromium.org>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <kernel@oss.qualcomm.com>,
	Mohammad Rafi Shaik <quic_mohs@quicinc.com>
Subject: Re: [PATCH v1 3/8] arm64: dts: qcom: qcs6490-rb3gen2: Modify WSA and VA macro clock nodes for audioreach solution
Date: Tue, 22 Apr 2025 22:29:19 +0530	[thread overview]
Message-ID: <04b7212c-d048-46d2-b5d4-e929cfc17f63@quicinc.com> (raw)
In-Reply-To: <D8XO1JU37NEV.YN595H7NEOU7@fairphone.com>



On 4/4/2025 12:42 PM, Luca Weiss wrote:
> Hi Konrad,
> 
> On Tue Apr 1, 2025 at 6:05 PM CEST, Konrad Dybcio wrote:
>> On 3/17/25 6:41 AM, Prasad Kumpatla wrote:
>>> From: Mohammad Rafi Shaik <quic_mohs@quicinc.com>
>>>
>>> Modify and enable WSA, VA and lpass_tlmm clock properties.
>>> For audioreach solution mclk, npl and fsgen clocks
>>> are enabled through the q6prm clock driver.
>>>
>>> Signed-off-by: Mohammad Rafi Shaik <quic_mohs@quicinc.com>
>>> Co-developed-by: Prasad Kumpatla <quic_pkumpatl@quicinc.com>
>>> Signed-off-by: Prasad Kumpatla <quic_pkumpatl@quicinc.com>
>>> ---
>>
>> Instead, put the inverse changes in sc7280-chrome-common.dtsi please
> 
> How are we going to handle other sc7280-based platforms, such as my
> QCM6490 Fairphone 5 needing to use q6afecc instead of q6prmcc which gets
> used in this patchset?
> 
> One solution might be to put q6afecc into the base sc7280.dtsi file,
> then we have a sc7280-audioreach.dtsi which overwrites q6afecc with
> q6prmcc which then gets included by boards using audioreach.
> 
> I also don't think we can split this across sc7280 vs qcm6490 vs sm7325,
> there seems to be any combination possible on any of these SoCs -
> depending on the firmware shipped with it.
> 
> So somewhat similar to the current sc7280-chrome-common.dtsi but just
> for audioreach.
> 
> Regards
> Luca
ACK, We will handle in next patchset version by creating a new 
qcs6490-audioreach.dtsi file.

Thanks,
Prasad>
>>
>> Konrad
> 


  reply	other threads:[~2025-04-22 16:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17  5:41 [PATCH v1 0/8] Enable audio on qcs6490-RB3Gen2 and qcm6490-idp boards Prasad Kumpatla
2025-03-17  5:41 ` [PATCH v1 1/8] arm64: dts: qcom: sc7280: Add gpr node Prasad Kumpatla
2025-03-26 22:51   ` Bryan O'Donoghue
2025-04-22 16:19     ` Prasad Kumpatla
2025-03-17  5:41 ` [PATCH v1 2/8] arm64: dts: qcom: sc7280: Add WSA SoundWire and LPASS support Prasad Kumpatla
2025-03-26 23:02   ` Bryan O'Donoghue
2025-04-22 16:22     ` Prasad Kumpatla
2025-03-27 14:12   ` Dmitry Baryshkov
2025-04-22 16:24     ` Prasad Kumpatla
2025-03-17  5:41 ` [PATCH v1 3/8] arm64: dts: qcom: qcs6490-rb3gen2: Modify WSA and VA macro clock nodes for audioreach solution Prasad Kumpatla
2025-04-01 16:05   ` Konrad Dybcio
2025-04-04  7:12     ` Luca Weiss
2025-04-22 16:59       ` Prasad Kumpatla [this message]
2025-03-17  5:41 ` [PATCH v1 4/8] arm64: dts: qcom: qcs6490-rb3gen2: add WSA8830 speakers amplifier Prasad Kumpatla
2025-03-26 17:28   ` Jorge Ramirez
2025-04-22 17:08     ` Prasad Kumpatla
2025-03-17  5:41 ` [PATCH v1 5/8] arm64: dts: qcom: qcs6490-rb3gen2: Add sound card Prasad Kumpatla
2025-04-01 21:32   ` Konrad Dybcio
2025-04-22 17:19     ` Prasad Kumpatla
2025-03-17  5:41 ` [PATCH v1 6/8] arm64: dts: qcom: qcm6490-idp: Modify WSA/VA/RX/TX macro clock nodes for audioreach solution Prasad Kumpatla
2025-03-17  5:41 ` [PATCH v1 7/8] arm64: dts: qcom: qcm6490-idp: Add WSA8830 speakers amplifier and WCD9370 headset codec Prasad Kumpatla
2025-03-17  5:41 ` [PATCH v1 8/8] arm64: dts: qcom: qcm6490-idp: Add sound card Prasad Kumpatla
2025-03-26 23:12   ` Bryan O'Donoghue
2025-04-22 17:21     ` Prasad Kumpatla

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=04b7212c-d048-46d2-b5d4-e929cfc17f63@quicinc.com \
    --to=quic_pkumpatl@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=cros-qcom-dts-watchers@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.weiss@fairphone.com \
    --cc=quic_mohs@quicinc.com \
    --cc=robh@kernel.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