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 09/14] i3c: master: Report wakeup events for IBIs
Date: Thu, 6 Aug 2026 16:18:52 +0300 [thread overview]
Message-ID: <20260806131857.119830-10-adrian.hunter@intel.com> (raw)
In-Reply-To: <20260806131857.119830-1-adrian.hunter@intel.com>
An I3C device configured as a wakeup source can wake the system by
generating an In-Band Interrupt (IBI).
When an IBI is queued for processing, record a wakeup event for the
device if wakeup is enabled. Use a 100 ms processing interval to give
the I3C device driver time to process the IBI.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
---
Changes in V4:
None
Changes in V2 and V3:
None
drivers/i3c/master.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
index 2616354dbe54..6c5341491944 100644
--- a/drivers/i3c/master.c
+++ b/drivers/i3c/master.c
@@ -3384,6 +3384,9 @@ static void i3c_master_unregister_i3c_devs(struct i3c_master_controller *master)
}
}
+/* Approximate time for IBI handler to run */
+#define I3C_WAKEUP_PROCESSING_TIME_MS 100
+
/**
* i3c_master_queue_ibi() - Queue an IBI
* @dev: the device this IBI is coming from
@@ -3397,6 +3400,9 @@ void i3c_master_queue_ibi(struct i3c_dev_desc *dev, struct i3c_ibi_slot *slot)
if (!dev->ibi || !slot)
return;
+ if (device_may_wakeup(&dev->dev->dev))
+ pm_wakeup_event(&dev->dev->dev, I3C_WAKEUP_PROCESSING_TIME_MS);
+
atomic_inc(&dev->ibi->pending_ibis);
queue_work(dev->ibi->wq, &slot->work);
}
--
2.53.0
--
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: 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 09/14] i3c: master: Report wakeup events for IBIs
Date: Thu, 6 Aug 2026 16:18:52 +0300 [thread overview]
Message-ID: <20260806131857.119830-10-adrian.hunter@intel.com> (raw)
In-Reply-To: <20260806131857.119830-1-adrian.hunter@intel.com>
An I3C device configured as a wakeup source can wake the system by
generating an In-Band Interrupt (IBI).
When an IBI is queued for processing, record a wakeup event for the
device if wakeup is enabled. Use a 100 ms processing interval to give
the I3C device driver time to process the IBI.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
---
Changes in V4:
None
Changes in V2 and V3:
None
drivers/i3c/master.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
index 2616354dbe54..6c5341491944 100644
--- a/drivers/i3c/master.c
+++ b/drivers/i3c/master.c
@@ -3384,6 +3384,9 @@ static void i3c_master_unregister_i3c_devs(struct i3c_master_controller *master)
}
}
+/* Approximate time for IBI handler to run */
+#define I3C_WAKEUP_PROCESSING_TIME_MS 100
+
/**
* i3c_master_queue_ibi() - Queue an IBI
* @dev: the device this IBI is coming from
@@ -3397,6 +3400,9 @@ void i3c_master_queue_ibi(struct i3c_dev_desc *dev, struct i3c_ibi_slot *slot)
if (!dev->ibi || !slot)
return;
+ if (device_may_wakeup(&dev->dev->dev))
+ pm_wakeup_event(&dev->dev->dev, I3C_WAKEUP_PROCESSING_TIME_MS);
+
atomic_inc(&dev->ibi->pending_ibis);
queue_work(dev->ibi->wq, &slot->work);
}
--
2.53.0
next prev parent reply other threads:[~2026-08-06 13:19 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 13:18 [PATCH V4 00/14] i3c: Support IBI-based system wakeup Adrian Hunter
2026-08-06 13:18 ` Adrian Hunter
2026-08-06 13:18 ` [PATCH V4 01/14] i3c: master: Fix recursive locking during device registration Adrian Hunter
2026-08-06 13:18 ` Adrian Hunter
2026-08-06 13:39 ` sashiko-bot
2026-08-06 13:39 ` sashiko-bot
2026-08-06 16:46 ` Adrian Hunter
2026-08-06 16:46 ` Adrian Hunter
2026-08-06 18:24 ` Frank Li
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 13:18 ` Adrian Hunter
2026-08-06 13:38 ` sashiko-bot
2026-08-06 13:38 ` sashiko-bot
2026-08-06 18:26 ` Frank Li
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 ` Adrian Hunter
2026-08-06 13:40 ` sashiko-bot
2026-08-06 13:40 ` sashiko-bot
2026-08-06 13:18 ` [PATCH V4 04/14] i3c: master: Fix use-after-free of master->this Adrian Hunter
2026-08-06 13:18 ` Adrian Hunter
2026-08-06 13:39 ` sashiko-bot
2026-08-06 13:39 ` sashiko-bot
2026-08-06 18:30 ` Frank Li
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 13:18 ` Adrian Hunter
2026-08-06 13:39 ` sashiko-bot
2026-08-06 13:39 ` sashiko-bot
2026-08-06 18:31 ` Frank Li
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 13:18 ` Adrian Hunter
2026-08-06 13:34 ` sashiko-bot
2026-08-06 13:34 ` sashiko-bot
2026-08-06 18:33 ` Frank Li
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 ` Adrian Hunter
2026-08-06 13:45 ` sashiko-bot
2026-08-06 13:45 ` sashiko-bot
2026-08-06 17:13 ` Adrian Hunter
2026-08-06 17:13 ` Adrian Hunter
2026-08-06 13:18 ` [PATCH V4 08/14] i3c: master: Support IBI-based wakeup capability Adrian Hunter
2026-08-06 13:18 ` Adrian Hunter
2026-08-06 13:31 ` sashiko-bot
2026-08-06 13:31 ` sashiko-bot
2026-08-06 18:58 ` Mukesh Savaliya
2026-08-06 18:58 ` Mukesh Savaliya
2026-08-06 13:18 ` Adrian Hunter [this message]
2026-08-06 13:18 ` [PATCH V4 09/14] i3c: master: Report wakeup events for IBIs Adrian Hunter
2026-08-06 13:49 ` sashiko-bot
2026-08-06 13:49 ` sashiko-bot
2026-08-06 17:16 ` Adrian Hunter
2026-08-06 17:16 ` Adrian Hunter
2026-08-06 18:35 ` Frank Li
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 13:18 ` Adrian Hunter
2026-08-06 13:29 ` sashiko-bot
2026-08-06 13:29 ` sashiko-bot
2026-08-06 18:46 ` Frank Li
2026-08-06 18:46 ` Frank Li
2026-08-06 19:03 ` Mukesh Savaliya
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 ` Adrian Hunter
2026-08-06 13:41 ` sashiko-bot
2026-08-06 13:41 ` sashiko-bot
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 13:18 ` Adrian Hunter
2026-08-06 13:56 ` sashiko-bot
2026-08-06 13:56 ` sashiko-bot
2026-08-06 17:20 ` Adrian Hunter
2026-08-06 17:20 ` Adrian Hunter
2026-08-06 18:42 ` Frank Li
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 13:18 ` Adrian Hunter
2026-08-06 13:46 ` sashiko-bot
2026-08-06 13:46 ` sashiko-bot
2026-08-06 18:44 ` Frank Li
2026-08-06 18:44 ` Frank Li
2026-08-06 19:07 ` Mukesh Savaliya
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
2026-08-06 13:18 ` Adrian Hunter
2026-08-06 13:54 ` sashiko-bot
2026-08-06 13:54 ` sashiko-bot
2026-08-06 17:37 ` Adrian Hunter
2026-08-06 17:37 ` 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-10-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 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.