diff options
author | Zhuo-hao Lee <zhuo-hao.lee@intel.com> | 2016-08-27 09:39:30 +0200 |
---|---|---|
committer | Wolfram Sang <wsa@the-dreams.de> | 2016-09-08 22:14:36 +0200 |
commit | 664d58bf4d3406dc4404e29bcb8c89fd22589d57 (patch) | |
tree | 8096bcb43ea1dbc7d623313bc14413591168d6da /drivers/i2c/busses/i2c-cadence.c | |
parent | Documentation: i2c: slave-interface: add note for driver development (diff) | |
download | linux-664d58bf4d3406dc4404e29bcb8c89fd22589d57.tar.xz linux-664d58bf4d3406dc4404e29bcb8c89fd22589d57.zip |
i2c: designware: save the preset value of DW_IC_SDA_HOLD
There are several ways to set the SDA hold time for i2c controller,
including: Device Tree, built-in device properties and ACPI. However,
if the SDA hold time is not specified by above method, we should
read the value, where it is preset by firmware, and save it to
sda_hold_time. This is needed because when i2c controller enters
runtime suspend, the DW_IC_SDA_HOLD value will be reset to chipset
default value. And during runtime resume, i2c_dw_init will be called
to reconfigure i2c controller. If sda_hold_time is zero, the chipset
default hold time will be used, that will be too short for some
platforms. Therefore, to have a better tolerance, the DW_IC_SDA_HOLD
value should be kept by sda_hold_time.
Signed-off-by: Zhuo-hao Lee <zhuo-hao.lee@intel.com>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'drivers/i2c/busses/i2c-cadence.c')
0 files changed, 0 insertions, 0 deletions