litmus-rt.git/Documentation/i2c/writing-clients, branch master The LITMUS^RT kernel. Documentation: i2c: Use PM ops instead of legacy suspend/resume 2014-12-04T18:09:03+00:00 Lars-Peter Clausen lars@metafoo.de 2014-11-30T16:52:31+00:00 5f835cef770fc71263ace29198a9e6743033a705 New drivers should use PM ops instead of the legacy suspend/resume callbacks. Update the I2C device driver guides to reflect this. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Wolfram Sang <wsa@the-dreams.de> 
New drivers should use PM ops instead of the legacy suspend/resume
callbacks. Update the I2C device driver guides to reflect this.

Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
i2c: core: Remove definition of i2c_smbus_process_call 2013-01-28T04:26:41+00:00 Tushar Behera tushar.behera@linaro.org 2012-11-19T11:01:42+00:00 c81109332068b44db4fd7b650c0e6bc0fc1411f1 i2c_smbus_process_call has no users in the kernel, so this can be removed. Documentation for the same has been updated accordingly. Fixes following sparse warning. drivers/i2c/i2c-core.c:1871:5: warning: symbol 'i2c_smbus_process_call' was not declared. Should it be static? [wsa: updated the documentation] Signed-off-by: Tushar Behera <tushar.behera@linaro.org> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de> 
i2c_smbus_process_call has no users in the kernel, so this can be
removed. Documentation for the same has been updated accordingly.

Fixes following sparse warning.
drivers/i2c/i2c-core.c:1871:5: warning: symbol 'i2c_smbus_process_call'
was not declared. Should it be static?

[wsa: updated the documentation]

Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
i2c/writing-clients: Mention module_i2c_driver() 2012-07-24T12:13:57+00:00 Jean Delvare khali@linux-fr.org 2012-07-24T12:13:57+00:00 9cd3f2e8496ce97a9218d8b0ace06c4d8f0c6bf5 Based on a previous patch from Peter Meerwald. Signed-off-by: Jean Delvare <khali@linux-fr.org> Acked-by: Peter Meerwald <p.meerwald@bct-electronic.com> 
Based on a previous patch from Peter Meerwald.

Signed-off-by: Jean Delvare <khali@linux-fr.org>
Acked-by: Peter Meerwald <p.meerwald@bct-electronic.com>
i2c/writing-clients: Fix foo_driver.id_table 2011-05-24T18:58:48+00:00 Vikram Narayanan vikram186@gmail.com 2011-05-24T18:58:48+00:00 3116c86033079a1d4d4e84c40028f96b614843b8 The i2c_device_id structure variable's name is not used in the i2c_driver structure. Signed-off-by: Vikram Narayanan <vikram186@gmail.com> Cc: stable@kernel.org Signed-off-by: Jean Delvare <khali@linux-fr.org> 
The i2c_device_id structure variable's name is not used in the
i2c_driver structure.

Signed-off-by: Vikram Narayanan <vikram186@gmail.com>
Cc: stable@kernel.org
Signed-off-by: Jean Delvare <khali@linux-fr.org>
i2c-core: Erase pointer to clientdata on removal 2010-05-04T09:09:27+00:00 Wolfram Sang w.sang@pengutronix.de 2010-05-04T09:09:27+00:00 e4a7b9b04de15f6b63da5ccdd373ffa3057a3681 After discovering that a lot of i2c-drivers leave the pointer to their clientdata dangling, it was decided to let the core handle this issue. It is assumed that the core may access the private data after remove() as there are no guarantees for the lifetime of such pointers anyhow (see thread starting at http://lkml.org/lkml/2010/3/21/68) Signed-off-by: Wolfram Sang <w.sang@pengutronix.de> Signed-off-by: Jean Delvare <khali@linux-fr.org> 
After discovering that a lot of i2c-drivers leave the pointer to their
clientdata dangling, it was decided to let the core handle this issue.
It is assumed that the core may access the private data after remove()
as there are no guarantees for the lifetime of such pointers anyhow (see
thread starting at http://lkml.org/lkml/2010/3/21/68)

Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
i2c: Document the message size limit 2010-03-02T11:23:49+00:00 Zhangfei Gao zgao6@marvell.com 2010-03-02T11:23:49+00:00 0c43ea544c1086fbbed5a6c99ea58eb64674ea8f i2c_master_send & i2c_master_recv do not support more than 64 kb transfer, since msg.len is u16. Signed-off-by: Zhangfei Gao <zgao6@marvell.com> Signed-off-by: Jean Delvare <khali@linux-fr.org> 
i2c_master_send & i2c_master_recv do not support more than 64 kb
transfer, since msg.len is u16.

Signed-off-by: Zhangfei Gao <zgao6@marvell.com>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
i2c: Get rid of struct i2c_client_address_data 2009-12-14T20:17:25+00:00 Jean Delvare khali@linux-fr.org 2009-12-14T20:17:25+00:00 c3813d6af177fab19e322f3114b1f64fbcf08d71 Struct i2c_client_address_data only contains one field at this point, which makes its usefulness questionable. Get rid of it and pass simple address lists around instead. Signed-off-by: Jean Delvare <khali@linux-fr.org> Tested-by: Wolfram Sang <w.sang@pengutronix.de> 
Struct i2c_client_address_data only contains one field at this point,
which makes its usefulness questionable. Get rid of it and pass simple
address lists around instead.

Signed-off-by: Jean Delvare <khali@linux-fr.org>
Tested-by: Wolfram Sang <w.sang@pengutronix.de>
i2c: Get rid of the legacy binding model 2009-06-19T14:58:18+00:00 Jean Delvare khali@linux-fr.org 2009-06-19T14:58:18+00:00 729d6dd571464954f625e6b80950d9e4e3bd94f7 We converted all the legacy i2c drivers so we can finally get rid of the legacy binding model. Hooray! Signed-off-by: Jean Delvare <khali@linux-fr.org> Cc: David Brownell <dbrownell@users.sourceforge.net> 
We converted all the legacy i2c drivers so we can finally get rid of
the legacy binding model. Hooray!

Signed-off-by: Jean Delvare <khali@linux-fr.org>
Cc: David Brownell <dbrownell@users.sourceforge.net>
i2c: Document the different ways to instantiate i2c devices 2009-03-28T20:34:40+00:00 Jean Delvare khali@linux-fr.org 2009-03-28T20:34:40+00:00 764c16918fb2347b3cbc8f6030b2b6561911bc32 On popular demand, here comes some documentation about how to instantiate i2c devices in the new (standard) i2c device driver binding model. I have also clarified how the class bitfield lets driver authors control which buses are probed in the auto-detect case, and warned more loudly against the abuse of this method. Signed-off-by: Jean Delvare <khali@linux-fr.org> Acked-by: Michael Lawnick <nospam_lawnick@gmx.de> Acked-by: Hans Verkuil <hverkuil@xs4all.nl> 
On popular demand, here comes some documentation about how to
instantiate i2c devices in the new (standard) i2c device driver
binding model.

I have also clarified how the class bitfield lets driver authors
control which buses are probed in the auto-detect case, and warned
more loudly against the abuse of this method.

Signed-off-by: Jean Delvare <khali@linux-fr.org>
Acked-by: Michael Lawnick <nospam_lawnick@gmx.de>
Acked-by: Hans Verkuil <hverkuil@xs4all.nl>
i2c: Update and clean up writing-clients document 2008-10-22T18:21:32+00:00 Jean Delvare khali@linux-fr.org 2008-10-22T18:21:32+00:00 0e47858da4b6825e1f1aede74742c7dd6d4ee476 * Strip trailing white space. * Remove out-of-date or irrelevant parts. * Insist on the fact that command is deprecated. * Fix spelling mistakes and typos. * Reformat code examples and function prototypes to comply with the kernel coding style. Signed-off-by: Jean Delvare <khali@linux-fr.org> 
* Strip trailing white space.
* Remove out-of-date or irrelevant parts.
* Insist on the fact that command is deprecated.
* Fix spelling mistakes and typos.
* Reformat code examples and function prototypes to comply with the
  kernel coding style.

Signed-off-by: Jean Delvare <khali@linux-fr.org>