[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1469797695.3012.48.camel@pengutronix.de>
Date: Fri, 29 Jul 2016 15:08:15 +0200
From: Philipp Zabel <p.zabel@...gutronix.de>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Arnd Bergmann <arnd@...db.de>, Axel Lin <axel.lin@...ics.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Hans de Goede <hdegoede@...hat.com>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Lee Jones <lee.jones@...aro.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: Why do we need reset_control_get_optional() ?
Hi Masahiro,
Am Donnerstag, den 28.07.2016, 19:29 +0900 schrieb Masahiro Yamada:
[...]
> However, I think the following makes more sense:
>
>
> menuconfig RESET_CONTROLLER
> bool "Reset Controller Support"
> depends on (ARCH_HAS_RESET_CONTROLLER || COMPILE_TEST)
> default y
> help
> Generic Reset Controller support.
That looks sensible to me. You'll only have to enable the reset
controller framework if either some enabled architecture has a reset
controller (in which case you want the driver for it to be activated by
default), or if you want to compile test some of the reset drivers.
regards
Philipp
Powered by blists - more mailing lists