From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 163E73B585F for ; Wed, 1 Jul 2026 20:06:12 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.15 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782936373; cv=none; b=YXyukJ5+nNjc8Bcnil5QLTxq/6ywsRCBom1o/0RWnDmM4K+dUTNVXh6D274JIt6Z7if9xtbivWk+Kh8gCwcFo1ZpSAXuL7dpNWJpoRpBXULYYKav28QdqVUOOCs06SbeUSVRgVz41aAsUrkg5EyYtSbL1fCH//ObmEkHOF/i5FU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782936373; c=relaxed/simple; bh=fUJQmeO30dZmNsYhdWgV/Cb07B9pDkcedp1zvYifsZg=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=qGAp+A0/dJ7UYZGS3bIJ4QX0NJzdOC8/AluYWEWjSzNZ+7IX7tY5CA9fOXokDXmkVfdsfwDyd2nhnpblZmiPq3JgPheSAQeXwFn0RcXUPtBt4kpyK0H4coSHfzGf+7SYyr/00nji07wT+nCwiggeai8IN4tJz1WkIsfcQ9uA9fY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=LfpqSfTt; arc=none smtp.client-ip=192.198.163.15 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="LfpqSfTt" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1782936372; x=1814472372; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=fUJQmeO30dZmNsYhdWgV/Cb07B9pDkcedp1zvYifsZg=; b=LfpqSfTtSBfgjIhruUo4CQnAFxczCYQ7dJWHK9jZ4NYWZCe0i1QmOvlG JL55Zxs5r/AjJbM7FKNG9CT7T2kxI0tHgIHVcUZLEL4Z7PQI2LJE98T/N x+VmCBFu0xS+u5vfJKjWGvy2UB/areboP/oannJc0qZXq14Qcj9/u0Mjp uzHH3uWz6UppaqnZvN3YbEYqbuKVqv8qd4Ul50/Uv3vhpU/oTUGJUTZ6m CI/ml5UsKx5vT+cOSy2Xn9fABEx7rsgRnTP7Xh0FYkCBDLmbg7UL2u5Mr bnZUrzS7pY6/P/ysFKQ2xCAeyH07lPBg5Atpn3Tx8QVs7t9AWvg6DkMVN w==; X-CSE-ConnectionGUID: CHdsqzfURLixW1x/nL9i2w== X-CSE-MsgGUID: vimIF5GgTKKlboG3m+VYog== X-IronPort-AV: E=McAfee;i="6800,10657,11834"; a="83812911" X-IronPort-AV: E=Sophos;i="6.25,142,1779174000"; d="scan'208";a="83812911" Received: from orviesa007.jf.intel.com ([10.64.159.147]) by fmvoesa109.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Jul 2026 13:06:12 -0700 X-CSE-ConnectionGUID: n8KdOeslS2CvHouqDLVrEA== X-CSE-MsgGUID: Qf9tePqYQd+LdzJTJM0evw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.25,142,1779174000"; d="scan'208";a="252805028" Received: from conormcd-mobl2.ger.corp.intel.com (HELO ahunter6-desk) ([10.245.244.30]) by orviesa007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Jul 2026 13:06:10 -0700 From: Adrian Hunter To: alexandre.belloni@bootlin.com Cc: Frank.Li@nxp.com, rafael@kernel.org, linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pci@lists.infradead.org, linux-pm@lists.infradead.org Subject: [PATCH RFC 2/7] i3c: master: Report wakeup events for IBIs Date: Wed, 1 Jul 2026 23:05:47 +0300 Message-ID: <20260701200552.220042-3-adrian.hunter@intel.com> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260701200552.220042-1-adrian.hunter@intel.com> References: <20260701200552.220042-1-adrian.hunter@intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Organization: Intel Finland Oy, Registered Address: c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo, Business Identity Code: 0357606 - 4, Domiciled in Helsinki Content-Transfer-Encoding: 8bit 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 --- drivers/i3c/master.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c index a47e2924bb70..a36f9b617cbf 100644 --- a/drivers/i3c/master.c +++ b/drivers/i3c/master.c @@ -2994,6 +2994,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 @@ -3007,6 +3010,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