diff mbox series

[v1,1/1] ACPI: docs: enumeration: Correct reference to the I²C device data type

Message ID 20230302161212.38142-1-andriy.shevchenko@linux.intel.com
State Accepted
Commit c29b97725c91add5021a3257c14ad1ed32eedf76
Headers show
Series [v1,1/1] ACPI: docs: enumeration: Correct reference to the I²C device data type | expand

Commit Message

Andy Shevchenko March 2, 2023, 4:12 p.m. UTC
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 <andriy.shevchenko@linux.intel.com>
---
 Documentation/firmware-guide/acpi/enumeration.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff mbox series

Patch

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.