diff options
| author | Maxime Ripard <maxime.ripard@free-electrons.com> | 2014-03-10 12:12:10 +0100 |
|---|---|---|
| committer | Wolfram Sang <wsa@the-dreams.de> | 2014-03-28 08:47:32 +0100 |
| commit | f2a67d0c27c5c018ed592116f1e1577aa041d73d (patch) | |
| tree | 592f4efa91414350bba2f2452a46836e48872ed9 /drivers/parport/parport_mfc3.c | |
| parent | ff370257ed0bba6e98a9538fefa402a4696f9857 (diff) | |
| download | lwn-f2a67d0c27c5c018ed592116f1e1577aa041d73d.tar.gz lwn-f2a67d0c27c5c018ed592116f1e1577aa041d73d.zip | |
i2c: mv64xxx: Fix reset controller handling
The reset framework recently gained optional stubs when CONFIG_RESET_CONTROLLER
is not selected. It also introduced a function reset_get_optional, that is also
dummy-defined whenever the framework isn't enabled, for drivers that needs an
optional reset controller.
Switch to this function, since the mv64xxx driver is in this case. This also
fixes a compilation breakage whenever the reset framework wasn't selected:
drivers/i2c/busses/i2c-mv64xxx.c:771:2: error: implicit declaration of function 'devm_reset_control_get'
While we're at it, remove the redundant test on dev.of_node surrounding the
calls to reset framework functions, since it will either be a valid pointer, an
error pointer in the case where we called reset_get_optional without an of_node
pointer or if it failed, or NULL if we're not loaded through DT.
Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'drivers/parport/parport_mfc3.c')
0 files changed, 0 insertions, 0 deletions