From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>, rjw@sisk.pl
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
linaro-kernel@lists.linaro.org, kernel@pengutronix.de,
linux-pm@vger.kernel.org, nsekhar@ti.com, magnus.damm@gmail.com,
rob.herring@calxeda.com, kevin.hilman@linaro.org,
horms@verge.net.au, ben-linux@fluff.org, kgene.kim@samsung.com,
lenb@kernel.org, plagnioj@jcrosoft.com, linux@maxim.org.za,
linux-arm-kernel@lists.infradead.org, jason@lakedaemon.net
Subject: Re: [RFC patch 02/11] cpuidle / arm : a single cpuidle driver
Date: Tue, 26 Mar 2013 12:44:34 +0100 [thread overview]
Message-ID: <51518A22.2040801@linaro.org> (raw)
In-Reply-To: <20130326111729.GQ5627@lunn.ch>
On 03/26/2013 12:17 PM, Andrew Lunn wrote:
>>> All above code is completly generic and I would rather create
>>> some thing like "drivers/cpuidle/generic-idle.c" where it can
>>> handle all the registration stuff for all arch's rather than
>>> just ARM. There is nothing ARM specific in above code IMHO.
>> Yes, it seems generic but it won't be.
> It very much sounds like you are going in the wrong direction. You
> should be moving towards generic code, not away from generic code.
Well, I am going to the right direction but with an intermediate step :)
But indeed, I will introduce this init function in the generic code
directly and rebase the patchset.
Rafael, is possible to apply the patches 1 - 5 ? Or shall I resend the
subset ?
> Yes, you at some point will need ARM specific code, but that should be
> a minor part and can be placed somewhere else, and called by a
> function pointer, or the generic code can be in a library and called
> from the ARM specific code, etc.
>
> Andrew
>
>
>
> _______________________________________________
> linaro-kernel mailing list
> linaro-kernel@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-kernel
>
WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC patch 02/11] cpuidle / arm : a single cpuidle driver
Date: Tue, 26 Mar 2013 12:44:34 +0100 [thread overview]
Message-ID: <51518A22.2040801@linaro.org> (raw)
In-Reply-To: <20130326111729.GQ5627@lunn.ch>
On 03/26/2013 12:17 PM, Andrew Lunn wrote:
>>> All above code is completly generic and I would rather create
>>> some thing like "drivers/cpuidle/generic-idle.c" where it can
>>> handle all the registration stuff for all arch's rather than
>>> just ARM. There is nothing ARM specific in above code IMHO.
>> Yes, it seems generic but it won't be.
> It very much sounds like you are going in the wrong direction. You
> should be moving towards generic code, not away from generic code.
Well, I am going to the right direction but with an intermediate step :)
But indeed, I will introduce this init function in the generic code
directly and rebase the patchset.
Rafael, is possible to apply the patches 1 - 5 ? Or shall I resend the
subset ?
> Yes, you at some point will need ARM specific code, but that should be
> a minor part and can be placed somewhere else, and called by a
> function pointer, or the generic code can be in a library and called
> from the ARM specific code, etc.
>
> Andrew
>
>
>
> _______________________________________________
> linaro-kernel mailing list
> linaro-kernel at lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-kernel
>
next prev parent reply other threads:[~2013-03-26 11:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 14:26 [RFC patch 00/11] cpuidle : ARM driver to rule them all Daniel Lezcano
2013-03-15 14:26 ` Daniel Lezcano
2013-03-15 14:27 ` [RFC patch 01/11] cpuidle : handle clockevent notify from the cpuidle framework Daniel Lezcano
2013-03-15 14:27 ` Daniel Lezcano
2013-03-15 14:27 ` [RFC patch 02/11] cpuidle / arm : a single cpuidle driver Daniel Lezcano
2013-03-15 14:27 ` Daniel Lezcano
2013-03-15 14:47 ` Arnd Bergmann
2013-03-15 14:47 ` Arnd Bergmann
2013-03-15 15:07 ` Daniel Lezcano
2013-03-15 15:07 ` Daniel Lezcano
2013-03-25 18:27 ` Catalin Marinas
2013-03-25 18:27 ` Catalin Marinas
2013-03-25 18:35 ` Daniel Lezcano
2013-03-25 18:35 ` Daniel Lezcano
2013-03-26 4:31 ` Santosh Shilimkar
2013-03-26 4:31 ` Santosh Shilimkar
2013-03-26 10:58 ` Daniel Lezcano
2013-03-26 10:58 ` Daniel Lezcano
2013-03-26 11:17 ` Andrew Lunn
2013-03-26 11:17 ` Andrew Lunn
2013-03-26 11:44 ` Daniel Lezcano [this message]
2013-03-26 11:44 ` Daniel Lezcano
2013-03-26 23:27 ` Rafael J. Wysocki
2013-03-26 23:27 ` Rafael J. Wysocki
2013-03-15 14:27 ` [RFC patch 03/11] cpuidle / ux500 : use common ARM " Daniel Lezcano
2013-03-15 14:27 ` Daniel Lezcano
2013-03-15 14:27 ` [RFC patch 04/11] cpuidle / omap3 " Daniel Lezcano
2013-03-15 14:27 ` Daniel Lezcano
2013-03-15 14:27 ` [RFC patch 05/11] cpuidle / davinci : use common ARM driver Daniel Lezcano
2013-03-15 14:27 ` Daniel Lezcano
2013-03-15 14:27 ` [RFC patch 06/11] cpuidle / at91 : use common ARM cpuidle driver Daniel Lezcano
2013-03-15 14:27 ` Daniel Lezcano
2013-03-15 14:27 ` [RFC patch 07/11] cpuidle / shmobile " Daniel Lezcano
2013-03-15 14:27 ` Daniel Lezcano
2013-03-15 14:27 ` [RFC patch 08/11] cpuidle / imx " Daniel Lezcano
2013-03-15 14:27 ` Daniel Lezcano
2013-03-15 14:27 ` [RFC patch 09/11] cpuidle / s3c64xx " Daniel Lezcano
2013-03-15 14:27 ` Daniel Lezcano
2013-03-15 14:27 ` [RFC patch 10/11] cpuidle / calxeda " Daniel Lezcano
2013-03-15 14:27 ` Daniel Lezcano
2013-03-15 14:27 ` [RFC patch 11/11] cpuidle / kirkwood " Daniel Lezcano
2013-03-15 14:27 ` 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=51518A22.2040801@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=andrew@lunn.ch \
--cc=ben-linux@fluff.org \
--cc=horms@verge.net.au \
--cc=jason@lakedaemon.net \
--cc=kernel@pengutronix.de \
--cc=kevin.hilman@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=lenb@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=magnus.damm@gmail.com \
--cc=nsekhar@ti.com \
--cc=plagnioj@jcrosoft.com \
--cc=rjw@sisk.pl \
--cc=rob.herring@calxeda.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.