Commit a8e58f29 authored by Mauro Carvalho Chehab's avatar Mauro Carvalho Chehab

[media] v4l2-subdev.rst: get rid of legacy functions

There are two warnings that are due to functions that has long
gone:

	Documentation/media/kapi/v4l2-subdev.rst:417: WARNING: c:func reference target not found: v4l2_i2c_new_subdev_cfg
	Documentation/media/kapi/v4l2-subdev.rst:436: WARNING: c:func reference target not found: v4l2_i2c_new_probed_subdev

Update the documentation to remove those.
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@s-opensource.com>
parent f06606e5
...@@ -412,19 +412,7 @@ later date. It differs between i2c drivers and as such can be confusing. ...@@ -412,19 +412,7 @@ later date. It differs between i2c drivers and as such can be confusing.
To see which chip variants are supported you can look in the i2c driver code To see which chip variants are supported you can look in the i2c driver code
for the i2c_device_id table. This lists all the possibilities. for the i2c_device_id table. This lists all the possibilities.
There are two more helper functions: There are one more helper function:
:c:func:`v4l2_i2c_new_subdev_cfg`: this function adds new irq and
platform_data arguments and has both 'addr' and 'probed_addrs' arguments:
if addr is not 0 then that will be used (non-probing variant), otherwise the
probed_addrs are probed.
For example: this will probe for address 0x10:
.. code-block:: c
struct v4l2_subdev *sd = v4l2_i2c_new_subdev_cfg(v4l2_dev, adapter,
"module_foo", "chipid", 0, NULL, 0, I2C_ADDRS(0x10));
:c:func:`v4l2_i2c_new_subdev_board` uses an :c:type:`i2c_board_info` struct :c:func:`v4l2_i2c_new_subdev_board` uses an :c:type:`i2c_board_info` struct
which is passed to the i2c driver and replaces the irq, platform_data and addr which is passed to the i2c driver and replaces the irq, platform_data and addr
...@@ -433,9 +421,10 @@ arguments. ...@@ -433,9 +421,10 @@ arguments.
If the subdev supports the s_config core ops, then that op is called with If the subdev supports the s_config core ops, then that op is called with
the irq and platform_data arguments after the subdev was setup. the irq and platform_data arguments after the subdev was setup.
The older :c:func:`v4l2_i2c_new_subdev` and The :c:func:`v4l2_i2c_new_subdev` function will call
:c:func:`v4l2_i2c_new_probed_subdev` functions will call ``s_config`` as :c:func:`v4l2_i2c_new_subdev_board`, internally filling a
well, but with irq set to 0 and platform_data set to ``NULL``. :c:type:`i2c_board_info` structure using the ``client_type`` and the
``addr`` to fill it.
V4L2 sub-device functions and data structures V4L2 sub-device functions and data structures
--------------------------------------------- ---------------------------------------------
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment