On Tue, 23 Oct 2012 10:54:08 +0100, Mark Brown
wrote:
> Rather than requiring platforms to select the generic clock API to make
> it available make the API available as a user selectable option unless the
> user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
> or selects
On Tue, 23 Oct 2012 10:54:08 +0100, Mark Brown
broo...@opensource.wolfsonmicro.com wrote:
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
or selects COMMON_CLK (if they depend on the generic implementation).
All
On Mon, Oct 22, 2012 at 09:56:54AM -0600, Stephen Warren wrote:
> Since v3.7-rc1, Tegra uses common clock, so I don't think the change
> above is right is it?
No, updated. It really shouldn't take multiple kernel releases to get
something like this done...
signature.asc
Description: Digital
On Tue, Oct 23, 2012 at 10:10:09AM +0800, Kelvin Cheung wrote:
> Hi Mark,
Don't top post!
> But the common clock infrastructure of Loongson1 has been implemented and
> enabled in previous patches.
> http://patchwork.linux-mips.org/patch/4268/
> Please remove this arch from your patch.
Done.
On Tue, Oct 23, 2012 at 10:10:09AM +0800, Kelvin Cheung wrote:
Hi Mark,
Don't top post!
But the common clock infrastructure of Loongson1 has been implemented and
enabled in previous patches.
http://patchwork.linux-mips.org/patch/4268/
Please remove this arch from your patch.
Done.
On Mon, Oct 22, 2012 at 09:56:54AM -0600, Stephen Warren wrote:
Since v3.7-rc1, Tegra uses common clock, so I don't think the change
above is right is it?
No, updated. It really shouldn't take multiple kernel releases to get
something like this done...
signature.asc
Description: Digital
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
or selects COMMON_CLK (if they depend on the generic implementation).
All
On 10/22/2012 07:02 AM, Mark Brown wrote:
> Rather than requiring platforms to select the generic clock API to make
> it available make the API available as a user selectable option unless the
> user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
> or selects COMMON_CLK (if
On Mon, Oct 22, 2012 at 02:50:24PM +0100, Russell King - ARM Linux wrote:
> On Mon, Oct 22, 2012 at 02:27:11PM +0100, Mark Brown wrote:
> > If we're worrying about that there's the larger point that the effect of
> > this patch is to make HAVE_CLK meaningless as there will be no platform
> > for
On Mon, Oct 22, 2012 at 02:27:11PM +0100, Mark Brown wrote:
> On Mon, Oct 22, 2012 at 02:05:57PM +0100, Russell King - ARM Linux wrote:
> > On Mon, Oct 22, 2012 at 02:02:50PM +0100, Mark Brown wrote:
> > > @@ -327,6 +328,7 @@ config ARCH_AT91
> > > select ARCH_REQUIRE_GPIOLIB
> > > select
On Mon, Oct 22, 2012 at 02:05:57PM +0100, Russell King - ARM Linux wrote:
> On Mon, Oct 22, 2012 at 02:02:50PM +0100, Mark Brown wrote:
> > @@ -327,6 +328,7 @@ config ARCH_AT91
> > select ARCH_REQUIRE_GPIOLIB
> > select CLKDEV_LOOKUP
> > select HAVE_CLK
> > + select HAVE_CUSTOM_CLK
On Mon, Oct 22, 2012 at 02:02:50PM +0100, Mark Brown wrote:
> @@ -327,6 +328,7 @@ config ARCH_AT91
> select ARCH_REQUIRE_GPIOLIB
> select CLKDEV_LOOKUP
> select HAVE_CLK
> + select HAVE_CUSTOM_CLK
This is silly. If you select "HAVE_CUSTOM_CLK" then isn't it true that
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
or selects COMMON_CLK (if they depend on the generic implementation).
All
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
or selects COMMON_CLK (if they depend on the generic implementation).
All
On Mon, Oct 22, 2012 at 02:02:50PM +0100, Mark Brown wrote:
@@ -327,6 +328,7 @@ config ARCH_AT91
select ARCH_REQUIRE_GPIOLIB
select CLKDEV_LOOKUP
select HAVE_CLK
+ select HAVE_CUSTOM_CLK
This is silly. If you select HAVE_CUSTOM_CLK then isn't it true that
HAVE_CLK
On Mon, Oct 22, 2012 at 02:05:57PM +0100, Russell King - ARM Linux wrote:
On Mon, Oct 22, 2012 at 02:02:50PM +0100, Mark Brown wrote:
@@ -327,6 +328,7 @@ config ARCH_AT91
select ARCH_REQUIRE_GPIOLIB
select CLKDEV_LOOKUP
select HAVE_CLK
+ select HAVE_CUSTOM_CLK
This is
On Mon, Oct 22, 2012 at 02:27:11PM +0100, Mark Brown wrote:
On Mon, Oct 22, 2012 at 02:05:57PM +0100, Russell King - ARM Linux wrote:
On Mon, Oct 22, 2012 at 02:02:50PM +0100, Mark Brown wrote:
@@ -327,6 +328,7 @@ config ARCH_AT91
select ARCH_REQUIRE_GPIOLIB
select CLKDEV_LOOKUP
On Mon, Oct 22, 2012 at 02:50:24PM +0100, Russell King - ARM Linux wrote:
On Mon, Oct 22, 2012 at 02:27:11PM +0100, Mark Brown wrote:
If we're worrying about that there's the larger point that the effect of
this patch is to make HAVE_CLK meaningless as there will be no platform
for which
On 10/22/2012 07:02 AM, Mark Brown wrote:
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
or selects COMMON_CLK (if
On Tue, 2012-08-28 at 13:35 -0700, Mark Brown wrote:
> Rather than requiring platforms to select the generic clock API to make
> it available make the API available as a user selectable option unless the
> user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
> or selects
On Tue, 2012-08-28 at 13:35 -0700, Mark Brown wrote:
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
or selects
On 08/30/12 10:19, Mark Brown wrote:
On Wed, Aug 29, 2012 at 02:49:34PM -0700, Stephen Warren wrote:
On 08/28/12 13:35, Mark Brown wrote:
@@ -674,6 +676,7 @@ config ARCH_TEGRA
select GENERIC_CLOCKEVENTS
select GENERIC_GPIO
select HAVE_CLK
+ select
On Wed, Aug 29, 2012 at 02:49:34PM -0700, Stephen Warren wrote:
> On 08/28/12 13:35, Mark Brown wrote:
> >@@ -674,6 +676,7 @@ config ARCH_TEGRA
> > select GENERIC_CLOCKEVENTS
> > select GENERIC_GPIO
> > select HAVE_CLK
> >+select HAVE_CUSTOM_CLK
> For 3.7, Tegra will switch to
On Wed, Aug 29, 2012 at 02:49:34PM -0700, Stephen Warren wrote:
On 08/28/12 13:35, Mark Brown wrote:
@@ -674,6 +676,7 @@ config ARCH_TEGRA
select GENERIC_CLOCKEVENTS
select GENERIC_GPIO
select HAVE_CLK
+select HAVE_CUSTOM_CLK
For 3.7, Tegra will switch to the common
On 08/30/12 10:19, Mark Brown wrote:
On Wed, Aug 29, 2012 at 02:49:34PM -0700, Stephen Warren wrote:
On 08/28/12 13:35, Mark Brown wrote:
@@ -674,6 +676,7 @@ config ARCH_TEGRA
select GENERIC_CLOCKEVENTS
select GENERIC_GPIO
select HAVE_CLK
+ select
On 08/28/12 13:35, Mark Brown wrote:
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
or selects COMMON_CLK (if they
On 08/28/12 13:35, Mark Brown wrote:
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
or selects COMMON_CLK (if they
Around Tue 28 Aug 2012 13:35:04 -0700 or thereabout, Mark Brown wrote:
> Rather than requiring platforms to select the generic clock API to make
> it available make the API available as a user selectable option unless the
> user either selects HAVE_CUSTOM_CLK (if they have their own
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
or selects COMMON_CLK (if they depend on the generic implementation).
All
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
or selects COMMON_CLK (if they depend on the generic implementation).
All
Around Tue 28 Aug 2012 13:35:04 -0700 or thereabout, Mark Brown wrote:
Rather than requiring platforms to select the generic clock API to make
it available make the API available as a user selectable option unless the
user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
32 matches
Mail list logo
