From: Sascha Hauer <s.hauer@pengutronix.de>
To: "open list:BAREBOX" <barebox@lists.infradead.org>
Subject: [PATCH 0/3] I2C: assign bus numbers from device tree
Date: Fri, 25 Oct 2024 09:30:23 +0200 [thread overview]
Message-ID: <20241025-i2c-busnum-v1-0-332d9257eafe@pengutronix.de> (raw)
Like done with SPI controllers already let's assign the I2C bus numbers
from device tree as well. This avoids confusing bus numbers when the
probe order doesn't match the intended bus number ordering or when
other I2C busses with dynamically assigned numbers are probed in
between.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (3):
i2c: set adapter.nr explicitly to -1
i2c: get adapter.nr from device tree
i2c: start dynamic I2C bus numbers at 32
drivers/i2c/busses/i2c-at91.c | 2 +-
drivers/i2c/busses/i2c-bcm283x.c | 2 +-
drivers/i2c/busses/i2c-cadence.c | 2 +-
drivers/i2c/busses/i2c-designware.c | 2 +-
drivers/i2c/busses/i2c-imx.c | 2 +-
drivers/i2c/busses/i2c-mv64xxx.c | 2 +-
drivers/i2c/busses/i2c-rockchip.c | 2 +-
drivers/i2c/busses/i2c-stm32.c | 2 +-
drivers/i2c/busses/i2c-tegra.c | 2 +-
drivers/i2c/i2c.c | 5 ++++-
10 files changed, 13 insertions(+), 10 deletions(-)
---
base-commit: e55e492573e33823f25935ee00fe7fa7bf2c5c90
change-id: 20241025-i2c-busnum-bd3bdee6c0c3
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next reply other threads:[~2024-10-25 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 7:30 Sascha Hauer [this message]
2024-10-25 7:30 ` [PATCH 1/3] i2c: set adapter.nr explicitly to -1 Sascha Hauer
2024-10-25 13:43 ` Alexander Shiyan
2024-10-28 12:11 ` Sascha Hauer
2024-10-25 7:30 ` [PATCH 2/3] i2c: get adapter.nr from device tree Sascha Hauer
2024-10-25 7:30 ` [PATCH 3/3] i2c: start dynamic I2C bus numbers at 32 Sascha Hauer
2024-10-28 12:11 ` [PATCH 0/3] I2C: assign bus numbers from device tree Sascha Hauer
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=20241025-i2c-busnum-v1-0-332d9257eafe@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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