diff mbox series

dt-bindings: cache: qcom,llcc: correct QDU1000 reg entries

Message ID 20231107080436.16747-1-krzysztof.kozlowski@linaro.org
State Accepted
Commit f0f99f371822c48847e02e56d6e7de507e18f186
Headers show
Series dt-bindings: cache: qcom,llcc: correct QDU1000 reg entries | expand

Commit Message

Krzysztof Kozlowski Nov. 7, 2023, 8:04 a.m. UTC
Qualcomm QDU1000 DTSI comes with one LLCC0 base address as pointed by
dtbs_check:

  qdu1000-idp.dtb: system-cache-controller@19200000: reg-names:2: 'llcc2_base' was expected

Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

---

Recent LLCC patches were not tested on QDU1000 thus the LLCC is there
broken.  This patch at least tries to bring some sense according to
DTSI, but I have no clue what is here correct: driver, DTS or bindings.
---
 Documentation/devicetree/bindings/cache/qcom,llcc.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

Conor Dooley Nov. 8, 2023, 12:26 p.m. UTC | #1
On Tue, Nov 07, 2023 at 02:25:25PM +0530, Mukesh Ojha wrote:
> 
> 
> On 11/7/2023 1:34 PM, Krzysztof Kozlowski wrote:
> > Qualcomm QDU1000 DTSI comes with one LLCC0 base address as pointed by
> > dtbs_check:
> > 
> >    qdu1000-idp.dtb: system-cache-controller@19200000: reg-names:2: 'llcc2_base' was expected
> > 
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > 
> > ---
> > 
> > Recent LLCC patches were not tested on QDU1000 thus the LLCC is there
> > broken.  This patch at least tries to bring some sense according to
> > DTSI, but I have no clue what is here correct: driver, DTS or bindings.
> > ---
> >   Documentation/devicetree/bindings/cache/qcom,llcc.yaml | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/Documentation/devicetree/bindings/cache/qcom,llcc.yaml b/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
> > index 580f9a97ddf7..d610b0be262c 100644
> > --- a/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
> > +++ b/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
> > @@ -64,6 +64,7 @@ allOf:
> >           compatible:
> >             contains:
> >               enum:
> > +              - qcom,qdu1000-llcc
> >                 - qcom,sc7180-llcc
> >                 - qcom,sm6350-llcc
> 
> Thanks, again.
> 
> Acked-by: Mukesh Ojha <quic_mojha@quicinc.com>

I'm assuming given your employer, this ack means that there is no
llcc2_base on the qdu1000.

Acked-by: Conor Dooley <conor.dooley@microchip.com>

Cheers,
Conor.
Mukesh Ojha Nov. 9, 2023, 8:40 a.m. UTC | #2
On 11/8/2023 5:56 PM, Conor Dooley wrote:
> On Tue, Nov 07, 2023 at 02:25:25PM +0530, Mukesh Ojha wrote:
>>
>>
>> On 11/7/2023 1:34 PM, Krzysztof Kozlowski wrote:
>>> Qualcomm QDU1000 DTSI comes with one LLCC0 base address as pointed by
>>> dtbs_check:
>>>
>>>     qdu1000-idp.dtb: system-cache-controller@19200000: reg-names:2: 'llcc2_base' was expected
>>>
>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>
>>> ---
>>>
>>> Recent LLCC patches were not tested on QDU1000 thus the LLCC is there
>>> broken.  This patch at least tries to bring some sense according to
>>> DTSI, but I have no clue what is here correct: driver, DTS or bindings.
>>> ---
>>>    Documentation/devicetree/bindings/cache/qcom,llcc.yaml | 2 +-
>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/cache/qcom,llcc.yaml b/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
>>> index 580f9a97ddf7..d610b0be262c 100644
>>> --- a/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
>>> +++ b/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
>>> @@ -64,6 +64,7 @@ allOf:
>>>            compatible:
>>>              contains:
>>>                enum:
>>> +              - qcom,qdu1000-llcc
>>>                  - qcom,sc7180-llcc
>>>                  - qcom,sm6350-llcc
>>
>> Thanks, again.
>>
>> Acked-by: Mukesh Ojha <quic_mojha@quicinc.com>
> 
> I'm assuming given your employer, this ack means that there is no
> llcc2_base on the qdu1000.

Yes, not even have llcc1 , just llcc0.

-Mukesh
> 
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> 
> Cheers,
> Conor.
Rob Herring Dec. 8, 2023, 1:23 p.m. UTC | #3
On Tue, 07 Nov 2023 09:04:36 +0100, Krzysztof Kozlowski wrote:
> Qualcomm QDU1000 DTSI comes with one LLCC0 base address as pointed by
> dtbs_check:
> 
>   qdu1000-idp.dtb: system-cache-controller@19200000: reg-names:2: 'llcc2_base' was expected
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> 
> ---
> 
> Recent LLCC patches were not tested on QDU1000 thus the LLCC is there
> broken.  This patch at least tries to bring some sense according to
> DTSI, but I have no clue what is here correct: driver, DTS or bindings.
> ---
>  Documentation/devicetree/bindings/cache/qcom,llcc.yaml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Applied, thanks!
Mukesh Ojha June 11, 2024, 10:15 a.m. UTC | #4
On Thu, Nov 09, 2023 at 02:10:41PM +0530, Mukesh Ojha wrote:
> 
> 
> On 11/8/2023 5:56 PM, Conor Dooley wrote:
> > On Tue, Nov 07, 2023 at 02:25:25PM +0530, Mukesh Ojha wrote:
> > > 
> > > 
> > > On 11/7/2023 1:34 PM, Krzysztof Kozlowski wrote:
> > > > Qualcomm QDU1000 DTSI comes with one LLCC0 base address as pointed by
> > > > dtbs_check:
> > > > 
> > > >     qdu1000-idp.dtb: system-cache-controller@19200000: reg-names:2: 'llcc2_base' was expected
> > > > 
> > > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > > > 
> > > > ---
> > > > 
> > > > Recent LLCC patches were not tested on QDU1000 thus the LLCC is there
> > > > broken.  This patch at least tries to bring some sense according to
> > > > DTSI, but I have no clue what is here correct: driver, DTS or bindings.
> > > > ---
> > > >    Documentation/devicetree/bindings/cache/qcom,llcc.yaml | 2 +-
> > > >    1 file changed, 1 insertion(+), 1 deletion(-)
> > > > 
> > > > diff --git a/Documentation/devicetree/bindings/cache/qcom,llcc.yaml b/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
> > > > index 580f9a97ddf7..d610b0be262c 100644
> > > > --- a/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
> > > > +++ b/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
> > > > @@ -64,6 +64,7 @@ allOf:
> > > >            compatible:
> > > >              contains:
> > > >                enum:
> > > > +              - qcom,qdu1000-llcc
> > > >                  - qcom,sc7180-llcc
> > > >                  - qcom,sm6350-llcc
> > > 
> > > Thanks, again.
> > > 
> > > Acked-by: Mukesh Ojha <quic_mojha@quicinc.com>
> > 
> > I'm assuming given your employer, this ack means that there is no
> > llcc2_base on the qdu1000.
> 
> Yes, not even have llcc1 , just llcc0.

Looks like i saw downstream usage and said LLCC has only one
instance for qdu1000, it looks refactor happened during the
same where each bank need to separately denoted in device tree.
Change was fine a/c to its usage in device tree.
Not an excuse, that is an ignorance from my side while acking
the change.

qdu1000 has 8 banks from llcc0-7 that need to corrected both
in its device tree and in the binding.

@komal will be sending patch for this.

-Mukesh
diff mbox series

Patch

diff --git a/Documentation/devicetree/bindings/cache/qcom,llcc.yaml b/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
index 580f9a97ddf7..d610b0be262c 100644
--- a/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
+++ b/Documentation/devicetree/bindings/cache/qcom,llcc.yaml
@@ -64,6 +64,7 @@  allOf:
         compatible:
           contains:
             enum:
+              - qcom,qdu1000-llcc
               - qcom,sc7180-llcc
               - qcom,sm6350-llcc
     then:
@@ -101,7 +102,6 @@  allOf:
         compatible:
           contains:
             enum:
-              - qcom,qdu1000-llcc
               - qcom,sc8180x-llcc
               - qcom,sc8280xp-llcc
     then: