From: Andy Shevchenko Date: Thu, 2 Mar 2023 16:12:12 +0000 (+0200) Subject: ACPI: docs: enumeration: Correct reference to the I²C device data type X-Git-Tag: microblaze-v6.6~904^2^5 X-Git-Url: http://git.monstr.eu/?a=commitdiff_plain;h=c29b97725c91add5021a3257c14ad1ed32eedf76;p=linux-2.6-microblaze.git 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 Signed-off-by: Rafael J. Wysocki --- diff --git a/Documentation/firmware-guide/acpi/enumeration.rst b/Documentation/firmware-guide/acpi/enumeration.rst index b9dc0c603f36..56d9913a3370 100644 --- a/Documentation/firmware-guide/acpi/enumeration.rst +++ b/Documentation/firmware-guide/acpi/enumeration.rst @@ -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.