[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <60e388df-cd03-3e88-e9c5-460ebdde29c5@linaro.org>
Date: Thu, 22 Dec 2022 11:44:13 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Srinivasa Rao Mandadapu <quic_srivasam@...cinc.com>,
swboyd@...omium.org, agross@...nel.org, andersson@...nel.org,
robh+dt@...nel.org, broonie@...nel.org, quic_plai@...cinc.com,
krzysztof.kozlowski+dt@...aro.org, konrad.dybcio@...ainline.org,
mturquette@...libre.com, sboyd@...nel.org,
linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, quic_rohkumar@...cinc.com
Subject: Re: [PATCH 2/2] clk: qcom: lpasscc: Add resets for SC7280 audioreach
clock controller
On 21/12/2022 14:18, Srinivasa Rao Mandadapu wrote:
>
> On 12/21/2022 4:09 PM, Krzysztof Kozlowski wrote:
> Thanks for your time Krzysztof!!!
>> On 21/12/2022 11:21, Srinivasa Rao Mandadapu wrote:
>>> The clock gating control for TX/RX/WSA core bus clocks would be required
>>> to be reset(moved from hardware control) from audio core driver. Thus
>>> add the support for the reset clocks in audioreach based clock driver.
>>>
>>> Signed-off-by: Srinivasa Rao Mandadapu <quic_srivasam@...cinc.com>
>>> ---
>>> drivers/clk/qcom/lpasscc-sc7280.c | 18 ++++++++++++++++++
>>> 1 file changed, 18 insertions(+)
>>>
>>> diff --git a/drivers/clk/qcom/lpasscc-sc7280.c b/drivers/clk/qcom/lpasscc-sc7280.c
>>> index 5c1e17b..d81d81b 100644
>>> --- a/drivers/clk/qcom/lpasscc-sc7280.c
>>> +++ b/drivers/clk/qcom/lpasscc-sc7280.c
>>> @@ -12,10 +12,12 @@
>>> #include <linux/regmap.h>
>>>
>>> #include <dt-bindings/clock/qcom,lpass-sc7280.h>
>>> +#include <dt-bindings/clock/qcom,lpassaudiocc-sc7280.h>
>> These are bindings for different device.
>
> They are not exactly for different device. It's for same device with
> ADSP enabled platforms.
>
> Basically lpassaudiocc-sc7280.c and lpasscorecc-sc7280.c are for legacy
> path.
>
> lpasscc-sc7280.c is for ADSP based AudioReach Solution.
I see two different devices:
lpasscc@...0000
clock-controller@...0000
clock inputs and outputs are different, so it does not look like for
same device.
Best regards,
Krzysztof
Powered by blists - more mailing lists