From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] clocksource: add an "menu" item to Kconfig
Date: Mon, 12 Aug 2013 14:55:31 +0200 [thread overview]
Message-ID: <5208DB43.6030404@linaro.org> (raw)
In-Reply-To: <52027CCD.3060609@linaro.org>
On 08/07/2013 06:58 PM, John Stultz wrote:
> On 08/07/2013 09:30 AM, Sebastian Andrzej Siewior wrote:
>> 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.
>
> PCI card, eh? (Heh. In writing my previous mail, I think I even wrote
> "These are clocksources soldered to the motherboard, not pci cards!",
> but deleted it as it didn't seem useful. :)
>
> So I think that's actually a first for clocksource drivers.
>
> So, if there are genuinely cross-architecture pluggable clocksources,
> that aren't part of a platform definition, I would be ok with making an
> exception. But I'd want to make sure that we kept a high-bar for adding
> clocksource options, so that folks don't just clutter up the Kconfig menu.
>
> That said, Daniel (now cc'ed - sorry for not cc'ing you earlier!) is now
> in charge of the clocksource directory, so my objections and wishes
> aren't as important as his.
Sebastian,
instead of adding a menu item in the Kconfig, is it possible to have
this Kconfig PCI board support to select the right driver ?
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2013-08-12 12:55 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
2013-08-07 16:58 ` John Stultz
2013-08-12 12:55 ` Daniel Lezcano [this message]
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=5208DB43.6030404@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=bigeasy@linutronix.de \
--cc=john.stultz@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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).