From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] spi: dt-bindings: Relax node name suffixes again
Date: Fri, 18 Sep 2026 15:00:33 -0500 [thread overview]
Message-ID: <20260918200033.GA1667835-robh@kernel.org> (raw)
In-Reply-To: <60988ce9c4913014e255ecbe127e93374f6a2295.1789570538.git.geert@linux-m68k.org>
On Wed, Sep 16, 2026 at 05:18:27PM +0200, Geert Uytterhoeven wrote:
> From: Geert Uytterhoeven <geert+renesas@glider.be>
>
> An SPI bus node name can have either a unit address, or a suffix.
> Commit c4fb6880edc15866 ("spi: dt-bindings: restrict node name
> suffixes") restricted these suffixes to decimal numbers.
> However, SPI bus node names with suffixes are typically used for
> board-level bit-banged SPI busses ("spi-gpio"), which live at the root
> of the device tree. Limiting their node names to numbers is prone to
> conflicts, and may cause silent overwrites, especially when a stack of
> sub-boards or expansion boards is involved.
How is that commit an issue 3 years later?
I've commented on the case which I guess prompted this patch.
BTW, "spi-gpio" or "i2c-gpio" are not good names because you can have
more than 1 instance.
>
> Hence relax node name suffixes to alphanumerical characters, so users
> can write more descriptive SPI bus names, which are less prone to
> conflicts.
>
> While at it, reject empty unit addresses.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202609150228.Nh4nZzbQ-lkp@intel.com
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Other subsystems (regulator, i2c) had similar issues, and numbered
> regulators caused conflicts before, see e.g. commit 45f5d5a9e34d3fe4
> ("arm64: dts: renesas: r8a77995: draak: Fix backlight regulator name").
I2C was a case of "too many to fix". Maybe time to revisit that.
Regulator binding is a unicorn and not a bus. I really want standard
names for buses given that's the only way to identify them generically.
Rob
next prev parent reply other threads:[~2026-09-18 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 15:18 [PATCH] spi: dt-bindings: Relax node name suffixes again Geert Uytterhoeven
2026-09-18 20:00 ` Rob Herring [this message]
2026-09-21 7:25 ` 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=20260918200033.GA1667835-robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=marek.vasut+renesas@mailbox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.