From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Conor Dooley <conor.dooley@microchip.com>, geert+renesas@glider.be
Cc: conor@kernel.org, Magnus Damm <magnus.damm@gmail.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] riscv: dts: renesas: clean up dtbs_check W=1 warning due to empty phy node
Date: Wed, 12 Jul 2023 11:43:43 +0300 [thread overview]
Message-ID: <18871eff-f2be-9eed-ee4c-99eba87686d8@gmail.com> (raw)
In-Reply-To: <20230712-squealer-walmart-9587342ddec1@wendy>
Hello!
On 7/12/23 11:14 AM, Conor Dooley wrote:
> dtbs_check w/ W=1 complains:
> Warning (unit_address_vs_reg): /soc/ethernet@11c20000/ethernet-phy@7: node has a unit name, but no reg or ranges property
> Warning (avoid_unnecessary_addr_size): /soc/ethernet@11c20000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
>
> The ethernet@11c20000 node is guarded by an `#if (!SW_ET0_EN_N)` in
> rzg2ul-smarc-som.dtsi, where the phy child node is added. In
> rzfive-smarc-som.dtsi, the ethernet node is marked disabled & the
> interrupt properties are deleted from the phy child node. As a result,
> the produced dts looks like:
> ethernet@11c20000 {
> compatible = "renesas,r9a07g043-gbeth\0renesas,rzg2l-gbeth";
> /* snip */
> #address-cells = <0x01>;
> #size-cells = <0x00>;
> status = "disabled";
>
> ethernet-phy@7 {
> };
> };
>
> Adding a corresponding `#if (!SW_ET0_EN_N)` around the node in
> rzfive-smarc-som.dtsi avoids the complaint, as the empty child node is
> not added:
> ethernet@11c20000 {
> compatible = "renesas,r9a07g043-gbeth\0renesas,rzg2l-gbeth";
> /* snip */
> #address-cells = <0x01>;
> #size-cells = <0x00>;
> status = "disabled";
> };
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
[...]
> diff --git a/arch/riscv/boot/dts/renesas/rzfive-smarc-som.dtsi b/arch/riscv/boot/dts/renesas/rzfive-smarc-som.dtsi
> index d6f18754eb5d..c62debc7ca7e 100644
> --- a/arch/riscv/boot/dts/renesas/rzfive-smarc-som.dtsi
> +++ b/arch/riscv/boot/dts/renesas/rzfive-smarc-som.dtsi
> @@ -22,6 +22,7 @@ &dmac {
> status = "disabled";
> };
>
> +#if (!SW_ET0_EN_N)
Are the parens really needed here?
> ð0 {
> status = "disabled";
>
[...]
MBR, Sergey
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-07-12 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 8:14 [PATCH v1] riscv: dts: renesas: clean up dtbs_check W=1 warning due to empty phy node Conor Dooley
2023-07-12 8:43 ` Sergei Shtylyov [this message]
2023-07-12 9:13 ` Geert Uytterhoeven
2023-07-12 9:12 ` Geert Uytterhoeven
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=18871eff-f2be-9eed-ee4c-99eba87686d8@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
/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