<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/drivers/misc/amd-sbi, branch v7.1-rc5</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=v7.1-rc5</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=v7.1-rc5'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2026-04-02T14:17:29+00:00</updated>
<entry>
<title>misc: amd-sbi: Add device tree mapping for AMD SBRMI devices</title>
<updated>2026-04-02T14:17:29+00:00</updated>
<author>
<name>Akshay Gupta</name>
<email>Akshay.Gupta@amd.com</email>
</author>
<published>2026-03-18T11:27:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=eef2a8ddfaf80ecca82800f40bce8647ac1bdf57'/>
<id>urn:sha1:eef2a8ddfaf80ecca82800f40bce8647ac1bdf57</id>
<content type='text'>
Add device tree mapping to enable SBRMI device support across
different models and steppings on the AMD Venice platform.

Reviewed-by: Naveen Krishna Chatradhi &lt;naveenkrishna.chatradhi@amd.com&gt;
Signed-off-by: Akshay Gupta &lt;Akshay.Gupta@amd.com&gt;
Link: https://patch.msgid.link/20260318112711.2757467-3-Akshay.Gupta@amd.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>misc: amd-sbi: Add check to probe only SBRMI devices</title>
<updated>2026-04-02T14:17:29+00:00</updated>
<author>
<name>Akshay Gupta</name>
<email>Akshay.Gupta@amd.com</email>
</author>
<published>2026-03-18T11:27:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=82e1288701c0b746397f2a133b1f93d3d48eee23'/>
<id>urn:sha1:82e1288701c0b746397f2a133b1f93d3d48eee23</id>
<content type='text'>
AMD OOB devices are differentiated by their Instance ID, with SBRMI
assigned Instance ID 1. Since the device ID match does not consider
the Instance ID, add an explicit check to restrict probing to only
the SBRMI device and exclude other OOB devices.

Reviewed-by: Naveen Krishna Chatradhi &lt;naveenkrishna.chatradhi@amd.com&gt;
Signed-off-by: Akshay Gupta &lt;Akshay.Gupta@amd.com&gt;
Link: https://patch.msgid.link/20260318112711.2757467-2-Akshay.Gupta@amd.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>misc: amd-sbi: Add revision support for AMD Venice platform</title>
<updated>2026-04-02T14:17:29+00:00</updated>
<author>
<name>Akshay Gupta</name>
<email>Akshay.Gupta@amd.com</email>
</author>
<published>2026-03-18T11:27:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=b5e7fb39819aec09a27c89f203774ffc6b13a78d'/>
<id>urn:sha1:b5e7fb39819aec09a27c89f203774ffc6b13a78d</id>
<content type='text'>
The AMD Venice platform uses revision 0x31 and a two-byte register
address size. Add the revision to the CPUID and MCAMSR protocol
functions to ensure correct protocol identification.

Reviewed-by: Naveen Krishna Chatradhi &lt;naveenkrishna.chatradhi@amd.com&gt;
Signed-off-by: Akshay Gupta &lt;Akshay.Gupta@amd.com&gt;
Link: https://patch.msgid.link/20260318112711.2757467-1-Akshay.Gupta@amd.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>misc: amd-sbi: Address CPUID extended function bits</title>
<updated>2026-04-02T14:17:25+00:00</updated>
<author>
<name>Akshay Gupta</name>
<email>Akshay.Gupta@amd.com</email>
</author>
<published>2026-03-18T09:47:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=ac7460c6037e45c72703cbe9a96ee6668601c80f'/>
<id>urn:sha1:ac7460c6037e45c72703cbe9a96ee6668601c80f</id>
<content type='text'>
According to the UAPI header (amd-apml.h), the CPUID extended function
capability is indicated by bits [55:48], but the driver currently
checks bits [63:56]. Adjust the driver to use bits [55:48] so that
extended function capability is detected correctly.

Fixes: bb13a84ed6b7 ("misc: amd-sbi: Add support for CPUID protocol")
Tested-by: Prathima L K &lt;Prathima.Lk@amd.com&gt;
Reviewed-by: Naveen Krishna Chatradhi &lt;naveenkrishna.chatradhi@amd.com&gt;
Signed-off-by: Akshay Gupta &lt;Akshay.Gupta@amd.com&gt;
Link: https://patch.msgid.link/20260318094706.2623258-1-Akshay.Gupta@amd.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>i3c: simplify combined i3c/i2c dependencies</title>
<updated>2026-02-27T15:33:07+00:00</updated>
<author>
<name>Arnd Bergmann</name>
<email>arnd@arndb.de</email>
</author>
<published>2026-02-04T16:41:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=663eb8763c251dbcd0536b14ec134e63e4173348'/>
<id>urn:sha1:663eb8763c251dbcd0536b14ec134e63e4173348</id>
<content type='text'>
All combined i2c/i3c drivers appear to suffer from the same link
time problem when CONFIG_I3C is set to 'm':

arm-linux-gnueabi-ld: drivers/iio/magnetometer/mmc5633.o: in function `mmc5633_i3c_driver_init':
mmc5633.c:(.init.text+0x30): undefined reference to `i3c_driver_register_with_owner'

This was previously fixed every time by marking individual
drivers as 'depends on I2C; depends on I3C || !I3C', but this gets
tedious and is somewhat confusing.

Add a Kconfig symbol 'I3C_OR_I2C' to help replace those dependencies,
and use this in all the existing drivers that had already fixed it
as well as the new mmc5633 driver.

Reviewed-by: Jonathan Cameron &lt;jonathan.cameron@huawei.com&gt;
Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Acked-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Acked-by: Jonathan Cameron &lt;jonathan.cameron@huawei.com&gt;
Link: https://patch.msgid.link/20260204164216.544409-1-arnd@kernel.org
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
</content>
</entry>
<entry>
<title>Merge 6.18-rc3 into char-misc-next</title>
<updated>2025-10-27T06:48:19+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2025-10-27T06:48:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=c428900703aaa528bf141358551287f87e5b2b93'/>
<id>urn:sha1:c428900703aaa528bf141358551287f87e5b2b93</id>
<content type='text'>
We need the fixes in here, and it resolves a merge conflict in:
	drivers/misc/amd-sbi/Kconfig

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>misc: amd-sbi: Clarify that this is a BMC driver</title>
<updated>2025-10-22T06:02:57+00:00</updated>
<author>
<name>Jean Delvare</name>
<email>jdelvare@suse.de</email>
</author>
<published>2025-10-16T13:50:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=70ad06df73a9796026b197d84ead751e096618c7'/>
<id>urn:sha1:70ad06df73a9796026b197d84ead751e096618c7</id>
<content type='text'>
Add a sentence to the driver description to clarify that the sbrmi-i2c
driver is intended to run on the BMC and not on the managed node. Add
platform dependencies accordingly.

Signed-off-by: Jean Delvare &lt;jdelvare@suse.de&gt;
Link: https://lore.kernel.org/r/5c9f7100-0e59-4237-a252-43c3ee4802a2@amd.com
Link: https://patch.msgid.link/20251016155040.0e86c102@endymion
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>misc: amd-sbi: Extend support for MCAMSR protocol for rev 0x21</title>
<updated>2025-10-22T05:59:57+00:00</updated>
<author>
<name>Akshay Gupta</name>
<email>akshay.gupta@amd.com</email>
</author>
<published>2025-09-15T10:36:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=18e4a02963b7582207b8a7b25d053f40ac206e4d'/>
<id>urn:sha1:18e4a02963b7582207b8a7b25d053f40ac206e4d</id>
<content type='text'>
- MCAMSR protocol for revision 0x21 is updated to include the
  extended thread supported by the platform.
- This modifies the existing protocol to include additional byte
  to provide high thread number.
- New input structure is defined to address this, as the hardware
  protocol is tightly coupled with the input structure length

Reviewed-by: Naveen Krishna Chatradhi &lt;naveenkrishna.chatradhi@amd.com&gt;
Signed-off-by: Akshay Gupta &lt;akshay.gupta@amd.com&gt;
Link: https://patch.msgid.link/20250915103649.1705078-6-akshay.gupta@amd.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>misc: amd-sbi: Extend support for CPUID protocol for rev 0x21</title>
<updated>2025-10-22T05:59:57+00:00</updated>
<author>
<name>Akshay Gupta</name>
<email>akshay.gupta@amd.com</email>
</author>
<published>2025-09-15T10:36:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=87816eb4701f9f1aa2866e0585b270a716769e6e'/>
<id>urn:sha1:87816eb4701f9f1aa2866e0585b270a716769e6e</id>
<content type='text'>
- CPUID protocol for revision 0x21 is updated to include the
  extended thread supported by the platform.
- This modifies the existing protocol to include additional byte
  to provide high thread number.
- New input structure is defined to address this, as the hardware
  protocol is tightly coupled with the input structure length

Reviewed-by: Naveen Krishna Chatradhi &lt;naveenkrishna.chatradhi@amd.com&gt;
Signed-off-by: Akshay Gupta &lt;akshay.gupta@amd.com&gt;
Link: https://patch.msgid.link/20250915103649.1705078-5-akshay.gupta@amd.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>misc: amd-sbi: CPUID/MCAMSR protocol for Revision 0x21</title>
<updated>2025-10-22T05:59:57+00:00</updated>
<author>
<name>Akshay Gupta</name>
<email>akshay.gupta@amd.com</email>
</author>
<published>2025-09-15T10:36:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=dd68c06380f67beda28b0cb7d77a75b91a6174e4'/>
<id>urn:sha1:dd68c06380f67beda28b0cb7d77a75b91a6174e4</id>
<content type='text'>
- CPUID and MCAMSR protocol for newer platform with revision
  0x21 and later is modified as per two byte register address size.
- Modify the CPUID and MCAMSR protocol to return error, "-EOPNOTSUPP",
  for revision 0x21.
- Next set of patches will add support for CPUID and MCAMSR for Turin and
  later platforms.

Reviewed-by: Naveen Krishna Chatradhi &lt;naveenkrishna.chatradhi@amd.com&gt;
Signed-off-by: Akshay Gupta &lt;akshay.gupta@amd.com&gt;
Link: https://patch.msgid.link/20250915103649.1705078-4-akshay.gupta@amd.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
