[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dce0f577-b08e-4eed-8457-9ea5fefbd8c9@quicinc.com>
Date: Tue, 2 Jan 2024 18:01:59 +0800
From: "Aiqun Yu (Maria)" <quic_aiquny@...cinc.com>
To: Konrad Dybcio <konrad.dybcio@...aro.org>,
Krzysztof Kozlowski
<krzysztof.kozlowski@...aro.org>,
Andy Gross <agross@...nel.org>,
"Bjorn
Andersson" <andersson@...nel.org>,
Mathieu Poirier
<mathieu.poirier@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
"Krzysztof
Kozlowski" <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley
<conor+dt@...nel.org>,
Manivannan Sadhasivam <mani@...nel.org>,
Sibi Sankar
<quic_sibis@...cinc.com>, Will Deacon <will@...nel.org>,
Robin Murphy
<robin.murphy@....com>, Joerg Roedel <joro@...tes.org>,
Greg Kroah-Hartman
<gregkh@...uxfoundation.org>,
Wesley Cheng <quic_wcheng@...cinc.com>
CC: Marijn Suijten <marijn.suijten@...ainline.org>,
Alexey Minnekhanov
<alexeymin@...tmarketos.org>,
<linux-arm-msm@...r.kernel.org>, <linux-remoteproc@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <iommu@...ts.linux.dev>,
<linux-usb@...r.kernel.org>
Subject: Re: [PATCH v2 01/14] arm64: dts: qcom: msm8916: Drop RPM bus clocks
On 9/13/2023 7:14 PM, Konrad Dybcio wrote:
> On 13.09.2023 13:14, Krzysztof Kozlowski wrote:
>> On 13/09/2023 12:48, Konrad Dybcio wrote:
>>> On 13.09.2023 10:53, Krzysztof Kozlowski wrote:
>>>> On 13/09/2023 10:47, Konrad Dybcio wrote:
>>>>> On 13.09.2023 09:07, Krzysztof Kozlowski wrote:
>>>>>> On 12/09/2023 15:31, Konrad Dybcio wrote:
>>>>>>> These clocks are now handled from within the icc framework and are
>>>>>>
>>>>>> That's a driver behavior, not hardware.
>>>>> I believe we've been over this already..
>>>>>
>>>>> The rationale behind this change is: that hardware, which falls
>>>>> under the "interconnect" class, was previously misrepresented as
>>>>> a bunch of clocks. There are clocks underneath, but accessing them
>>>>> directly would be equivalent to e.g. circumventing the PHY subsystem
>>>>> and initializing your UFS PHY from within the UFS device.
>>>>
>>>> And every time one write such commit msg, how should we remember there
>>>> is some exception and actually it is about clock representation not CCF
>>>> or ICC framework.
>>> So is your reply essentially "fine, but please make it clear in
>>> each commit message"?
>>
>> I am fine with this change. If commit msg had such statement, I would
>> not have doubts :/
> Ok, I'll resend, thanks for confirming!
Is there any one continue working on this?
The bindings already merged while the dtb is not consistent with current
binding files. So dt bindings checks are failed actually.
>
> Konrad
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Thx and BRs,
Aiqun(Maria) Yu
Powered by blists - more mailing lists