From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kishon Vijay Abraham I <kishon@ti.com>,
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>
Subject: Re: [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs
Date: Thu, 2 Jun 2022 13:09:54 +0200 [thread overview]
Message-ID: <f7d62376-49b7-8929-7027-9c81703a5f7b@linaro.org> (raw)
In-Reply-To: <68381314-136b-776d-070a-e825506f2132@ti.com>
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
next prev parent reply other threads:[~2022-06-02 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 7:27 [PATCH 0/2] soc: ti: Enable PRUSS-M on " Kishon Vijay Abraham I
2022-04-27 7:27 ` [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for " Kishon Vijay Abraham I
2022-04-28 6:18 ` Krzysztof Kozlowski
2022-05-16 12:33 ` Kishon Vijay Abraham I
2022-05-16 15:18 ` Krzysztof Kozlowski
2022-06-02 10:03 ` Kishon Vijay Abraham I
2022-06-02 11:09 ` Krzysztof Kozlowski [this message]
2022-04-27 7:27 ` [PATCH 2/2] soc: ti: pruss: Enable support for PRUSS-M subsystem on " Kishon Vijay Abraham I
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7d62376-49b7-8929-7027-9c81703a5f7b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®