From: Herve Codina <herve.codina@bootlin•com>
To: Philipp Zabel <p.zabel@pengutronix•de>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Rob Herring <robh@kernel•org>
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
Arnd Bergmann <arnd@arndb•de>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
Allan Nielsen <allan.nielsen@microchip•com>,
Horatiu Vultur <horatiu.vultur@microchip•com>,
Steen Hegelund <steen.hegelund@microchip•com>,
Thomas Petazzoni <thomas.petazzoni@bootlin•com>,
Herve Codina <herve.codina@bootlin•com>
Subject: [PATCH v2 0/2] Fix dtc warnings when building the LAN966x device tree overlay
Date: Tue, 29 Oct 2024 09:43:34 +0100 [thread overview]
Message-ID: <20241029084338.194942-1-herve.codina@bootlin.com> (raw)
dtc generates 3 kinds of warnings when it builds the LAN966x dtso.
- missing or empty reg/ranges property
.../pci-ep-bus@0/cpu_clk: missing or empty reg/ranges property
.../pci-ep-bus@0/ddr_clk: missing or empty reg/ranges property
.../pci-ep-bus@0/sys_clk: missing or empty reg/ranges property
Patch 1 in this series fixes these warnings
- Missing interrupt-parent
.../pci-ep-bus@0/oic@e00c0120: Missing interrupt-parent
This warning was quickly silenced by Philipp [1].
Patch 2 in this series fixes the warning and should replace the patch
applied by Philipp to silence the warning.
- Warning (avoid_unnecessary_addr_size)
/fragment@0/__overlay__: unnecessary #address-cells/#size-cells without "ranges", "dma-ranges" or child "reg" property
This warning should be fixed in dtc.
A patch has already be sent by Philip to fix it [2].
[1] https://lore.kernel.org/all/57793bb01e02f03e215dfa6f8783df18034ae2ea.camel@pengutronix.de/
[2] https://lore.kernel.org/devicetree-compiler/20241025161307.3629901-1-p.zabel@pengutronix.de/T/#u
Compare to the previous iteration, this v2 series mainly renames clock
nodes.
Best regards,
Hervé
Changes v1 -> v2
v1: https://lore.kernel.org/lkml/20241028122405.27090-1-herve.codina@bootlin.com/
- Patch 1
Rename clock nodes
- Patch 2
Add 'Reviewed-by: Rob Herring (Arm) <robh@kernel•org>'
Herve Codina (2):
misc: lan966x_pci: Fix dtc warns 'missing or empty reg/ranges
property'
misc: lan966x_pci: Fix dtc warn 'Missing interrupt-parent'
drivers/misc/lan966x_pci.dtso | 46 +++++++++++++++++++++--------------
1 file changed, 28 insertions(+), 18 deletions(-)
--
2.46.2
next reply other threads:[~2024-10-29 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 8:43 Herve Codina [this message]
2024-10-29 8:43 ` [PATCH v2 1/2] misc: lan966x_pci: Fix dtc warns 'missing or empty reg/ranges property' Herve Codina
2024-10-29 12:36 ` Rob Herring
2024-10-29 8:43 ` [PATCH v2 2/2] misc: lan966x_pci: Fix dtc warn 'Missing interrupt-parent' Herve Codina
2024-10-31 15:01 ` [PATCH v2 0/2] Fix dtc warnings when building the LAN966x device tree overlay Herve Codina
2024-11-04 13:47 ` Philipp Zabel
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=20241029084338.194942-1-herve.codina@bootlin.com \
--to=herve.codina@bootlin$(echo .)com \
--cc=allan.nielsen@microchip$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=horatiu.vultur@microchip$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=p.zabel@pengutronix$(echo .)de \
--cc=robh@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=steen.hegelund@microchip$(echo .)com \
--cc=thomas.petazzoni@bootlin$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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