From: Vishwanath Sripathy <vishwanath.bs@ti.com>
To: jean.pihet@newoldbits.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Kevin Hilman <khilman@ti.com>
Cc: Nishanth Menon <nm@ti.com>, Jean Pihet-XID <j-pihet@ti.com>
Subject: RE: [PATCH 6/6] ARM: OMAP3+: SmartReflex Class3: restrict CPU to run on
Date: Tue, 13 Mar 2012 16:04:13 +0530 [thread overview]
Message-ID: <ef588847b5162cc1174c7cdeffc74ffd@mail.gmail.com> (raw)
In-Reply-To: <1331634381-31436-7-git-send-email-j-pihet@ti.com>
> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of jean.pihet@newoldbits.com
> Sent: Tuesday, March 13, 2012 3:56 PM
> To: linux-omap@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org; Kevin Hilman
> Cc: Nishanth Menon; Jean Pihet
> Subject: [PATCH 6/6] ARM: OMAP3+: SmartReflex Class3: restrict CPU
> to run on
>
> From: Nishanth Menon <nm@ti.com>
>
> Use SmartReflex AVS Class3 initialization only for OMAP343x family
> of
> processors.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> Signed-off-by: Jean Pihet <j-pihet@ti.com>
> ---
> arch/arm/mach-omap2/smartreflex-class3.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/smartreflex-class3.c
> b/arch/arm/mach-omap2/smartreflex-class3.c
> index 9dcda93..735937a 100644
> --- a/arch/arm/mach-omap2/smartreflex-class3.c
> +++ b/arch/arm/mach-omap2/smartreflex-class3.c
> @@ -11,6 +11,7 @@
> * published by the Free Software Foundation.
> */
>
> +#include <plat/cpu.h>
> #include "smartreflex.h"
>
> static int sr_class3_enable(struct voltagedomain *voltdm,
> @@ -58,6 +59,10 @@ static struct omap_sr_class_data class3_data = {
> /* Smartreflex Class3 init API to be called from board file */
> static int __init sr_class3_init(void)
> {
> + /* Enable this class only for OMAP343x */
> + if (!cpu_is_omap343x())
> + return -EINVAL;
Wouldn't this break SR on OMAP3630 and OMAP4? Shouldn't this be done once
you have SR1.5 support in mainline?
Vishwa
> +
> pr_info("SmartReflex Class3 initialized\n");
> return sr_register_class(&class3_data);
> }
> --
> 1.7.5.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-
> omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: vishwanath.bs@ti.com (Vishwanath Sripathy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/6] ARM: OMAP3+: SmartReflex Class3: restrict CPU to run on
Date: Tue, 13 Mar 2012 16:04:13 +0530 [thread overview]
Message-ID: <ef588847b5162cc1174c7cdeffc74ffd@mail.gmail.com> (raw)
In-Reply-To: <1331634381-31436-7-git-send-email-j-pihet@ti.com>
> -----Original Message-----
> From: linux-omap-owner at vger.kernel.org [mailto:linux-omap-
> owner at vger.kernel.org] On Behalf Of jean.pihet at newoldbits.com
> Sent: Tuesday, March 13, 2012 3:56 PM
> To: linux-omap at vger.kernel.org; linux-arm-
> kernel at lists.infradead.org; Kevin Hilman
> Cc: Nishanth Menon; Jean Pihet
> Subject: [PATCH 6/6] ARM: OMAP3+: SmartReflex Class3: restrict CPU
> to run on
>
> From: Nishanth Menon <nm@ti.com>
>
> Use SmartReflex AVS Class3 initialization only for OMAP343x family
> of
> processors.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> Signed-off-by: Jean Pihet <j-pihet@ti.com>
> ---
> arch/arm/mach-omap2/smartreflex-class3.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/smartreflex-class3.c
> b/arch/arm/mach-omap2/smartreflex-class3.c
> index 9dcda93..735937a 100644
> --- a/arch/arm/mach-omap2/smartreflex-class3.c
> +++ b/arch/arm/mach-omap2/smartreflex-class3.c
> @@ -11,6 +11,7 @@
> * published by the Free Software Foundation.
> */
>
> +#include <plat/cpu.h>
> #include "smartreflex.h"
>
> static int sr_class3_enable(struct voltagedomain *voltdm,
> @@ -58,6 +59,10 @@ static struct omap_sr_class_data class3_data = {
> /* Smartreflex Class3 init API to be called from board file */
> static int __init sr_class3_init(void)
> {
> + /* Enable this class only for OMAP343x */
> + if (!cpu_is_omap343x())
> + return -EINVAL;
Wouldn't this break SR on OMAP3630 and OMAP4? Shouldn't this be done once
you have SR1.5 support in mainline?
Vishwa
> +
> pr_info("SmartReflex Class3 initialized\n");
> return sr_register_class(&class3_data);
> }
> --
> 1.7.5.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-
> omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-13 10:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 10:26 [PATCH 0/6] ARM: OMAP3+: smartreflex: add class support jean.pihet
2012-03-13 10:26 ` jean.pihet at newoldbits.com
2012-03-13 10:26 ` [PATCH 1/6] ARM: OMAP3+: SmartReflex: introduce class init, deinit and priv data jean.pihet
2012-03-13 10:26 ` jean.pihet at newoldbits.com
2012-03-13 10:26 ` [PATCH 2/6] ARM: OMAP3+: SmartReflex: introduce notifiers flags jean.pihet
2012-03-13 10:26 ` jean.pihet at newoldbits.com
2012-03-13 10:26 ` [PATCH 3/6] ARM: OMAP3+: SmartReflex: introduce notifier_control jean.pihet
2012-03-13 10:26 ` jean.pihet at newoldbits.com
2012-03-13 17:40 ` Menon, Nishanth
2012-03-13 17:40 ` Menon, Nishanth
2012-03-13 10:26 ` [PATCH 4/6] ARM: OMAP3+: SmartReflex: disable spamming interrupts jean.pihet
2012-03-13 10:26 ` jean.pihet at newoldbits.com
2012-03-13 10:26 ` [PATCH 5/6] ARM: OMAP3+: SmartReflex: introduce class private data per voltage domain jean.pihet
2012-03-13 10:26 ` jean.pihet at newoldbits.com
2012-03-13 10:26 ` [PATCH 6/6] ARM: OMAP3+: SmartReflex Class3: restrict CPU to run on jean.pihet
2012-03-13 10:26 ` jean.pihet at newoldbits.com
2012-03-13 10:34 ` Vishwanath Sripathy [this message]
2012-03-13 10:34 ` Vishwanath Sripathy
2012-03-13 17:31 ` [PATCH 0/6] ARM: OMAP3+: smartreflex: add class support Tony Lindgren
2012-03-13 17:31 ` Tony Lindgren
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=ef588847b5162cc1174c7cdeffc74ffd@mail.gmail.com \
--to=vishwanath.bs@ti.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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.