diff options
| author |   Jarkko Nikula <jarkko.nikula@linux.intel.com> | 2015-12-10 13:48:43 +0200 |
|---|---|---|
| committer |   Wolfram Sang <wsa@the-dreams.de> | 2015-12-12 18:04:57 +0100 |
| commit | e79e72c5a242fa21c971cfb40017f1039daf4d77 (patch) | |
| tree | e31e0726b461d4b8a5910b58003289974e3eb32d /arch/arm/boot/dts/armada-38x.dtsi | |
| parent | i2c: designware: fix IO timeout issue for AMD controller (diff) | |
| download | linux-dev-e79e72c5a242fa21c971cfb40017f1039daf4d77.tar.xz linux-dev-e79e72c5a242fa21c971cfb40017f1039daf4d77.zip | |
i2c: designware: Keep pm_runtime_enable/_disable calls in sync
On an hardware shared I2C bus (certain Intel Baytrail SoC platforms) the
runtime PM disable depth keeps increasing over repeated modprobe/rmmod
cycle because pm_runtime_disable() is called without checking should it
be disabled already because of bus sharing.
This hasn't made any other harm than dev->power.disable_depth keeps
increasing but keep it sync by calling pm_runtime_disable() only when
runtime PM is not disabled.
Reported-by: Wolfram Sang <wsa@the-dreams.de>
Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'arch/arm/boot/dts/armada-38x.dtsi')
0 files changed, 0 insertions, 0 deletions