From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: linux-i3c@lists.infradead.org, Jamie Iles <quic_jiles@quicinc.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH 0/2] i3c: support for dynamically added i2c devices
Date: Fri, 4 Mar 2022 11:35:54 +0100 [thread overview]
Message-ID: <164639013739.20219.13627775120905663769.b4-ty@bootlin.com> (raw)
In-Reply-To: <20220117174816.1963463-1-quic_jiles@quicinc.com>
On Mon, 17 Jan 2022 17:48:14 +0000, Jamie Iles wrote:
> Devices are currently added at controller initialization time with
> boardinfo, but the i2c subsystem also supports dynamically adding
> devices through a variety of mechanisms including user-space through
> sysfs, device tree overlays and ACPI.
>
> This small series decouples registration from the boardinfo and then
> adds a notifier to add the devices at runtime. A future series will
> build on this to allow adding the I2C devices through ACPI.
>
> [...]
Applied, thanks!
[1/2] i3c: remove i2c board info from i2c_dev_desc
commit: 97a82882d8529c18ff15a0b5396d8c4bd2a36157
[2/2] i3c: support dynamically added i2c devices
commit: cd5883f7e933764e2ddddd9cbb0f7ce18df127c4
Best regards,
--
Alexandre Belloni <alexandre.belloni@bootlin.com>
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2022-03-04 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 17:48 [PATCH 0/2] i3c: support for dynamically added i2c devices Jamie Iles
2022-01-17 17:48 ` [PATCH 1/2] i3c: remove i2c board info from i2c_dev_desc Jamie Iles
2022-01-17 17:48 ` [PATCH 2/2] i3c: support dynamically added i2c devices Jamie Iles
2022-03-04 10:35 ` Alexandre Belloni [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=164639013739.20219.13627775120905663769.b4-ty@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=linux-i3c@lists.infradead.org \
--cc=quic_jiles@quicinc.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).