From nobody Sun Feb 8 14:10:32 2026 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.18]) (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 517B42F693D; Thu, 29 Jan 2026 18:19:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.18 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769710745; cv=none; b=BC87u5aCz3oO7dcm41Z1ammvrSkhy2Yy5Bw5Q+MRhgb6LnGTH0HcpwbgJENx+dDkrYd6tBRlOAJVH+JcCHBuVZkXoRzqsK1yGOHO5w/fzyoZmiUod2LW0+WnXdgbKVQPTACR6wtfI8Aolk9ujd8RLB4QJOshNkssZ46/IiNw9UE= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769710745; c=relaxed/simple; bh=Vth7ZQ3l7iGCOJhyGFQCxUbjMiSgkkexgfCMAYp6YQs=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=frB50oKMMtUilk43RfZ00Sv3LnvuiTVxMWHizNgBfgqIBBlHCoT0v/mp1X46KLUxGXi9KhDQP0WXKqL0lNX0tp3wsjWrCYfi7xa5davK9wMg4GwI5a+WbIe4Os2Feculwh8yrfKsb8DmMzyqRltOQWoNs7QAcaaNsm2dM8Jn/ak= 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=Y4Lohu0z; arc=none smtp.client-ip=192.198.163.18 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="Y4Lohu0z" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1769710743; x=1801246743; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=Vth7ZQ3l7iGCOJhyGFQCxUbjMiSgkkexgfCMAYp6YQs=; b=Y4Lohu0zPWNnBDHNuDjx6CDWWzwYPMj36ReowZIihWqZnnhfckajz0Mt pGlm1iFU9qCJNPSeC39azGBMr/S2WZu55zhaAQbJfsQIAJB2xtK3qChZq kVNk9PDEedtmi3EWB383whrYBNpq4DeZ8/VHK7XEqtuYcJ07lXtngr+88 atYV9U2H1HiOcf1vBf3Gt9vBvjzgOJ9c/sIxUP7IzoiN1E69zTl54mT7a Z46acgTtf4n/mXxIHmvOjrWNxkaOjTyyR4kTeLY5B4lMNpdx/V/8/eQ9g DRL0VxsZpymBw1hsIsJu7Y9zqF3IuA6QTcxXAwYpBN7SUD5ZA+bkQ4B7a w==; X-CSE-ConnectionGUID: 80BBKQ8QTL6fWjb1chAilw== X-CSE-MsgGUID: 34zcYWm1TkifsGurYztbqQ== X-IronPort-AV: E=McAfee;i="6800,10657,11686"; a="70158289" X-IronPort-AV: E=Sophos;i="6.21,261,1763452800"; d="scan'208";a="70158289" Received: from fmviesa007.fm.intel.com ([10.60.135.147]) by fmvoesa112.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jan 2026 10:19:03 -0800 X-CSE-ConnectionGUID: R7wiPTGETneIcE3M7sRjbg== X-CSE-MsgGUID: V3hjQdqDQue9OnI1CA7roQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.21,261,1763452800"; d="scan'208";a="208255299" Received: from egrumbac-mobl6.ger.corp.intel.com (HELO ahunter6-desk) ([10.245.245.96]) by fmviesa007-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jan 2026 10:19:01 -0800 From: Adrian Hunter To: alexandre.belloni@bootlin.com Cc: Frank.Li@nxp.com, linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org Subject: [PATCH 4/7] i3c: mipi-i3c-hci: Add quirk to allow IBI while runtime suspended Date: Thu, 29 Jan 2026 20:18:38 +0200 Message-ID: <20260129181841.130864-5-adrian.hunter@intel.com> X-Mailer: git-send-email 2.51.0 In-Reply-To: <20260129181841.130864-1-adrian.hunter@intel.com> References: <20260129181841.130864-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: quoted-printable Content-Type: text/plain; charset="utf-8" Some I3C controllers can be automatically runtime-resumed in order to handle in-band interrupts (IBIs), meaning that runtime suspend does not need to be blocked when IBIs are enabled. For example, a PCI-attached controller in a low-power state may generate a Power Management Event (PME) when the SDA line is pulled low to signal the START condition of an IBI. The PCI subsystem will then runtime-resume the device, allowing the IBI to be received without requiring the controller to remain active. Introduce a new quirk, HCI_QUIRK_RPM_IBI_ALLOWED, so that drivers can opt-in to this capability via driver data. Signed-off-by: Adrian Hunter --- drivers/i3c/master/mipi-i3c-hci/core.c | 3 +++ drivers/i3c/master/mipi-i3c-hci/hci.h | 1 + 2 files changed, 4 insertions(+) diff --git a/drivers/i3c/master/mipi-i3c-hci/core.c b/drivers/i3c/master/mi= pi-i3c-hci/core.c index e925584113d1..ec4dbe64c35e 100644 --- a/drivers/i3c/master/mipi-i3c-hci/core.c +++ b/drivers/i3c/master/mipi-i3c-hci/core.c @@ -959,6 +959,9 @@ static int i3c_hci_probe(struct platform_device *pdev) if (hci->quirks & HCI_QUIRK_RPM_ALLOWED) i3c_hci_rpm_enable(&pdev->dev); =20 + if (hci->quirks & HCI_QUIRK_RPM_IBI_ALLOWED) + hci->master.rpm_ibi_allowed =3D true; + return i3c_master_register(&hci->master, &pdev->dev, &i3c_hci_ops, false); } =20 diff --git a/drivers/i3c/master/mipi-i3c-hci/hci.h b/drivers/i3c/master/mip= i-i3c-hci/hci.h index 6035f74212db..819328a85b84 100644 --- a/drivers/i3c/master/mipi-i3c-hci/hci.h +++ b/drivers/i3c/master/mipi-i3c-hci/hci.h @@ -146,6 +146,7 @@ struct i3c_hci_dev_data { #define HCI_QUIRK_OD_PP_TIMING BIT(3) /* Set OD and PP timings for AMD p= latforms */ #define HCI_QUIRK_RESP_BUF_THLD BIT(4) /* Set resp buf thld to 0 for AMD= platforms */ #define HCI_QUIRK_RPM_ALLOWED BIT(5) /* Runtime PM allowed */ +#define HCI_QUIRK_RPM_IBI_ALLOWED BIT(6) /* IBI and Hot-Join allowed whil= e runtime suspended */ =20 /* global functions */ void mipi_i3c_hci_resume(struct i3c_hci *hci); --=20 2.51.0