[PATCH 0/2] soc: ti: Enable PRUSS-M on K3 AM62x SoCs

[PATCH 0/2] soc: ti: Enable PRUSS-M on K3 AM62x SoCs

[Kishon Vijay Abraham I]

Series adds AM62x specific compatible string to enable PRUSS-M in
AM62x SoCs.

Kishon Vijay Abraham I (2):
  dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs
  soc: ti: pruss: Enable support for PRUSS-M subsystem on K3 AM62x SoCs

 Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 1 +
 drivers/soc/ti/pruss.c                                 | 1 +
 2 files changed, 2 insertions(+)

-- 
2.17.1

[PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs

[Kishon Vijay Abraham I]

Update the PRUSS bindings for the PRUSSM instance present in
AM625 SoC.

Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
 Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
index 64461d432004..cf13e5179657 100644
--- a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
+++ b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
@@ -69,6 +69,7 @@ properties:
       - ti,am654-icssg   # for K3 AM65x SoC family
       - ti,j721e-icssg   # for K3 J721E SoC family
       - ti,am642-icssg   # for K3 AM64x SoC family
+      - ti,am625-pruss   # for K3 AM62x SoC family
 
   reg:
     maxItems: 1
-- 
2.17.1

[PATCH 2/2] soc: ti: pruss: Enable support for PRUSS-M subsystem on K3 AM62x SoCs

[Kishon Vijay Abraham I]

The K3 AM62x family of SoC has one PRUSS-M instance and it has two
Programmable Real-Time Units (PRU0 and PRU1). This does not support
Industrial Communications Subsystem features like Ethernet.

The existing pruss platform driver has been updated to support this
through a new AM62x specific compatible.

Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
 drivers/soc/ti/pruss.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/soc/ti/pruss.c b/drivers/soc/ti/pruss.c
index b36779309e49..7c8111ca2b72 100644
--- a/drivers/soc/ti/pruss.c
+++ b/drivers/soc/ti/pruss.c
@@ -339,6 +339,7 @@ static const struct of_device_id pruss_of_match[] = {
 	{ .compatible = "ti,am654-icssg", .data = &am65x_j721e_pruss_data, },
 	{ .compatible = "ti,j721e-icssg", .data = &am65x_j721e_pruss_data, },
 	{ .compatible = "ti,am642-icssg", .data = &am65x_j721e_pruss_data, },
+	{ .compatible = "ti,am625-pruss", .data = &am65x_j721e_pruss_data, },
 	{},
 };
 MODULE_DEVICE_TABLE(of, pruss_of_match);
-- 
2.17.1

Re: [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs

[Krzysztof Kozlowski]

On 27/04/2022 09:27, Kishon Vijay Abraham I wrote:
> Update the PRUSS bindings for the PRUSSM instance present in
> AM625 SoC.
> 
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> ---
>  Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
> index 64461d432004..cf13e5179657 100644
> --- a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
> +++ b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
> @@ -69,6 +69,7 @@ properties:
>        - ti,am654-icssg   # for K3 AM65x SoC family
>        - ti,j721e-icssg   # for K3 J721E SoC family
>        - ti,am642-icssg   # for K3 AM64x SoC family
> +      - ti,am625-pruss   # for K3 AM62x SoC family
>  

Looks like out of order (although for some reason before it was also
misordered...).


Best regards,
Krzysztof

Re: [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs

[Kishon Vijay Abraham I]

Hi Krzysztof,

On 28/04/22 11:48, Krzysztof Kozlowski wrote:
> On 27/04/2022 09:27, Kishon Vijay Abraham I wrote:
>> Update the PRUSS bindings for the PRUSSM instance present in
>> AM625 SoC.
>>
>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>> ---
>>  Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>> index 64461d432004..cf13e5179657 100644
>> --- a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>> +++ b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>> @@ -69,6 +69,7 @@ properties:
>>        - ti,am654-icssg   # for K3 AM65x SoC family
>>        - ti,j721e-icssg   # for K3 J721E SoC family
>>        - ti,am642-icssg   # for K3 AM64x SoC family
>> +      - ti,am625-pruss   # for K3 AM62x SoC family
>>  
> 
> Looks like out of order (although for some reason before it was also
> misordered...).

These are really in the chronological order of the introduction of SoCs.
Isn't that okay to have?

Thanks,
Kishon

Re: [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs

[Krzysztof Kozlowski]

On 16/05/2022 14:33, Kishon Vijay Abraham I wrote:
> Hi Krzysztof,
> 
> On 28/04/22 11:48, Krzysztof Kozlowski wrote:
>> On 27/04/2022 09:27, Kishon Vijay Abraham I wrote:
>>> Update the PRUSS bindings for the PRUSSM instance present in
>>> AM625 SoC.
>>>
>>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>>> ---
>>>  Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 1 +
>>>  1 file changed, 1 insertion(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>> index 64461d432004..cf13e5179657 100644
>>> --- a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>> +++ b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>> @@ -69,6 +69,7 @@ properties:
>>>        - ti,am654-icssg   # for K3 AM65x SoC family
>>>        - ti,j721e-icssg   # for K3 J721E SoC family
>>>        - ti,am642-icssg   # for K3 AM64x SoC family
>>> +      - ti,am625-pruss   # for K3 AM62x SoC family
>>>  
>>
>> Looks like out of order (although for some reason before it was also
>> misordered...).
> 
> These are really in the chronological order of the introduction of SoCs.
> Isn't that okay to have?

You mean order of release on the market of order of adding files here?
The first is ok, the latter would mean there is no order at all.

It's a nit, so I don't expect to change it. It just increases our
chances for conflicts...


Best regards,
Krzysztof

Re: [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs

[Kishon Vijay Abraham I]

Hi Krzysztof,

On 16/05/22 20:48, Krzysztof Kozlowski wrote:
> On 16/05/2022 14:33, Kishon Vijay Abraham I wrote:
>> Hi Krzysztof,
>>
>> On 28/04/22 11:48, Krzysztof Kozlowski wrote:
>>> On 27/04/2022 09:27, Kishon Vijay Abraham I wrote:
>>>> Update the PRUSS bindings for the PRUSSM instance present in
>>>> AM625 SoC.
>>>>
>>>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>>>> ---
>>>>  Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 1 +
>>>>  1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>>> index 64461d432004..cf13e5179657 100644
>>>> --- a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>>> +++ b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>>> @@ -69,6 +69,7 @@ properties:
>>>>        - ti,am654-icssg   # for K3 AM65x SoC family
>>>>        - ti,j721e-icssg   # for K3 J721E SoC family
>>>>        - ti,am642-icssg   # for K3 AM64x SoC family
>>>> +      - ti,am625-pruss   # for K3 AM62x SoC family
>>>>  
>>>
>>> Looks like out of order (although for some reason before it was also
>>> misordered...).
>>
>> These are really in the chronological order of the introduction of SoCs.
>> Isn't that okay to have?
> 
> You mean order of release on the market of order of adding files here?
> The first is ok, the latter would mean there is no order at all.

I meant order of release to market. Anyways, I'll send a patch to change
the order to alphabetic order.

Thanks,
Kishon

Re: [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs

[Krzysztof Kozlowski]

On 02/06/2022 12:03, Kishon Vijay Abraham I wrote:
> Hi Krzysztof,
> 
> On 16/05/22 20:48, Krzysztof Kozlowski wrote:
>> On 16/05/2022 14:33, Kishon Vijay Abraham I wrote:
>>> Hi Krzysztof,
>>>
>>> On 28/04/22 11:48, Krzysztof Kozlowski wrote:
>>>> On 27/04/2022 09:27, Kishon Vijay Abraham I wrote:
>>>>> Update the PRUSS bindings for the PRUSSM instance present in
>>>>> AM625 SoC.
>>>>>
>>>>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>>>>> ---
>>>>>  Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 1 +
>>>>>  1 file changed, 1 insertion(+)
>>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>>>> index 64461d432004..cf13e5179657 100644
>>>>> --- a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>>>> +++ b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>>>> @@ -69,6 +69,7 @@ properties:
>>>>>        - ti,am654-icssg   # for K3 AM65x SoC family
>>>>>        - ti,j721e-icssg   # for K3 J721E SoC family
>>>>>        - ti,am642-icssg   # for K3 AM64x SoC family
>>>>> +      - ti,am625-pruss   # for K3 AM62x SoC family
>>>>>  
>>>>
>>>> Looks like out of order (although for some reason before it was also
>>>> misordered...).
>>>
>>> These are really in the chronological order of the introduction of SoCs.
>>> Isn't that okay to have?
>>
>> You mean order of release on the market of order of adding files here?
>> The first is ok, the latter would mean there is no order at all.
> 
> I meant order of release to market. Anyways, I'll send a patch to change
> the order to alphabetic order.

It's okay to keep it then in such release-market order. Up to you:


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


Best regards,
Krzysztof