Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <dcce6737-5881-a703-67f0-59c5f55f1cd1@ti.com>
Date:   Mon, 16 May 2022 18:03:37 +0530
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.9.0
Subject: Re: [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3
 AM62x SoCs
Content-Language: en-US
To:     Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Nishanth Menon <nm@ti.com>
CC:     Santosh Shilimkar <ssantosh@kernel.org>,
        <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>,
        Vignesh Raghavendra <vigneshr@ti.com>
References: <20220427072703.4898-1-kishon@ti.com>
 <20220427072703.4898-2-kishon@ti.com>
 <53212a3b-d02c-ab5e-6b5c-e19d359c7c2b@linaro.org>
From:   Kishon Vijay Abraham I <kishon@ti.com>
In-Reply-To: <53212a3b-d02c-ab5e-6b5c-e19d359c7c2b@linaro.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

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