From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "David Nyström" <david.nystrom@est.tech>
Cc: 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 13:53:04 +0100 [thread overview]
Message-ID: <aXIdsGgHQQPKy4Ok@shikoro> (raw)
In-Reply-To: <20260122-i3c_rescan-v1-1-0c17071e232b@est.tech>
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?
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "David Nyström" <david.nystrom@est.tech>
Cc: 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 13:53:04 +0100 [thread overview]
Message-ID: <aXIdsGgHQQPKy4Ok@shikoro> (raw)
In-Reply-To: <20260122-i3c_rescan-v1-1-0c17071e232b@est.tech>
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?
next prev parent reply other threads:[~2026-01-22 12:53 UTC|newest]
Thread overview: 8+ 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 11:36 ` David Nyström
2026-01-22 12:53 ` Wolfram Sang [this message]
2026-01-22 12:53 ` Wolfram Sang
2026-01-22 15:47 ` David Nyström
2026-01-22 15:47 ` David Nyström
2026-01-22 16:00 ` Frank Li
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=aXIdsGgHQQPKy4Ok@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=david.nystrom@est.tech \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.