From: Kevin Hilman <khilman@ti.com>
To: "Govindraj.R" <govindraj.raja@ti.com>
Cc: linux-omap@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Tony Lindgren <tony@atomide.com>, Partha Basak <p-basak2@ti.com>,
Vishwanath Sripathy <vishwanath.bs@ti.com>,
Rajendra Nayak <rnayak@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH v8 17/20] OMAP2+: UART: Use custom activate func for console uart.
Date: Fri, 18 Nov 2011 13:24:38 -0800 [thread overview]
Message-ID: <87vcqhuns9.fsf@ti.com> (raw)
In-Reply-To: <1321005712-21871-3-git-send-email-govindraj.raja@ti.com> (Govindraj R.'s message of "Fri, 11 Nov 2011 15:31:50 +0530")
"Govindraj.R" <govindraj.raja@ti.com> writes:
> Omap-uart can be used as console uart to print early boot
> messages using earlyprintk so for console uart prevent
> hwmod reset or idling during bootup.
>
> Identify the console_uart set the id and use the custom
> pm_latency ops for console uart for the first time
> to idle console uart left enabled from bootup and then enable
> them back and reset pm_latency ops to default ops.
>
> Thanks to Kevin Hilman <khilman@ti.com> for suggesting
> this approach.
You're welcome, but Rajendra's solution is much better. ;)
Can you updated your branch without these custom hooks and using
Rajendra's INIT_NO_IDLE change to the hwmod core.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 17/20] OMAP2+: UART: Use custom activate func for console uart.
Date: Fri, 18 Nov 2011 13:24:38 -0800 [thread overview]
Message-ID: <87vcqhuns9.fsf@ti.com> (raw)
In-Reply-To: <1321005712-21871-3-git-send-email-govindraj.raja@ti.com> (Govindraj R.'s message of "Fri, 11 Nov 2011 15:31:50 +0530")
"Govindraj.R" <govindraj.raja@ti.com> writes:
> Omap-uart can be used as console uart to print early boot
> messages using earlyprintk so for console uart prevent
> hwmod reset or idling during bootup.
>
> Identify the console_uart set the id and use the custom
> pm_latency ops for console uart for the first time
> to idle console uart left enabled from bootup and then enable
> them back and reset pm_latency ops to default ops.
>
> Thanks to Kevin Hilman <khilman@ti.com> for suggesting
> this approach.
You're welcome, but Rajendra's solution is much better. ;)
Can you updated your branch without these custom hooks and using
Rajendra's INIT_NO_IDLE change to the hwmod core.
Kevin
next prev parent reply other threads:[~2011-11-18 21:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 10:01 [PATCH v8 15/20] OMAP2+: UART: Make the RX_TIMEOUT for DMA configurable for each UART Govindraj.R
2011-11-11 10:01 ` Govindraj.R
2011-11-11 10:01 ` [PATCH v8 16/20] OMAP2+: UART: remove temporary variable used to count uart instance Govindraj.R
2011-11-11 10:01 ` Govindraj.R
2011-11-11 10:01 ` [PATCH v8 17/20] OMAP2+: UART: Use custom activate func for console uart Govindraj.R
2011-11-11 10:01 ` Govindraj.R
2011-11-18 21:24 ` Kevin Hilman [this message]
2011-11-18 21:24 ` Kevin Hilman
2011-11-21 13:47 ` Govindraj
2011-11-21 13:47 ` Govindraj
2011-11-21 13:51 ` Govindraj
2011-11-21 13:51 ` Govindraj
2011-11-11 10:01 ` [PATCH v8 18/20] OMAP2+: UART: Avoid uart idling on suspend for no_console_suspend usecase Govindraj.R
2011-11-11 10:01 ` Govindraj.R
2011-11-11 10:01 ` [PATCH v8 19/20] OMAP2+: UART: Do not gate uart clocks if used for debug_prints Govindraj.R
2011-11-11 10:01 ` Govindraj.R
2012-01-02 9:25 ` Bedia, Vaibhav
2012-01-02 9:25 ` Bedia, Vaibhav
2012-01-02 10:30 ` Govindraj
2012-01-02 10:30 ` Govindraj
2012-01-03 10:24 ` Bedia, Vaibhav
2012-01-03 10:24 ` Bedia, Vaibhav
2012-01-03 10:31 ` Govindraj
2012-01-03 10:31 ` Govindraj
2012-01-03 11:52 ` Bedia, Vaibhav
2012-01-03 11:52 ` Bedia, Vaibhav
2012-01-03 14:12 ` Govindraj
2012-01-03 14:12 ` 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=87vcqhuns9.fsf@ti.com \
--to=khilman@ti.com \
--cc=govindraj.raja@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=p-basak2@ti.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
--cc=vishwanath.bs@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.