From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Jack Chen <zenghuchen@google.com>
Cc: linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
Jesus Sanchez-Palencia <jesussanp@google.com>,
Mark Slevinsky <markslevinsky@google.com>
Subject: Re: [PATCH] i3c: transfer pid from boardinfo to device info
Date: Tue, 10 Jan 2023 14:43:33 +0100 [thread overview]
Message-ID: <167335818715.550702.4568478412316741935.b4-ty@bootlin.com> (raw)
In-Reply-To: <20230105212952.56321-1-zenghuchen@google.com>
On Thu, 05 Jan 2023 16:29:52 -0500, Jack Chen wrote:
> I3C device PID could be defined in device tree and stored in
> i3c_dev_boardinfo. It should be passed to i3c_device_info when
> allocating a i3c_dev_desc.
> Rational behind this change is: when users decide to use SETDASA to
> assign a dynamic address with exactly the original static address, in
> step of i3c_master_reattach_i3c_dev, this address is checked to be
> taken. Then device information retrieving step is skipped. As a result,
> though the i3c device is registered correctly, its device driver could
> not be probed.
>
> [...]
Applied, thanks!
[1/1] i3c: transfer pid from boardinfo to device info
commit: e826acc18bc7bdf4278bf8928caa3a0cd4065432
Best regards,
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2023-01-10 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 21:29 [PATCH] i3c: transfer pid from boardinfo to device info Jack Chen
2023-01-10 13:43 ` 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=167335818715.550702.4568478412316741935.b4-ty@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=jesussanp@google.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markslevinsky@google.com \
--cc=zenghuchen@google.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 NNTP newsgroup(s).