From: Justin Swartz <justin.swartz@risingedge.co.za>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 2/2] mips: dts: ralink: mt7621: add serial1 and serial2 nodes
Date: Thu, 07 Mar 2024 17:14:57 +0200 [thread overview]
Message-ID: <13e3063facfea3407dba23b74b0a56db@risingedge.co.za> (raw)
In-Reply-To: <CAMhs-H9WyQZsvEvCfUcZ0_eU8--EzxEmaxR50wdRFDGP3E64ZQ@mail.gmail.com>
Hi Sergio
On 2024-03-07 12:04, Sergio Paracuellos wrote:
> Hi Justin,
>
> On Wed, Mar 6, 2024 at 9:11 PM Justin Swartz
> <justin.swartz@risingedge.co.za> wrote:
>>
>> Add serial1 and serial2 nodes to define the existence of
>> UART1 and UART2.
>>
>> Signed-off-by: Justin Swartz <justin.swartz@risingedge.co.za>
>> ---
>> arch/mips/boot/dts/ralink/mt7621.dtsi | 38
>> +++++++++++++++++++++++++++
>> 1 file changed, 38 insertions(+)
>>
>> diff --git a/arch/mips/boot/dts/ralink/mt7621.dtsi
>> b/arch/mips/boot/dts/ralink/mt7621.dtsi
>> index dca415fdd..2069249c8 100644
>> --- a/arch/mips/boot/dts/ralink/mt7621.dtsi
>> +++ b/arch/mips/boot/dts/ralink/mt7621.dtsi
>> @@ -128,6 +128,44 @@ serial0: serial@c00 {
>> pinctrl-0 = <&uart1_pins>;
>> };
>>
>> + serial1: serial@d00 {
>> + status = "disabled";
>> +
>> + compatible = "ns16550a";
>> + reg = <0xd00 0x100>;
>> +
>> + clocks = <&sysc MT7621_CLK_UART2>;
>> +
>> + interrupt-parent = <&gic>;
>> + interrupts = <GIC_SHARED 27
>> IRQ_TYPE_LEVEL_HIGH>;
>> +
>> + reg-shift = <2>;
>> + reg-io-width = <4>;
>> + no-loopback-test;
>> +
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&uart2_pins>;
>> + };
>> +
>> + serial2: serial@e00 {
>> + status = "disabled";
>> +
>> + compatible = "ns16550a";
>> + reg = <0xe00 0x100>;
>> +
>> + clocks = <&sysc MT7621_CLK_UART3>;
>> +
>> + interrupt-parent = <&gic>;
>> + interrupts = <GIC_SHARED 28
>> IRQ_TYPE_LEVEL_HIGH>;
>> +
>> + reg-shift = <2>;
>> + reg-io-width = <4>;
>> + no-loopback-test;
>> +
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&uart3_pins>;
>> + };
>> +
>
> Please follow the preferred order for properties described in dts
> coding style [0]. I know that there is some mess around the properties
> order in some nodes with the current dtsi file but we did not have
> coding style before and now we have it, so I think we should follow it
> at least for new additions.
No problem. I see you've already "Acked-by" patch 1 (adding pinctrl
properties to serial0) of this set, so would it be a better move to
submit a new patch set that would look something like:
1. add pinctrl-name and pinctrl-0 to serial0 [no changes from what I
sent]
2. reorder serial0 properties according to the DTS style guidelines
3. add serial1 and serial2 with the correct property order
Or instead, submit one more patch that will reorder the properties in
serial0, serial1 and serial2 - which would depend on the current set?
> Best regards,
> Sergio Paracuellos
Regards
Justin
> [0]: https://docs.kernel.org/devicetree/bindings/dts-coding-style.html
next prev parent reply other threads:[~2024-03-07 15:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 20:10 [PATCH 1/2] mips: dts: ralink: mt7621: associate uart1_pins with serial0 Justin Swartz
2024-03-06 20:10 ` [PATCH 2/2] mips: dts: ralink: mt7621: add serial1 and serial2 nodes Justin Swartz
2024-03-07 10:04 ` Sergio Paracuellos
2024-03-07 15:14 ` Justin Swartz [this message]
2024-03-07 16:36 ` Sergio Paracuellos
2024-03-07 19:04 ` [PATCH v2 1/3] mips: dts: ralink: mt7621: associate uart1_pins with serial0 Justin Swartz
2024-03-07 19:04 ` [PATCH v2 2/3] mips: dts: ralink: mt7621: reorder serial0 properties Justin Swartz
2024-03-08 7:29 ` Sergio Paracuellos
2024-03-08 8:42 ` AngeloGioacchino Del Regno
2024-03-07 19:04 ` [PATCH v2 3/3] mips: dts: ralink: mt7621: add serial1 and serial2 nodes Justin Swartz
2024-03-08 7:28 ` Sergio Paracuellos
2024-03-08 8:44 ` AngeloGioacchino Del Regno
2024-03-08 10:56 ` Arınç ÜNAL
2024-03-08 13:50 ` Arınç ÜNAL
2024-03-08 13:56 ` Justin Swartz
2024-03-08 7:27 ` [PATCH v2 1/3] mips: dts: ralink: mt7621: associate uart1_pins with serial0 Sergio Paracuellos
2024-03-08 7:30 ` Sergio Paracuellos
2024-03-08 8:41 ` AngeloGioacchino Del Regno
2024-03-08 12:40 ` Justin Swartz
2024-03-08 13:24 ` Arınç ÜNAL
2024-03-07 11:33 ` [PATCH 1/2] " Sergio Paracuellos
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=13e3063facfea3407dba23b74b0a56db@risingedge.co.za \
--to=justin.swartz@risingedge.co.za \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arinc.unal@arinc9.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for NNTP newsgroup(s).