[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1389197175.23721.24.camel@hornet>
Date: Wed, 08 Jan 2014 16:06:15 +0000
From: Pawel Moll <pawel.moll@....com>
To: Mike Turquette <mturquette@...aro.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Samuel Ortiz <sameo@...ux.intel.com>,
Arnd Bergmann <arnd@...db.de>, Jon Medhurst <tixy@...aro.org>,
"arm@...nel.org" <arm@...nel.org>, Olof Johansson <olof@...om.net>
Subject: Re: [RFC 12/18] clk: versatile: Split config options for sp810 and
vexpress_osc
On Mon, 2013-12-23 at 20:05 +0000, Mike Turquette wrote:
> Quoting Pawel Moll (2013-12-23 08:23:44)
> > Move the Kconfig entry for Versatile (& Express) clock drivers
> > into a separate file and add individual options for sp810
> > and vexpress_osc drivers, as they are optional in some
> > configurations and may have separate dependencies.
> >
> > Signed-off-by: Pawel Moll <pawel.moll@....com>
> > Cc: Mike Turquette <mturquette@...aro.org>
>
> Is there a reason to continue to expose these as user-visible config
> options? I guess that with Device Tree we can just include clock nodes
> (or not) for boards that use these clocks (or do not use them).
>
> And it seems for many configurations COMMON_CLK_VERSATILE is always
> selected, so what is the point of the other two sub-options?
It's mostly for arm64, where all the bits and pieces are individually
selected (and SP810 is not present in some vexpress configurations).
Paweł
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists