From: Tony Lindgren <tony@atomide.com>
To: Konstantin Baydarov <kbaidarov@dev.rtsoft.ru>
Cc: balbi@ti.com, kishon@ti.com, amit.kucheria@linaro.org,
linux-pm@lists.linux-foundation.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [linux-pm] [PATCH v4 2/4] mfd: omap: control: core system control driver
Date: Wed, 8 Aug 2012 23:18:13 -0700 [thread overview]
Message-ID: <20120809061813.GK11011@atomide.com> (raw)
In-Reply-To: <50227ED9.3010508@dev.rtsoft.ru>
* Konstantin Baydarov <kbaidarov@dev.rtsoft.ru> [120808 07:59]:
> On 08/08/2012 06:39 PM, Tony Lindgren wrote:
>
> Yes, omap_type() is called very early , that is why I'm using early_initcall
> for omap_control_base initialization.
>
> Do you mean following?:
> void __init omap2_set_globals_control(struct omap_globals *omap2_globals)
> {
> if (omap2_globals->ctrl)
> omap2_ctrl_base = omap2_globals->ctrl;
>
> if (omap2_globals->ctrl_pad)
> omap4_ctrl_pad_base = omap2_globals->ctrl_pad;
>
> omap_control_base = omap2_ctrl_base; // this line is added
> }
OK so we already have set_globals_control, but we're not using it..
No need for this line is added above.
Let's do the attached clean-up patch and just leave omap_control_base
out of the driver for now as it's not currently needed there.
If omap_control_base is needed in the driver, then we need to pass
it in the platform_data to the driver for the non-DT boot case, or
parse it from DT like you're doing.
Regards,
Tony
From: Tony Lindgren <tony@atomide.com>
Date: Wed, 8 Aug 2012 23:13:03 -0700
Subject: [PATCH] ARM: OMAP2+: Change omap_type() to use omap_ctrl_base_get()
We have the SoC specific ctrl_base already initialized in
set_globals.
Signed-off-by: Tony Lindgren <tony@atomide.com>
--- a/arch/arm/mach-omap2/id.c
+++ b/arch/arm/mach-omap2/id.c
@@ -42,28 +42,20 @@ int omap_type(void)
{
u32 val = 0;
- if (cpu_is_omap24xx()) {
- val = omap_ctrl_readl(OMAP24XX_CONTROL_STATUS);
- } else if (soc_is_am33xx()) {
- val = omap_ctrl_readl(AM33XX_CONTROL_STATUS);
- } else if (cpu_is_omap34xx()) {
- val = omap_ctrl_readl(OMAP343X_CONTROL_STATUS);
- } else if (cpu_is_omap44xx()) {
- val = omap_ctrl_readl(OMAP4_CTRL_MODULE_CORE_STATUS);
- } else if (soc_is_omap54xx()) {
- val = omap_ctrl_readl(OMAP5XXX_CONTROL_STATUS);
+ val = __raw_readl(omap_ctrl_base_get());
+ if (!val) {
+ pr_err("Cannot detect omap type!\n");
+ return 0;
+ }
+
+ if (soc_is_omap54xx()) {
val &= OMAP5_DEVICETYPE_MASK;
val >>= 6;
- goto out;
} else {
- pr_err("Cannot detect omap type!\n");
- goto out;
+ val &= OMAP2_DEVICETYPE_MASK;
+ val >>= 8;
}
- val &= OMAP2_DEVICETYPE_MASK;
- val >>= 8;
-
-out:
return val;
}
EXPORT_SYMBOL(omap_type);
next prev parent reply other threads:[~2012-08-09 6:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 11:05 [PATCH v4 2/4] mfd: omap: control: core system control driver Konstantin Baydarov
2012-07-25 11:07 ` Felipe Balbi
2012-08-08 14:05 ` Tony Lindgren
2012-08-08 14:10 ` Tony Lindgren
2012-08-08 14:39 ` [linux-pm] " Tony Lindgren
2012-08-08 14:59 ` Konstantin Baydarov
2012-08-09 6:18 ` Tony Lindgren [this message]
2012-08-09 11:00 ` Konstantin Baydarov
2012-08-10 8:50 ` Tony Lindgren
2012-08-29 12:33 ` AnilKumar, Chimata
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=20120809061813.GK11011@atomide.com \
--to=tony@atomide.com \
--cc=amit.kucheria@linaro.org \
--cc=balbi@ti.com \
--cc=kbaidarov@dev.rtsoft.ru \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).