mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "open list:BAREBOX" <barebox@lists.infradead.org>,
	 Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 0/3] I2C: assign bus numbers from device tree
Date: Mon, 28 Oct 2024 13:11:46 +0100	[thread overview]
Message-ID: <173011750675.318927.7359171537224061702.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20241025-i2c-busnum-v1-0-332d9257eafe@pengutronix.de>


On Fri, 25 Oct 2024 09:30:23 +0200, Sascha Hauer wrote:
> 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.
> 
> 
> [...]

Applied, thanks!

[1/3] i2c: set adapter.nr explicitly to -1
      https://git.pengutronix.de/cgit/barebox/commit/?id=5b167ad520c4 (link may not be stable)
[2/3] i2c: get adapter.nr from device tree
      https://git.pengutronix.de/cgit/barebox/commit/?id=b4746725454c (link may not be stable)
[3/3] i2c: start dynamic I2C bus numbers at 32
      https://git.pengutronix.de/cgit/barebox/commit/?id=79357f8b965a (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2024-10-28 12:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25  7:30 Sascha Hauer
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 ` Sascha Hauer [this message]

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=173011750675.318927.7359171537224061702.b4-ty@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