From: Kevin Hilman <khilman@deeprootsystems.com>
To: HU TAO-TGHK48 <taohu@motorola.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: FW: [RFC][PATCH]: Adding support for omap-serail driver
Date: Thu, 10 Sep 2009 08:57:49 -0700 [thread overview]
Message-ID: <87ws46aj2a.fsf@deeprootsystems.com> (raw)
In-Reply-To: <F12CE1A68F023D498A2691C7B539311503935BC4@ZMY16EXM66.ds.mot.com> (HU TAO-TGHK's message of "Tue\, 1 Sep 2009 01\:32\:45 +0800")
"HU TAO-TGHK48" <taohu@motorola.com> writes:
> Resend to linux-omap
>
> -----Original Message-----
> From: HU TAO-TGHK48
> Sent: Monday, August 31, 2009 7:50 PM
> To: 'vimal singh'; linux-omap@vger.kernel.org; LKML;
> linux-serial@vger.kernel.org
> Cc: Ye Yuan.Bo-A22116; Chen Xiaolong-A21785
> Subject: RE: [RFC][PATCH]: Adding support for omap-serail driver
>
>
> 1. Shall we cleanup PM related stuff in arch/arm/mach-omap2/serial.c as
> well?
> Originally serail.c register UART IRQ to decide if UART idle for a
> while and is able to enter low power mode (e.g. retention).
> To work with original 8250 driver, it is probably the only way since
> 8250 is not aware of OMAP PM.
>
> However it would be more reasonable to merge PM stuff to
> omap-serial.c. since the new driver is already OMAP specific
>
> 2. There is an issue for DMA with current implementation in serial.c
> When Rx DMA is active NO Rx IRQ will be generated.
> So serial.c will easily set uart->can_sleep with "1" even there is
> Rx DMA ongoing
> + if ((iir & 0x4) && up->use_dma) {
> + up->ier &= ~UART_IER_RDI;
> + serial_out(up, UART_IER, up->ier
>
> In my view, the best way is to do the idle detection in
> omap_serial.c.
FWIW, as the author of much of the PM hacker in mach-omap2/serial.c, I
agree with Tao.
The only reason for the PM hackery in mach-omap2/serial.c is because
of the limitations of the 8250 driver.
Kevin
next prev parent reply other threads:[~2009-09-10 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 17:32 FW: [RFC][PATCH]: Adding support for omap-serail driver HU TAO-TGHK48
2009-09-10 15:57 ` Kevin Hilman [this message]
2009-09-11 6:15 ` Govindraj
2009-09-11 21:25 ` Kevin Hilman
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=87ws46aj2a.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=taohu@motorola.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.