From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Why do we need reset_control_get_optional() ?
Date: Sat, 30 Jul 2016 22:13:54 +0200 [thread overview]
Message-ID: <3400649.NoVKUzu81R@wuerfel> (raw)
In-Reply-To: <1469797695.3012.48.camel@pengutronix.de>
On Friday, July 29, 2016 3:08:15 PM CEST Philipp Zabel wrote:
> 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.
This still doesn't let a platform 'select RESET_FOO', unless they
also select RESET_CONTROLLER and ARCH_HAS_RESET_CONTROLLER.
Why do we need to guard all drivers inside of two symbols?
Arnd
next prev parent reply other threads:[~2016-07-30 20:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 11:22 Why do we need reset_control_get_optional() ? Masahiro Yamada
2016-07-28 9:43 ` Philipp Zabel
2016-07-28 10:09 ` Arnd Bergmann
2016-07-28 10:52 ` Masahiro Yamada
2016-07-28 11:00 ` Philipp Zabel
2016-08-05 15:50 ` Arnd Bergmann
2016-08-08 16:39 ` Philipp Zabel
2016-08-08 21:39 ` Arnd Bergmann
2016-08-16 14:36 ` Masahiro Yamada
2016-08-24 6:58 ` Masahiro Yamada
2016-08-24 12:30 ` Philipp Zabel
2016-07-28 10:56 ` Philipp Zabel
2016-07-28 10:29 ` Masahiro Yamada
2016-07-29 13:08 ` Philipp Zabel
2016-07-30 20:13 ` Arnd Bergmann [this message]
2016-08-05 8:55 ` Philipp Zabel
2016-08-05 15:35 ` Arnd Bergmann
2016-08-08 17:29 ` Philipp Zabel
2016-08-16 9:41 ` Masahiro Yamada
2016-08-24 13:29 ` Philipp Zabel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3400649.NoVKUzu81R@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox