linux-i3c.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Jack Chen <zenghuchen@google.com>
Cc: Jesus Sanchez-Palencia <jesussanp@google.com>,
	linux-kernel@vger.kernel.org,
	Mark Slevinsky <markslevinsky@google.com>,
	linux-i3c@lists.infradead.org
Subject: Re: [PATCH] I3C: export SETDASA method
Date: Sun, 11 Dec 2022 21:29:32 +0100	[thread overview]
Message-ID: <167079040326.15858.302543275649765579.b4-ty@bootlin.com> (raw)
In-Reply-To: <20221207205059.3848851-1-zenghuchen@google.com>

On Wed, 7 Dec 2022 15:50:59 -0500, Jack Chen wrote:
> Because not all I3C drivers have the hot-join feature ready, and
> especially not all I3C devices support hot-join feature, exporting
> SETDASA method could be useful. With this function, the I3C controller
> could perform a DAA to I3C devices when users decide to turn these I3C
> devices off and on again during run-time.
> 
> Tested: This change has been tested with turnning off an I3C device and
> turning on it again during run-time. The device driver calls SETDASA
> method to perform DAA to the device. And communication between I3C
> controller and device is set up again correctly.
> 
> [...]

Applied, thanks!

[1/1] I3C: export SETDASA method
      commit: 672825cd2823a0cee4687ce80fef5b702ff3caa3

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

      reply	other threads:[~2022-12-11 20:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 20:50 [PATCH] I3C: export SETDASA method Jack Chen
2022-12-11 20:29 ` 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=167079040326.15858.302543275649765579.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).