public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@nabladev.com>
To: Marek Vasut <marek.vasut+renesas@mailbox.org>, u-boot@lists.denx.de
Cc: Christian Marangi <ansuelsmth@gmail.com>,
	Dinesh Maniyam <dinesh.maniyam@altera.com>,
	Guillaume La Roque <glaroque@baylibre.com>,
	Mattijs Korpershoek <mkorpershoek@kernel.org>,
	Simon Glass <sjg@chromium.org>,
	Svyatoslav Ryhel <clamor95@gmail.com>,
	Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH 2/2] sandbox: Fix DT compiler pin warnings in sandbox DTs
Date: Thu, 13 Nov 2025 13:54:32 +0100	[thread overview]
Message-ID: <5a76ffc8-c41e-b2ff-4d95-8f93048dfd21@nabladev.com> (raw)
In-Reply-To: <20251113115658.947953-2-marek.vasut+renesas@mailbox.org>

Hello Marek,

On 13.11.25 12:56, Marek Vasut wrote:
> Trivially fix the following warnings in sandbox DTs, which show up with
> DTC 1.7.2. Assign pin groups less confusing node names with pins- prefix
> to avoid confusing DT compiler into thinking the node is really a bus node:
> 
> "
> arch/sandbox/dts/.test.dtb.pre.tmp:1831.20-1841.5: Warning (i2c_bus_bridge): /pinctrl/i2c: incorrect #address-cells for I2C bus
> arch/sandbox/dts/.test.dtb.pre.tmp:1831.20-1841.5: Warning (i2c_bus_bridge): /pinctrl/i2c: incorrect #size-cells for I2C bus
> arch/sandbox/dts/test.dtb: Warning (i2c_bus_reg): Failed prerequisite 'i2c_bus_bridge'
> arch/sandbox/dts/.test.dtb.pre.tmp:1848.20-1856.5: Warning (spi_bus_bridge): /pinctrl/spi: incorrect #address-cells for SPI bus
> arch/sandbox/dts/.test.dtb.pre.tmp:1848.20-1856.5: Warning (spi_bus_bridge): /pinctrl/spi: incorrect #size-cells for SPI bus
> arch/sandbox/dts/test.dtb: Warning (spi_bus_reg): Failed prerequisite 'spi_bus_bridge'
> "
> 
> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
> ---
> Cc: Christian Marangi <ansuelsmth@gmail.com>
> Cc: Dinesh Maniyam <dinesh.maniyam@altera.com>
> Cc: Guillaume La Roque <glaroque@baylibre.com>
> Cc: Heiko Schocher <hs@nabladev.com>
> Cc: Mattijs Korpershoek <mkorpershoek@kernel.org>
> Cc: Simon Glass <sjg@chromium.org>
> Cc: Svyatoslav Ryhel <clamor95@gmail.com>
> Cc: Tom Rini <trini@konsulko.com>
> Cc: u-boot@lists.denx.de
> ---
>   arch/sandbox/dts/test.dts | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)

Reviewed-by: Heiko Schocher <hs@nabladev.com>

bye,
Heiko
-- 
Nabla Software Engineering
HRB 40522 Augsburg
Phone: +49 821 45592596
E-Mail: office@nabladev.com
Geschäftsführer : Stefano Babic

  reply	other threads:[~2025-11-13 12:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 11:56 [PATCH 1/2] sandbox: Fix DT compiler address warnings in sandbox DTs Marek Vasut
2025-11-13 11:56 ` [PATCH 2/2] sandbox: Fix DT compiler pin " Marek Vasut
2025-11-13 12:54   ` Heiko Schocher [this message]
2025-11-21 10:57   ` Mattijs Korpershoek
2025-11-13 12:52 ` [PATCH 1/2] sandbox: Fix DT compiler address " Heiko Schocher
2025-11-21 10:56 ` Mattijs Korpershoek
2025-11-28 17:41 ` Tom Rini

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=5a76ffc8-c41e-b2ff-4d95-8f93048dfd21@nabladev.com \
    --to=hs@nabladev.com \
    --cc=ansuelsmth@gmail.com \
    --cc=clamor95@gmail.com \
    --cc=dinesh.maniyam@altera.com \
    --cc=glaroque@baylibre.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=mkorpershoek@kernel.org \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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