Messages in this thread | | | Subject | Re: Why do we need reset_control_get_optional() ? | From | Philipp Zabel <> | Date | Wed, 24 Aug 2016 15:29:42 +0200 |
| |
Am Dienstag, den 16.08.2016, 18:41 +0900 schrieb Masahiro Yamada: > Hi Arnd, > > 2016-08-06 0:35 GMT+09:00 Arnd Bergmann <arnd@arndb.de>: > > > > > config RESET_FOO > > bool "FOO reset controller" if COMPILE_TEST && !ARCH_FOO > > default ARCH_FOO > > > > then I think we get both: you won't be able to turn it off > > but also get the build testing. > > This looks good to me, too. > I do not know if we need "&& !ARCH_FOO", though. > > When we are compile-testing, we do not care if it works on run-time, > so perhaps it makes sense to allow to enable/disable RESET_FOO > regardless ARCH_FOO.
I'll send a few patches to add the Kconfig symbols. Turning around the RESET_CONTROLLER selection can be done in a second step.
regards Philipp
| |