ACPI: docs: enumeration: Correct reference to the I²C device data type
PATCH 1/1 ACPI: docs: enumeration: Correct reference to the I²C device data type
I²C peripheral devices that are connected to the controller are represented in the Linux kernel as objects of the struct i2c_client. Fix this in the documentation.
Signed-off-by Andy Shevchenko <[email protected]>
--- Documentation/firmware-guide/acpi/enumeration.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/firmware-guide/acpi/enumeration.rst +1 -1
@@ -19,7 +19,7 @@ possible we decided to do following: platform devices. - Devices behind real busses where there is a connector resource - are represented as struct spi_device or struct i2c_device. Note + are represented as struct spi_device or struct i2c_client. Note that standard UARTs are not busses so there is no struct uart_device, although some of them may be represented by struct serdev_device.
Signature · 1 line
2.39.1
Quoted 15 lines · Andy Shevchenko
I²C peripheral devices that are connected to the controller are represented in the Linux kernel as objects of the struct
i2c_client. Fix this in the documentation.Signed-off-by Andy Shevchenko <[email protected]>--- Documentation/firmware-guide/acpi/enumeration.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/firmware-guide/acpi/enumeration.rst +0
-0
Documentation/firmware-guide/acpi/enumeration.rst possible we decided to do following:
Quoted 9 lines
Documentation/firmware-guide/acpi/enumeration.rst +1
-2@@ -19,7 +19,7 @@ possible we decided to do following: platform devices. - Devices behind real busses where there is a connector resource - are represented as struct spi_device or struct i2c_device. Note + are represented as struct spi_device or struct i2c_client. Note that standard UARTs are not busses so there is no struct uart_device, although some of them may be represented by struct serdev_device. --
Applied as 6.3-rc material, thanks!