Minki/linux
1
0
Fork 1
mirror of https://github.com/torvalds/linux.git synced 2024-11-26 14:12:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: i2c: use the new API in 'writing-clients'

Browse Source 
i2c_new_device is deprecated, use i2c_new_client_device. Also, align a
paragraph while here.

Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
This commit is contained in:
Wolfram Sang 2020-01-07 18:47:46 +01:00 committed by Wolfram Sang
parent e634a50c9c
commit e8d51e9629
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Documentation/i2c/writing-clients.rst
View File

@ -175,8 +175,8 @@ Device Creation
If you know for a fact that an I2C device is connected to a given I2C bus, If you know for a fact that an I2C device is connected to a given I2C bus,
you can instantiate that device by simply filling an i2c_board_info you can instantiate that device by simply filling an i2c_board_info
structure with the device address and driver name, and calling structure with the device address and driver name, and calling
i2c_new_device(). This will create the device, then the driver core will i2c_new_client_device(). This will create the device, then the driver core
take care of finding the right driver and will call its probe() method. will take care of finding the right driver and will call its probe() method.
If a driver supports different device types, you can specify the type you If a driver supports different device types, you can specify the type you
want using the type field. You can also specify an IRQ and platform data want using the type field. You can also specify an IRQ and platform data
if needed. if needed.
@ -186,14 +186,14 @@ don't know the exact address it uses. This happens on TV adapters for
example, where the same driver supports dozens of slightly different example, where the same driver supports dozens of slightly different
models, and I2C device addresses change from one model to the next. In models, and I2C device addresses change from one model to the next. In
that case, you can use the i2c_new_scanned_device() variant, which is that case, you can use the i2c_new_scanned_device() variant, which is
similar to i2c_new_device(), except that it takes an additional list of similar to i2c_new_client_device(), except that it takes an additional list
possible I2C addresses to probe. A device is created for the first of possible I2C addresses to probe. A device is created for the first
responsive address in the list. If you expect more than one device to be responsive address in the list. If you expect more than one device to be
present in the address range, simply call i2c_new_scanned_device() that present in the address range, simply call i2c_new_scanned_device() that
many times. many times.
The call to i2c_new_device() or i2c_new_scanned_device() typically happens The call to i2c_new_client_device() or i2c_new_scanned_device() typically
in the I2C bus driver. You may want to save the returned i2c_client happens in the I2C bus driver. You may want to save the returned i2c_client
reference for later use. reference for later use.
@ -236,11 +236,11 @@ possible.
Device Deletion Device Deletion
--------------- ---------------
Each I2C device which has been created using i2c_new_device() or Each I2C device which has been created using i2c_new_client_device()
i2c_new_scanned_device() can be unregistered by calling or i2c_new_scanned_device() can be unregistered by calling
i2c_unregister_device(). If you don't call it explicitly, it will be i2c_unregister_device(). If you don't call it explicitly, it will be
called automatically before the underlying I2C bus itself is removed, as a called automatically before the underlying I2C bus itself is removed,
device can't survive its parent in the device driver model. as a device can't survive its parent in the device driver model.
Initializing the driver Initializing the driver