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 CC2E1448384 for ; Mon, 14 Sep 2026 11:30:32 +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=1789385435; cv=none; b=AnH7lFrftQyXHLkDUverr+Pz7on66FzK/rG8VCl5OyudMq7gAv2UQHHv+OhENd61fUqaKzj5/tP504NCc4TAx7DrMqEefa0z+pmVMPj5lk3zCZwEpXZPoIYlP0frxaTJmWs7DyPSdz/QR9CqCJgDaZcGoChx3jcxMJL2vy0T+8Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789385435; c=relaxed/simple; bh=A6ansUeDN7k/9sT0TmvrZh2giOrXschlK/7xkmr3exo=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=MKwNmMuVQFDm9hu5qyRWClYUXSLhVAg0JnfPmtKxcrB97pVMpYHDLSk0WqvCwx1n84MnvBJAFseFyweG7Ihd9i8dwxv4d98ZZcAAi9K0oWVlcVvPIKbHTANowbuWor/by4UtVvLRTIG4U9AcT9q3/moiGJ5aCCitFMYI1BNq52g= 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=ihHC03uV; 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="ihHC03uV" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1789385433; x=1820921433; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=A6ansUeDN7k/9sT0TmvrZh2giOrXschlK/7xkmr3exo=; b=ihHC03uVgVgeCpkPG0340sYERuoi2hnLsRedNg5AjBPbJtO7Zp7iCZwc emKXoNxx3nGwLemYHmVr/yZrIRIlTsdvwOZnf0RsbsO809+HfhSHJ5CKi wFANPyGD/SUp4T6IcsJxav0KV595p2B82rdZ4sQItucKpuUISiPTEwT90 IUXhz6Cvtx1s+eAjTdn0Vm91uFRg2ea5mnUSItoMIYpHxALN+7+aywx75 eFP+6d0TFVy/IHCLTL3l+x3SbX5nffU64HIIG1/9A4o35Yb0Xc1LFsj6s ZrcNRGcN7BtEESBi2G9EFRS706QgYsJji7XQ0OuCfZIpJp/mvtyu99fGV g==; X-CSE-ConnectionGUID: 9Yo1RAPWThWauXy4mucTEg== X-CSE-MsgGUID: vqkwlORFTZOktIv1B13yQg== X-IronPort-AV: E=McAfee;i="6800,10657,11904"; a="89864455" X-IronPort-AV: E=Sophos;i="6.27,102,1787036400"; d="scan'208";a="89864455" Received: from orviesa009.jf.intel.com ([10.64.159.149]) by fmvoesa109.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2026 04:30:32 -0700 X-CSE-ConnectionGUID: 4jnyY0tTSX6vwZNp/n99HQ== X-CSE-MsgGUID: vw1VwUPxRluwSzaibhloIA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.27,102,1787036400"; d="scan'208";a="273133121" Received: from mkosciow-mobl1.ger.corp.intel.com (HELO ahunter6-desk) ([10.245.245.35]) by orviesa009-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2026 04:30:31 -0700 From: Adrian Hunter To: alexandre.belloni@bootlin.com Cc: Frank.Li@nxp.com, billy_tsai@aspeedtech.com, linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH 08/17] i3c: mipi-i3c-hci: Fix runtime PM violation in i3c_hci_free_ibi() Date: Mon, 14 Sep 2026 14:29:54 +0300 Message-ID: <20260914113003.183150-9-adrian.hunter@intel.com> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260914113003.183150-1-adrian.hunter@intel.com> References: <20260914113003.183150-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 i3c_hci_free_ibi() calls __i3c_hci_disable_ibi(), but the latter requires runtime PM to be resumed. The ->free_ibi() callback does not guarantee that condition. The cases where ->free_ibi() may be called without a preceding ->disable_ibi() do not require re-enabling runtime PM handling: - runtime resume failed in i3c_dev_free_ibi_locked(), so it skips the IBI disable but still proceeds to call ->free_ibi() - the device has been re-enumerated under a new dynamic address in __i3c_master_add_i3c_dev_locked(), which tears down the old device descriptor and deliberately clears olddev->ibi->enabled (to avoid sending a DISEC to the stale old address) before calling i3c_dev_free_ibi_locked(). As a result ->free_ibi() is reached with neither a hardware IBI disable nor runtime PM resumed. In both cases the important requirement is to prevent further IBI processing for the device. That can be done without accessing hardware by removing the device from the ibi_devs[] table. Replace the call to __i3c_hci_disable_ibi() with clearing the corresponding ibi_devs[] entry under the controller lock. Fixes: 650716f23eac4 ("i3c: mipi-i3c-hci: Fix race in i3c_hci_addr_to_dev()") Signed-off-by: Adrian Hunter --- drivers/i3c/master/mipi-i3c-hci/core.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/i3c/master/mipi-i3c-hci/core.c b/drivers/i3c/master/mipi-i3c-hci/core.c index f6a34ce7a295..b9b20797d045 100644 --- a/drivers/i3c/master/mipi-i3c-hci/core.c +++ b/drivers/i3c/master/mipi-i3c-hci/core.c @@ -675,11 +675,13 @@ static void __i3c_hci_disable_ibi(struct i3c_hci *hci, struct i3c_dev_desc *dev) static void i3c_hci_free_ibi(struct i3c_dev_desc *dev) { + struct i3c_hci_dev_data *dev_data = i3c_dev_get_master_data(dev); struct i3c_master_controller *m = i3c_dev_get_master(dev); struct i3c_hci *hci = to_i3c_hci(m); - /* Must ensure the IBI has been disabled */ - __i3c_hci_disable_ibi(hci, dev); + /* Must ensure IBIs for this device will no longer be processed */ + scoped_guard(spinlock_irqsave, &hci->lock) + hci->ibi_devs[dev_data->dat_idx] = NULL; hci->io->free_ibi(hci, dev); } -- 2.53.0