linux-kernel - Re: [PATCH] i3c: master: Add WO sysfs option to re-DDA bus.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aXJJtgtZ59ZxJC0b@lizhi-Precision-Tower-5810>
Date: Thu, 22 Jan 2026 11:00:54 -0500
From: Frank Li <Frank.li@....com>
To: David Nyström <david.nystrom@....tech>
Cc: Wolfram Sang <wsa+renesas@...g-engineering.com>,
	Alexandre Belloni <alexandre.belloni@...tlin.com>,
	linux-i3c@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] i3c: master: Add WO sysfs option to re-DDA bus.

On Thu, Jan 22, 2026 at 04:47:23PM +0100, David Nyström wrote:
>
> 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.

It is useful. Please improve commit message.

Frank