From: "David Nyström" <david.nystrom@est.tech>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "David Nyström" <david.nystrom@est.tech>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Frank Li" <Frank.Li@nxp.com>,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i3c: master: Add WO sysfs option to re-DDA bus.
Date: Thu, 22 Jan 2026 16:47:23 +0100 (CET) [thread overview]
Message-ID: <6b15a03c-57ae-021a-581c-4f83e58842e8@est.tech> (raw)
In-Reply-To: <aXIdsGgHQQPKy4Ok@shikoro>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
On Thu, 22 Jan 2026, Wolfram Sang wrote:
> On Thu, Jan 22, 2026 at 12:36:30PM +0100, David Nyström wrote:
>> Add ability to rescan the i3c bus from userspace, i.e. provoke a DDA.
>
> Your are describing what you do but what is missing is why you want the
> change. What is the use case?
The usecase would be an i3cdev userspace driver for a device with
broken hotjoin support.
The device requires FW loading(userspace framework) before it will respond
to DAA, and is thus not registered during initial bus probe.
I guess a similiar problem would apply if hot-join is bus disabled
via sysfs, and resume hook DDA runs before i3c devices are powered up properly.
A bit of a niche usecase, I know.
I found it to be usable though, but perhaps this is better placed in
debugfs in case its too much of an eyesore for the stable ABI.
[-- Attachment #2: Type: text/plain, Size: 111 bytes --]
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2026-03-11 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 11:36 [PATCH] i3c: master: Add WO sysfs option to re-DDA bus David Nyström
2026-01-22 12:53 ` Wolfram Sang
2026-01-22 15:47 ` David Nyström [this message]
2026-01-22 16:00 ` Frank Li
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=6b15a03c-57ae-021a-581c-4f83e58842e8@est.tech \
--to=david.nystrom@est.tech \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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