From: Adrian Hunter <adrian.hunter@intel.com>
To: alexandre.belloni@bootlin.com
Cc: Frank.Li@nxp.com, akhilrajeev@nvidia.com,
mukesh.savaliya@oss.qualcomm.com, rafael@kernel.org,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-pm@vger.kernel.org
Subject: [PATCH V4 00/14] i3c: Support IBI-based system wakeup
Date: Thu, 6 Aug 2026 16:18:43 +0300 [thread overview]
Message-ID: <20260806131857.119830-1-adrian.hunter@intel.com> (raw)
Hi
Intel LPSS I3C controllers support up to two I3C busses and can wake the
system from an In-Band Interrupt (IBI) via a PCI PME. Today that wakeup
capability lives only at the PCI function, with no way to express which
I3C device is actually responsible for waking the system, and no way for
user space to enable or disable wakeup on a per-device basis.
This series pushes the wakeup capability down to the individual I3C
devices and then aggregates the resulting wakeup state back up to the PCI
device.
An IBI-capable I3C device on a bus whose controller can wake the system
is marked as wakeup capable, so it can be managed through the standard
device wakeup framework (e.g. via power/wakeup in sysfs). When such a
device is enabled for wakeup, a wakeup event is reported each time it
queues an IBI.
At suspend time, the mipi-i3c-hci PCI driver aggregates the wakeup
configuration of the I3C devices across its HCI instances (up to two I3C
busses) and enables PCI wakeup (PME) only when at least one attached I3C
device is enabled as a wakeup source and has IBI enabled. This keeps
the PCI wakeup state in sync with the actual requirements of the devices
on the busses.
The series is organised as follows:
- Patch 1 fixes a pre-existing recursive acquisition of the bus rwsem
in i3c_master_register_new_i3c_devs(). The remaining patches add
work to that same function, so the locking is corrected first.
- Patches 2-7 fix use-after-free and unlocked accesses of the i3c_device
desc pointer. Moving device registration out from under the bus lock
in patch 1 is what makes it possible to take the bus lock in the
helpers that run during registration.
- Patches 8-11 add the generic I3C core support: an ibi_wakeup flag for
controllers, marking IBI-capable devices as wakeup capable, reporting
wakeup events on IBIs, a helper to query whether any device on a bus
has both wakeup and IBI enabled, and a fix to reject IBI requests
from devices that do not advertise IBI capability.
- Patches 12-14 wire this up for the mipi-i3c-hci driver: propagate the
aggregated I3C wakeup requirements to the PCI function, factor out
i3c_hci_sysdev() for the shared device lookup, and advertise IBI
wakeup capability when the underlying system device can wake the
system.
Note, since the PCI wakeup state is now derived from the wakeup
configuration of the attached I3C devices, the PCI device's
power/wakeup sysfs attribute no longer provides independent wakeup
control.
Changes in V4:
i3c: master: Fix recursive locking during device registration
Expanded the kernel-doc for the new struct i3c_device @node
member to note that it is only for use by
i3c_master_register_new_i3c_devs() and is not protected by a
lock.
i3c: master: Fix use-after-free of master->this
Also reset master->this and bus.cur_master to NULL on the
i3c_master_set_info() error path before freeing the allocated
device. Tidied up the commit message wording.
i3c: master: Support IBI-based wakeup capability
Shortened the comment about IBI-capable devices being wakeup
capable.
i3c: master: Add helper to query bus wakeup requirements
Renamed i3c_master_any_wakeup_enabled() to
i3c_master_has_wakeup_enabled_devs().
i3c: mipi-i3c-hci-pci: Propagate I3C wakeup requirements to PCI
Updated for the rename of i3c_master_any_wakeup_enabled() to
i3c_master_has_wakeup_enabled_devs().
i3c: mipi-i3c-hci: Factor out i3c_hci_sysdev()
Reworked the comment that moves with the code into kernel-doc,
and mentioned that in the commit message.
i3c: mipi-i3c-hci: Advertise IBI wakeup capability
Updated the i3c_hci_sysdev() kernel-doc to mention system PM and
wakeup, in place of the old comment tweak.
Added Frank Li's Reviewed-by and Mukesh Savaliya's Acked-by tags.
Changes in V3:
Added 6 patches (2-7) that fix use-after-free and unlocked accesses
of the i3c_device desc pointer. Moving device registration out from
under the bus lock in patch 1 is what allows that pointer to be
protected in the helpers that run during registration.
i3c: master: Fix recursive locking during device registration
Added Cc: stable@vger.kernel.org
i3c: master: Add helper to query bus wakeup requirements
Skip the master device explicitly. Noted in the kernel-doc that
wakeup enablement is user space policy, so the helper is meant to
be called from a system suspend callback.
Added Frank Li's Reviewed-by tags.
Rebased onto i3c/next.
Changes in V2:
Dropped the RFC tag.
i3c: master: Fix recursive locking during device registration
New patch
i3c: master: Support IBI-based wakeup capability
Dropped the redundant #include <linux/pm_wakeup.h>. That header
must not be included directly, and linux/device.h, which is
already included, provides device_set_wakeup_capable().
i3c: master: Add helper to query bus wakeup requirements
i3c_master_any_wakeup_enabled() now also requires the device to
have IBI enabled, not just system wakeup enabled, so that a
device with no active IBI request does not keep PCI PME enabled.
desc->ibi_lock is taken while checking. The commit message and
kernel-doc are updated to match.
Rebased onto i3c/next.
Adrian Hunter (14):
i3c: master: Fix recursive locking during device registration
i3c: Fix unlocked dereference of dev->desc in i3c_device_get_supported_xfer_mode()
i3c: master: Do not treat master device as a duplicate target
i3c: master: Fix use-after-free of master->this
i3c: Make dev->desc locking assumptions explicit
i3c: master: Fix potential UAF in i3c_device_uevent()
i3c: master: Fix potential UAF in i3c_device_match()
i3c: master: Support IBI-based wakeup capability
i3c: master: Report wakeup events for IBIs
i3c: master: Add helper to query bus wakeup requirements
i3c: master: Reject IBI requests from non-IBI-capable devices
i3c: mipi-i3c-hci-pci: Propagate I3C wakeup requirements to PCI
i3c: mipi-i3c-hci: Factor out i3c_hci_sysdev()
i3c: mipi-i3c-hci: Advertise IBI wakeup capability
drivers/i3c/device.c | 13 +--
drivers/i3c/internals.h | 5 +
drivers/i3c/master.c | 119 ++++++++++++++++-----
drivers/i3c/master/mipi-i3c-hci/core.c | 20 ++++
drivers/i3c/master/mipi-i3c-hci/dma.c | 15 +--
drivers/i3c/master/mipi-i3c-hci/hci.h | 2 +
drivers/i3c/master/mipi-i3c-hci/mipi-i3c-hci-pci.c | 23 +++-
include/linux/i3c/master.h | 6 ++
8 files changed, 155 insertions(+), 48 deletions(-)
Regards
Adrian
next reply other threads:[~2026-08-06 13:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 13:18 Adrian Hunter [this message]
2026-08-06 13:18 ` [PATCH V4 01/14] i3c: master: Fix recursive locking during device registration Adrian Hunter
2026-08-06 18:24 ` Frank Li
2026-08-06 13:18 ` [PATCH V4 02/14] i3c: Fix unlocked dereference of dev->desc in i3c_device_get_supported_xfer_mode() Adrian Hunter
2026-08-06 18:26 ` Frank Li
2026-08-06 13:18 ` [PATCH V4 03/14] i3c: master: Do not treat master device as a duplicate target Adrian Hunter
2026-08-06 13:18 ` [PATCH V4 04/14] i3c: master: Fix use-after-free of master->this Adrian Hunter
2026-08-06 18:30 ` Frank Li
2026-08-06 13:18 ` [PATCH V4 05/14] i3c: Make dev->desc locking assumptions explicit Adrian Hunter
2026-08-06 18:31 ` Frank Li
2026-08-06 13:18 ` [PATCH V4 06/14] i3c: master: Fix potential UAF in i3c_device_uevent() Adrian Hunter
2026-08-06 18:33 ` Frank Li
2026-08-06 13:18 ` [PATCH V4 07/14] i3c: master: Fix potential UAF in i3c_device_match() Adrian Hunter
2026-08-06 13:18 ` [PATCH V4 08/14] i3c: master: Support IBI-based wakeup capability Adrian Hunter
2026-08-06 18:58 ` Mukesh Savaliya
2026-08-06 13:18 ` [PATCH V4 09/14] i3c: master: Report wakeup events for IBIs Adrian Hunter
2026-08-06 18:35 ` Frank Li
2026-08-06 13:18 ` [PATCH V4 10/14] i3c: master: Add helper to query bus wakeup requirements Adrian Hunter
2026-08-06 18:46 ` Frank Li
2026-08-06 19:03 ` Mukesh Savaliya
2026-08-06 13:18 ` [PATCH V4 11/14] i3c: master: Reject IBI requests from non-IBI-capable devices Adrian Hunter
2026-08-06 13:18 ` [PATCH V4 12/14] i3c: mipi-i3c-hci-pci: Propagate I3C wakeup requirements to PCI Adrian Hunter
2026-08-06 18:42 ` Frank Li
2026-08-06 13:18 ` [PATCH V4 13/14] i3c: mipi-i3c-hci: Factor out i3c_hci_sysdev() Adrian Hunter
2026-08-06 18:44 ` Frank Li
2026-08-06 19:07 ` Mukesh Savaliya
2026-08-06 13:18 ` [PATCH V4 14/14] i3c: mipi-i3c-hci: Advertise IBI wakeup capability Adrian Hunter
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=20260806131857.119830-1-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=Frank.Li@nxp.com \
--cc=akhilrajeev@nvidia.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.com \
--cc=rafael@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox