[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8c1428a6-f268-cb03-3e55-887d30236924@linaro.org>
Date: Mon, 24 Oct 2022 12:46:41 -0400
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Vinod Koul <vkoul@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Stephen Boyd <sboyd@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, Andy Gross <agross@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 10/13] arm64: dts: qcom: sm8450: add spmi node
On 24/10/2022 12:45, Dmitry Baryshkov wrote:
> On 24/10/2022 17:56, Krzysztof Kozlowski wrote:
>> On 09/12/2021 05:35, Vinod Koul wrote:
>>> Add the spmi bus as found in the SM8450 SoC
>>>
>>> Signed-off-by: Vinod Koul <vkoul@...nel.org>
>>> Reviewed-by: Konrad Dybcio <konrad.dybcio@...ainline.org>
>>> ---
>>> arch/arm64/boot/dts/qcom/sm8450.dtsi | 18 ++++++++++++++++++
>>> 1 file changed, 18 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/qcom/sm8450.dtsi b/arch/arm64/boot/dts/qcom/sm8450.dtsi
>>> index f75de777f6ea..b80e34fd3fe1 100644
>>> --- a/arch/arm64/boot/dts/qcom/sm8450.dtsi
>>> +++ b/arch/arm64/boot/dts/qcom/sm8450.dtsi
>>> @@ -645,6 +645,24 @@ pdc: interrupt-controller@...0000 {
>>> interrupt-controller;
>>> };
>>>
>>> + spmi_bus: spmi@...d000 {
>>> + compatible = "qcom,spmi-pmic-arb";
>>> + reg = <0x0 0x0c400000 0x0 0x00003000>,
>>> + <0x0 0x0c500000 0x0 0x00400000>,
>>> + <0x0 0x0c440000 0x0 0x00080000>,
>>> + <0x0 0x0c4c0000 0x0 0x00010000>,
>>> + <0x0 0x0c42d000 0x0 0x00010000>;
>>
>> This is a patch from December 2021. Is there anything blocking it from
>> being merged?
>>
>> The same applies to several other patches here.
>
> As far as I know, Stephen still didn't pick up the spmi-pmic-arb support
> for the PMIC on the SM8450 platform. Thus we also can not merge the DT
> parts.
Why we cannot merge DTS? How is DTS with new nodes depending on any
driver changes?
Just like I replied to Konrad - if that's true, bindings are simply
wrong and should be fixed.
Best regards,
Krzysztof
Powered by blists - more mailing lists