From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: John Stultz <john.stultz@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Mattias Wallin <mattias.wallin@stericsson.com>,
Fabio Baltieri <fabio.baltieri@linaro.org>
Subject: Re: [PATCH] clocksource: add an "menu" item to Kconfig
Date: Wed, 07 Aug 2013 18:30:27 +0200 [thread overview]
Message-ID: <52027623.20807@linutronix.de> (raw)
In-Reply-To: <520273FB.3030103@linaro.org>
On 08/07/2013 06:21 PM, John Stultz wrote:
> On 08/07/2013 03:56 AM, Sebastian Andrzej Siewior wrote:
>> This patch adds a menu item to clocksource' Kconfig file. Without it the
>> changeable items look somehow lost in the main drivers' menu
>
> So I'd like to push back on this a bit and ask why we need user-visible
> clocksource config options?
There was one visible Option if I remember correctly. I added two and
was wondering once I found them. I do have a PCI card which provides a
clock source and clock events device. So I assumed select <m|y> would
be doable.
> I'm much prefer the platform options select the needed clocksources, and
> not leave it up to the user (who really doesn't want to go digging
> around to find the clocksource sub-menu under drivers, and scan a list
> of 100 options that aren't possible on their hardware).
>
> For an example of what I consider bad behavior here, see the RTC driver
> directory - at a certain point they just become hashes: "Oh no.. you
> selected rtc-387aae6fd, on your hardware, you need rtc-adfb8e5".
>
> It really just seems like it forces more unnecessary options on the user
> and more ways to build a kernel that won't boot.
>
> I do get you're trying to fix up the bad situation, caused by
> user-prompts slipping into the Kconfig.
Yes, that is fine. That PCI device is divided into multiple devices so
once it is enabled I could use "select" for required clock source.
> But I might prefer a patch closer to whats below.
Okay.
>
> thanks
> -john
Sebastian
next prev parent reply other threads:[~2013-08-07 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 10:56 [PATCH] clocksource: add an "menu" item to Kconfig Sebastian Andrzej Siewior
2013-08-07 16:21 ` John Stultz
2013-08-07 16:30 ` Sebastian Andrzej Siewior [this message]
2013-08-07 16:58 ` John Stultz
2013-08-12 12:55 ` Daniel Lezcano
2013-08-12 13:04 ` Sebastian Andrzej Siewior
2013-08-12 13:06 ` Daniel Lezcano
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=52027623.20807@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=fabio.baltieri@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattias.wallin@stericsson.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).