From: Neha Malcom Francis <n-francis@ti.com>
To: Manorit Chawdhry <m-chawdhry@ti.com>, Nishanth Menon <nm@ti.com>
Cc: Andrew Davis <afd@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Aniket Limaye <a-limaye@ti.com>, Udit Kumar <u-kumar1@ti.com>,
Beleswar Padhi <b-padhi@ti.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>
Subject: Re: [PATCH v3 1/5] arm64: dts: ti: k3-j721s2*: Add bootph-* properties
Date: Wed, 7 Aug 2024 11:03:29 +0530 [thread overview]
Message-ID: <8a910e2f-aaf2-40cd-8131-a1a2531a12c8@ti.com> (raw)
In-Reply-To: <20240807052628.jclbmw4zs72jm6km@uda0497581>
Hi Manorit
On 07/08/24 10:56, Manorit Chawdhry wrote:
> Hi Nishanth,
>
> On 10:07-20240806, Nishanth Menon wrote:
>> On 09:43-20240806, Andrew Davis wrote:
>>> On 7/30/24 4:53 AM, Manorit Chawdhry wrote:
>>>> Adds bootph-* properties to the leaf nodes to enable U-boot to
>>>> utilise them.
>>>
>>> U-Boot? Let's try to pretend like this is a generic property and
>>> just say "bootloader" :)
>>>> @@ -445,6 +446,7 @@ flash@0 {
>>>> cdns,tchsh-ns = <60>;
>>>> cdns,tslch-ns = <60>;
>>>> cdns,read-delay = <4>;
>>>> + bootph-all;
>>
>> Here and elsewhere, follow:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/dts-coding-style.rst#n117
>
> Could you tell me what are you seeing wrong? The dts-coding-style that
> you shared doesn't tell a specific location for bootph-* properties so
> using the generic reasoning.
>
> "1. Most important properties start the node: compatible then bus addressing to
> match unit address."
>
> This is the least important property considering Linux and hence the
> reasoning was that it should come in the last. Also, j722s and am62p
> follow the same convention so it was taken from there only.
>
Not sure if this is what he meant, but bootph-* comes under standard/common
properties as per my understanding of the coding style. And status needs to be
at the very end if it's there (in this case it's not but just mentioning).
> Regards,
> Manorit
>
>>
>>
>>>> };
>>>> };
>>>>
>>
>> --
>> Regards,
>> Nishanth Menon
>> Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
--
Thanking You
Neha Malcom Francis
next prev parent reply other threads:[~2024-08-07 5:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 9:53 [PATCH v3 0/5] Add bootph-all property for J7 boards Manorit Chawdhry
2024-07-30 9:53 ` [PATCH v3 1/5] arm64: dts: ti: k3-j721s2*: Add bootph-* properties Manorit Chawdhry
2024-08-06 14:43 ` Andrew Davis
2024-08-06 15:05 ` Nishanth Menon
2024-08-06 15:07 ` Nishanth Menon
2024-08-07 5:26 ` Manorit Chawdhry
2024-08-07 5:33 ` Neha Malcom Francis [this message]
2024-08-07 5:42 ` Manorit Chawdhry
2024-08-07 5:48 ` Neha Malcom Francis
2024-08-07 6:36 ` Manorit Chawdhry
2024-08-07 11:49 ` Nishanth Menon
2024-08-07 5:49 ` Manorit Chawdhry
2024-08-07 11:47 ` Nishanth Menon
2024-08-07 5:31 ` Manorit Chawdhry
2024-07-30 9:53 ` [PATCH v3 2/5] arm64: dts: ti: k3-j784s4*: Remove bootph properties from parent nodes Manorit Chawdhry
2024-08-07 7:51 ` Kumar, Udit
2024-07-30 9:53 ` [PATCH v3 3/5] arm64: dts: ti: k3-am68*: Add bootph-* properties Manorit Chawdhry
2024-07-30 9:53 ` [PATCH v3 4/5] arm64: dts: ti: k3-j721e*: " Manorit Chawdhry
2024-08-07 7:37 ` Kumar, Udit
2024-08-07 8:35 ` Manorit Chawdhry
2024-08-07 9:16 ` Kumar, Udit
2024-08-07 9:24 ` Neha Malcom Francis
2024-08-07 9:47 ` Manorit Chawdhry
2024-07-30 9:53 ` [PATCH v3 5/5] arm64: dts: ti: k3-j7200*: " Manorit Chawdhry
2024-08-07 7:28 ` Kumar, Udit
2024-08-07 7:50 ` Manorit Chawdhry
2024-08-07 9:15 ` Kumar, Udit
2024-08-07 14:37 ` Limaye, Aniket
2024-08-08 9:20 ` Manorit Chawdhry
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=8a910e2f-aaf2-40cd-8131-a1a2531a12c8@ti.com \
--to=n-francis@ti.com \
--cc=a-limaye@ti.com \
--cc=afd@ti.com \
--cc=b-padhi@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=u-kumar1@ti.com \
--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