From nobody Sun Feb 8 21:46:45 2026 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.16]) (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 7C2F146AF31; Wed, 21 Jan 2026 09:23:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.16 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768987420; cv=none; b=Bs+07JCJV/mi5DRLhMp5qsqY2r99cBhI0x0shGqpgho1BKhNBafDXW0pKYRQyNNyOs9MAFiaePTHRIhSNy9akvSKPeYvXBi7Xy/gybOUjufPqW3Bp6K48nMp2aLkhRYa02MGIXBbZmtttS9UZIfuCwo117uzzzycjrW5BDryyKE= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768987420; c=relaxed/simple; bh=G1GyKVSX9uKD79xYXrL1AswlRkuNmQ2QzEepyMFCmHs=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=hCxqfL42BE1c3AoWOjynsYK7y80zm96rKTQgQnaPa+I9JUHCA93dK49J3iferE46IhbhRXTq1POB4Acn408Hoox+cQEIvvgnDLZPd+oYzyQAQw9QmH1CJl1Jqu24mSsuyCfiMjshX5VmYTpNPmTE+JptbFtwG9KyUfJBcNQkDMc= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=R22BqTqV; arc=none smtp.client-ip=192.198.163.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="R22BqTqV" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1768987418; x=1800523418; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=G1GyKVSX9uKD79xYXrL1AswlRkuNmQ2QzEepyMFCmHs=; b=R22BqTqVFMy195+eHXC5iTdyZVcMhYYWCPtG7LUAzIKKZ+kcyG4w8mje jyqgmFLdWNdD6akaki1+gwqGxx3GsclGg4ayR54d5jeY6IqKEiIvYqqnO tXF7mhVpVzvFP489taHRvRgnHntVsigex/SZdbrwr75I615vy7vsw8QdE 6hGRATbkmNn7o1e/1qvoBXviJPmaRtV3EzieUwVkHP8WE4TGEwgqXh6OZ K+FwZygeJXRfbudmot3nseiuiUl2soIbYra+z9rKSmEkaZKARClUN6mX7 rly14/sbXfS0C88aRJpLdt0NRSECZYCuzgTVZQa061OxdZ0FjuSB+jh+d Q==; X-CSE-ConnectionGUID: UV1IEhP7QSeXcOd18fWRXQ== X-CSE-MsgGUID: eihg6aN5T0eQ34apfD3wug== X-IronPort-AV: E=McAfee;i="6800,10657,11677"; a="57773282" X-IronPort-AV: E=Sophos;i="6.21,242,1763452800"; d="scan'208";a="57773282" Received: from orviesa003.jf.intel.com ([10.64.159.143]) by fmvoesa110.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Jan 2026 01:23:38 -0800 X-CSE-ConnectionGUID: Uoph8pElSlGD9fUCxwwe5A== X-CSE-MsgGUID: 9HzlT/PCQROiXYhEDVPByQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.21,242,1763452800"; d="scan'208";a="210561003" Received: from black.igk.intel.com ([10.91.253.5]) by orviesa003.jf.intel.com with ESMTP; 21 Jan 2026 01:23:37 -0800 From: Heikki Krogerus To: Wolfram Sang Cc: Jeremy Kerr , Matt Johnston , linux-i2c@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 3/4] mctp i2c: Enable SMBus ARP discovery Date: Wed, 21 Jan 2026 10:23:27 +0100 Message-ID: <20260121092328.2308705-4-heikki.krogerus@linux.intel.com> X-Mailer: git-send-email 2.50.1 In-Reply-To: <20260121092328.2308705-1-heikki.krogerus@linux.intel.com> References: <20260121092328.2308705-1-heikki.krogerus@linux.intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Since the SMBus Address Resolution Protocol (ARP) is now supported with all I2C host adapters, every ARP-capable MCTP device will get automatically enumerated. Those devices just need to be bind to this driver. The SMBus ARP-capable MCTP devices are identified by checking the interface (MCTP SMBus/I2C Transport Binding Specification section 6.5). The interface must match the ASF protocol, so all devices that use the ASF protocol as their interface will be probed by this driver. Link: https://www.dmtf.org/sites/default/files/standards/documents/DSP0237_= 1.2.0.pdf Signed-off-by: Heikki Krogerus Acked-by: Jakub Kicinski --- drivers/net/mctp/mctp-i2c.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/drivers/net/mctp/mctp-i2c.c b/drivers/net/mctp/mctp-i2c.c index 8043b57bdf25..47d7f6b5212e 100644 --- a/drivers/net/mctp/mctp-i2c.c +++ b/drivers/net/mctp/mctp-i2c.c @@ -21,6 +21,7 @@ #include #include #include +#include #include #include #include @@ -1105,6 +1106,12 @@ static const struct i2c_device_id mctp_i2c_id[] =3D { }; MODULE_DEVICE_TABLE(i2c, mctp_i2c_id); =20 +static const struct smbus_device_id mctp_smbus_id[] =3D { + { SMBUS_INTERFACE_ASF }, + {} +}; +MODULE_DEVICE_TABLE(smbus, mctp_smbus_id); + static const struct of_device_id mctp_i2c_of_match[] =3D { { .compatible =3D "mctp-i2c-controller" }, {}, @@ -1119,6 +1126,7 @@ static struct i2c_driver mctp_i2c_driver =3D { .probe =3D mctp_i2c_probe, .remove =3D mctp_i2c_remove, .id_table =3D mctp_i2c_id, + .smbus_id_table =3D mctp_smbus_id, }; =20 static __init int mctp_i2c_mod_init(void) --=20 2.50.1