From: Govindraj <govindraj.ti@gmail.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Govindraj.R" <govindraj.raja@ti.com>, linux-omap@vger.kernel.org
Subject: Re: [pm-wip/uart][PATCH] Serial: Avoid populating uart_list in early init phase
Date: Wed, 30 Jun 2010 20:13:04 +0530 [thread overview]
Message-ID: <AANLkTimHkAujlsEXf7dbkek48yltLe8w-ajeMWNqzShL@mail.gmail.com> (raw)
In-Reply-To: <871vbvt72x.fsf@deeprootsystems.com>
>
> Your inline patch is still getting mangled somehow. It looks like
> you're using a webmail client (SquirrelMail) that seems to be altering
> the whitespace in the patch. The attached .zip worked fine. Please
> spend some time figuring out how to use git send-email directly
>
Have been trying to setup git-send quite some time, but firewall is blocking.
Will try to get this enabled somehow.
> However, I just discovered another snag...
>
> I did some more testing on Zoom3 and discovered that because we do the
> HWMOD_INIT_NO_IDLE, and omap_serial_init[_port] is never called on Zoom3
> (since it only uses debug board UART) the UART hwmods are left active
> are never disabled (since they are not used.) This prevents retention :(
>
Yes I was able to reproduce this as said.
But I was trying to set this option from flags field from uart_hmwod
in omap_hwmod data file as below
.flags = (HWMOD_INIT_NO_IDLE | HWMOD_INIT_NO_RESET),
But strangely it doesn't work, but works only when we set the flag
from serial_early_init phase
any idea why so?
It was hitting retention for zoom2 with earlier suggested changes as
below: [ttyS3->console]
diff --git a/arch/arm/mach-omap2/board-zoom-debugboard.c
b/arch/arm/mach-omap2/board-zoom-debugboard.c
index 1d7f827..9307f58 100644
--- a/arch/arm/mach-omap2/board-zoom-debugboard.c
+++ b/arch/arm/mach-omap2/board-zoom-debugboard.c
@@ -96,7 +96,7 @@ static struct plat_serial8250_port serial_platform_data[] = {
static struct platform_device zoom_debugboard_serial_device = {
.name = "serial8250",
- .id = PLAT8250_DEV_PLATFORM,
+ .id = PLAT8250_DEV_PLATFORM + 4,
.dev = {
.platform_data = serial_platform_data,
},
diff --git a/arch/arm/mach-omap2/board-zoom2.c
b/arch/arm/mach-omap2/board-zoom2.c
index 803ef14..c858b43 100644
--- a/arch/arm/mach-omap2/board-zoom2.c
+++ b/arch/arm/mach-omap2/board-zoom2.c
@@ -80,6 +80,7 @@ static struct omap_board_mux board_mux[] __initdata = {
static void __init omap_zoom2_init(void)
{
omap3_mux_init(board_mux, OMAP_PACKAGE_CBB);
+ omap_serial_init();
zoom_peripherals_init();
zoom_debugboard_init();
}
---
Regards,
Govindraj.R
--
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
next prev parent reply other threads:[~2010-06-30 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 12:55 [pm-wip/uart][PATCH v3] Serial: Avoid using hwmod lookup using name string Govindraj.R
2010-06-24 22:33 ` Kevin Hilman
2010-06-25 13:41 ` [pm-wip/uart][PATCH] Serial: Avoid populating uart_list in early init phase Govindraj.R
2010-06-25 16:23 ` Kevin Hilman
2010-06-30 14:43 ` Govindraj [this message]
2010-06-26 16:08 ` DebBarma, Tarun Kanti
2010-06-28 12:18 ` Govindraj
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=AANLkTimHkAujlsEXf7dbkek48yltLe8w-ajeMWNqzShL@mail.gmail.com \
--to=govindraj.ti@gmail.com \
--cc=govindraj.raja@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.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).