From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Justin Swartz <justin.swartz@risingedge.co.za>,
Sergio Paracuellos <sergio.paracuellos@gmail.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>
Cc: 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 v2] mips: dts: ralink: mt7621: add cell count properties to usb
Date: Fri, 8 Mar 2024 15:01:00 +0300 [thread overview]
Message-ID: <c445fd12-f8a8-41df-bee8-8b126b26110b@arinc9.com> (raw)
In-Reply-To: <20240307223756.31643-1-justin.swartz@risingedge.co.za>
On 8.03.2024 01:37, Justin Swartz wrote:
> Add default #address-cells and #size-cells properties to the
> usb node, which should be suitable for hubs and devices without
> explicitly declared interface nodes, as:
>
> "#address-cells":
> description: should be 1 for hub nodes with device nodes,
> should be 2 for device nodes with interface nodes.
> enum: [1, 2]
>
> "#size-cells":
> const: 0
>
> -- Documentation/devicetree/bindings/usb/usb-device.yaml
>
> This version of the patch places the properties according to
> the order recommended by:
>
> Documentation/devicetree/bindings/dts-coding-style.rst
>
> Signed-off-by: Justin Swartz <justin.swartz@risingedge.co.za>
> ---
> arch/mips/boot/dts/ralink/mt7621.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/boot/dts/ralink/mt7621.dtsi b/arch/mips/boot/dts/ralink/mt7621.dtsi
> index 5a89f0b8c..7532e17dd 100644
> --- a/arch/mips/boot/dts/ralink/mt7621.dtsi
> +++ b/arch/mips/boot/dts/ralink/mt7621.dtsi
> @@ -289,10 +289,10 @@ usb: usb@1e1c0000 {
> reg = <0x1e1c0000 0x1000
> 0x1e1d0700 0x0100>;
> reg-names = "mac", "ippc";
> -
> + #address-cells = <1>;
> + #size-cells = <0>;
> clocks = <&sysc MT7621_CLK_XTAL>;
> clock-names = "sys_ck";
> -
Please keep the empty lines. It's easier to read. I don't see anything on
the Devicetree Sources (DTS) Coding Style that would restrict this.
Arınç
next prev parent reply other threads:[~2024-03-08 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0001-mips-dts-ralink-mt7621-add-cell-count-properties-to-.patch>
2024-03-07 22:37 ` [PATCH v2] mips: dts: ralink: mt7621: add cell count properties to usb Justin Swartz
2024-03-08 9:32 ` Sergio Paracuellos
2024-03-08 12:01 ` Arınç ÜNAL [this message]
2024-03-08 13:21 ` Justin Swartz
2024-03-08 13:48 ` Arınç ÜNAL
2024-03-08 13:57 ` Justin Swartz
2024-03-07 14:58 [PATCH] mips: dts: ralink: mt7621: add cell count properties to usb0 Justin Swartz
2024-03-07 23:58 ` [PATCH v2] mips: dts: ralink: mt7621: add cell count properties to usb Justin Swartz
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=c445fd12-f8a8-41df-bee8-8b126b26110b@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=justin.swartz@risingedge.co.za \
--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