On Tue, Dec 3, 2013 at 12:08 AM, John Stultz wrote:
> On 11/27/2013 09:42 PM, Magnus Damm wrote:
>> Hi John, everyone,
>>
>> Let me get back to you all in a little while together with some code,
>> but before that let me just clarify this:
>>
>> On Wed, Nov 13, 2013 at 5:47 AM, John Stultz
On Tue, Dec 3, 2013 at 12:08 AM, John Stultz john.stu...@linaro.org wrote:
On 11/27/2013 09:42 PM, Magnus Damm wrote:
Hi John, everyone,
Let me get back to you all in a little while together with some code,
but before that let me just clarify this:
On Wed, Nov 13, 2013 at 5:47 AM, John
On 11/27/2013 09:42 PM, Magnus Damm wrote:
> Hi John, everyone,
>
> Let me get back to you all in a little while together with some code,
> but before that let me just clarify this:
>
> On Wed, Nov 13, 2013 at 5:47 AM, John Stultz wrote:
>> On Tue, Nov 12, 2013 at 4:26 AM, Magnus Damm wrote:
>>>
On 11/27/2013 09:42 PM, Magnus Damm wrote:
Hi John, everyone,
Let me get back to you all in a little while together with some code,
but before that let me just clarify this:
On Wed, Nov 13, 2013 at 5:47 AM, John Stultz john.stu...@linaro.org wrote:
On Tue, Nov 12, 2013 at 4:26 AM, Magnus
Hi John, everyone,
Let me get back to you all in a little while together with some code,
but before that let me just clarify this:
On Wed, Nov 13, 2013 at 5:47 AM, John Stultz wrote:
> On Tue, Nov 12, 2013 at 4:26 AM, Magnus Damm wrote:
>> On Sat, Nov 9, 2013 at 3:34 AM, John Stultz wrote:
Hi John, everyone,
Let me get back to you all in a little while together with some code,
but before that let me just clarify this:
On Wed, Nov 13, 2013 at 5:47 AM, John Stultz john.stu...@linaro.org wrote:
On Tue, Nov 12, 2013 at 4:26 AM, Magnus Damm magnus.d...@gmail.com wrote:
On Sat, Nov 9,
On 11/20/2013 11:34 AM, Arnd Bergmann wrote:
> On Wednesday 20 November 2013, John Stultz wrote:
>> On 11/14/2013 04:40 AM, Arnd Bergmann wrote:
>>
>> Sorry, somehow this mail slipped by me.
>>
>> So yea, as I mentioned earlier, the build testing is the one thing I
>> don't have a good argument
On Wednesday 20 November 2013, John Stultz wrote:
> On 11/14/2013 04:40 AM, Arnd Bergmann wrote:
>
> Sorry, somehow this mail slipped by me.
>
> So yea, as I mentioned earlier, the build testing is the one thing I
> don't have a good argument against. But I still would rather not having
> user
On 11/14/2013 04:40 AM, Arnd Bergmann wrote:
> On Wednesday 13 November 2013, John Stultz wrote:
>>> +config EM_TIMER_STI
>>> + bool "STI timer driver"
>>> + default y if ARM
>>> + help
>>> + This enables build of the STI timer driver.
>>
>> So since I do want to avoid
On 11/14/2013 01:40 PM, Arnd Bergmann wrote:
On Wednesday 13 November 2013, John Stultz wrote:
+config EM_TIMER_STI
+ bool "STI timer driver"
+ default y if ARM
+ help
+ This enables build of the STI timer driver.
So since I do want to avoid adding user-selectable
On 11/14/2013 01:40 PM, Arnd Bergmann wrote:
On Wednesday 13 November 2013, John Stultz wrote:
+config EM_TIMER_STI
+ bool STI timer driver
+ default y if ARM
+ help
+ This enables build of the STI timer driver.
So since I do want to avoid adding user-selectable
On 11/14/2013 04:40 AM, Arnd Bergmann wrote:
On Wednesday 13 November 2013, John Stultz wrote:
+config EM_TIMER_STI
+ bool STI timer driver
+ default y if ARM
+ help
+ This enables build of the STI timer driver.
So since I do want to avoid adding user-selectable
On Wednesday 20 November 2013, John Stultz wrote:
On 11/14/2013 04:40 AM, Arnd Bergmann wrote:
Sorry, somehow this mail slipped by me.
So yea, as I mentioned earlier, the build testing is the one thing I
don't have a good argument against. But I still would rather not having
user prompts
On 11/20/2013 11:34 AM, Arnd Bergmann wrote:
On Wednesday 20 November 2013, John Stultz wrote:
On 11/14/2013 04:40 AM, Arnd Bergmann wrote:
Sorry, somehow this mail slipped by me.
So yea, as I mentioned earlier, the build testing is the one thing I
don't have a good argument against. But I
On Wednesday 13 November 2013, John Stultz wrote:
> > +config EM_TIMER_STI
> > + bool "STI timer driver"
> > + default y if ARM
> > + help
> > + This enables build of the STI timer driver.
>
>
> So since I do want to avoid adding user-selectable configs if
> possible,
On Wednesday 13 November 2013, John Stultz wrote:
+config EM_TIMER_STI
+ bool STI timer driver
+ default y if ARM
+ help
+ This enables build of the STI timer driver.
So since I do want to avoid adding user-selectable configs if
possible, here are some
On Wed, Nov 6, 2013 at 3:05 AM, Magnus Damm wrote:
> From: Magnus Damm
>
> Add Kconfig entries for CMT, MTU2, TMU and STI to
> drivers/clocksource/Kconfig. This will allow us to
> get rid of duplicated entires in architecture code
> such as arch/sh and arch/arm/mach-shmobile.
>
> Signed-off-by:
On 11/13/2013 01:14 PM, Daniel Lezcano wrote:
> On 11/12/2013 09:47 PM, John Stultz wrote:
>
> [ ... ]
>
>>> I think all your goals make sense, and I would like to reach the same
>>> place from a usability point of view. I would however like to allow
>>> existing power users to select whatever
On 11/12/2013 09:47 PM, John Stultz wrote:
[ ... ]
I think all your goals make sense, and I would like to reach the same
place from a usability point of view. I would however like to allow
existing power users to select whatever they want enabled on their
platform. Ideally I also would like to
On 11/12/2013 09:47 PM, John Stultz wrote:
[ ... ]
I think all your goals make sense, and I would like to reach the same
place from a usability point of view. I would however like to allow
existing power users to select whatever they want enabled on their
platform. Ideally I also would like to
On 11/13/2013 01:14 PM, Daniel Lezcano wrote:
On 11/12/2013 09:47 PM, John Stultz wrote:
[ ... ]
I think all your goals make sense, and I would like to reach the same
place from a usability point of view. I would however like to allow
existing power users to select whatever they want
On Wed, Nov 6, 2013 at 3:05 AM, Magnus Damm magnus.d...@gmail.com wrote:
From: Magnus Damm d...@opensource.se
Add Kconfig entries for CMT, MTU2, TMU and STI to
drivers/clocksource/Kconfig. This will allow us to
get rid of duplicated entires in architecture code
such as arch/sh and
On Tue, Nov 12, 2013 at 4:26 AM, Magnus Damm wrote:
> On Sat, Nov 9, 2013 at 3:34 AM, John Stultz wrote:
>> I know for some SoC maintainers, there's a desire to have config options
>> be this abstract "buckets of parts", which folks can put together some
>> random configuration and out will pop
On Sat, Nov 9, 2013 at 3:34 AM, John Stultz wrote:
> On 11/08/2013 12:23 AM, Magnus Damm wrote:
>> On Thu, Nov 7, 2013 at 8:27 PM, Daniel Lezcano
>> wrote:
>>> On 11/06/2013 12:05 PM, Magnus Damm wrote:
From: Magnus Damm
Add Kconfig entries for CMT, MTU2, TMU and STI to
On Sat, Nov 9, 2013 at 3:34 AM, John Stultz john.stu...@linaro.org wrote:
On 11/08/2013 12:23 AM, Magnus Damm wrote:
On Thu, Nov 7, 2013 at 8:27 PM, Daniel Lezcano
daniel.lezc...@linaro.org wrote:
On 11/06/2013 12:05 PM, Magnus Damm wrote:
From: Magnus Damm d...@opensource.se
Add Kconfig
On Tue, Nov 12, 2013 at 4:26 AM, Magnus Damm magnus.d...@gmail.com wrote:
On Sat, Nov 9, 2013 at 3:34 AM, John Stultz john.stu...@linaro.org wrote:
I know for some SoC maintainers, there's a desire to have config options
be this abstract buckets of parts, which folks can put together some
On 11/08/2013 12:23 AM, Magnus Damm wrote:
> On Thu, Nov 7, 2013 at 8:27 PM, Daniel Lezcano
> wrote:
>> On 11/06/2013 12:05 PM, Magnus Damm wrote:
>>> From: Magnus Damm
>>>
>>> Add Kconfig entries for CMT, MTU2, TMU and STI to
>>> drivers/clocksource/Kconfig. This will allow us to
>>> get rid of
On Thu, Nov 7, 2013 at 8:27 PM, Daniel Lezcano
wrote:
> On 11/06/2013 12:05 PM, Magnus Damm wrote:
>>
>> From: Magnus Damm
>>
>> Add Kconfig entries for CMT, MTU2, TMU and STI to
>> drivers/clocksource/Kconfig. This will allow us to
>> get rid of duplicated entires in architecture code
>> such
On Thu, Nov 7, 2013 at 8:27 PM, Daniel Lezcano
daniel.lezc...@linaro.org wrote:
On 11/06/2013 12:05 PM, Magnus Damm wrote:
From: Magnus Damm d...@opensource.se
Add Kconfig entries for CMT, MTU2, TMU and STI to
drivers/clocksource/Kconfig. This will allow us to
get rid of duplicated entires
On 11/08/2013 12:23 AM, Magnus Damm wrote:
On Thu, Nov 7, 2013 at 8:27 PM, Daniel Lezcano
daniel.lezc...@linaro.org wrote:
On 11/06/2013 12:05 PM, Magnus Damm wrote:
From: Magnus Damm d...@opensource.se
Add Kconfig entries for CMT, MTU2, TMU and STI to
drivers/clocksource/Kconfig. This will
On 11/06/2013 12:05 PM, Magnus Damm wrote:
From: Magnus Damm
Add Kconfig entries for CMT, MTU2, TMU and STI to
drivers/clocksource/Kconfig. This will allow us to
get rid of duplicated entires in architecture code
such as arch/sh and arch/arm/mach-shmobile.
Signed-off-by: Magnus Damm
Hi
On 11/06/2013 12:05 PM, Magnus Damm wrote:
From: Magnus Damm d...@opensource.se
Add Kconfig entries for CMT, MTU2, TMU and STI to
drivers/clocksource/Kconfig. This will allow us to
get rid of duplicated entires in architecture code
such as arch/sh and arch/arm/mach-shmobile.
Signed-off-by:
From: Magnus Damm
Add Kconfig entries for CMT, MTU2, TMU and STI to
drivers/clocksource/Kconfig. This will allow us to
get rid of duplicated entires in architecture code
such as arch/sh and arch/arm/mach-shmobile.
Signed-off-by: Magnus Damm
---
drivers/clocksource/Kconfig | 30
From: Magnus Damm d...@opensource.se
Add Kconfig entries for CMT, MTU2, TMU and STI to
drivers/clocksource/Kconfig. This will allow us to
get rid of duplicated entires in architecture code
such as arch/sh and arch/arm/mach-shmobile.
Signed-off-by: Magnus Damm d...@opensource.se
---
34 matches
Mail list logo
