public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Govindraj <govindraj.ti@gmail.com>
Cc: HU TAO-TGHK48 <taohu@motorola.com>, linux-omap@vger.kernel.org
Subject: Re: FW: [RFC][PATCH]: Adding support for omap-serail driver
Date: Fri, 11 Sep 2009 14:25:30 -0700	[thread overview]
Message-ID: <8763bp5g39.fsf@deeprootsystems.com> (raw)
In-Reply-To: <d6a0f7aa0909102315r3ec682a3u9b3da26eb031ca27@mail.gmail.com> (Govindraj's message of "Fri\, 11 Sep 2009 11\:45\:02 +0530")

Govindraj <govindraj.ti@gmail.com> writes:

> Hi,
>
>>
>> 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.
>>
>
> I have an query,
>
> We have following functionality in serial.c:
> 1.) Enabling and disabling uart clocks.
> 2.) Adding rx wakeup capabilities.
> 3.) Preparing UARTs for idle mode.
> 4.) Context save and restore.
>
> What functionality should be retained in serial.c file?
>
> AFAIK currently no serial driver has incorporated their platform
> specific PM functionality like context_save and restore into their
> serial driver, shouldn't these things be retained into
> */mach-omap2/serial.c ?

Only SoC and/or board-specific settings should be done in serial.c
(setup of base addresses, IRQs, DMA channels, etc.)

The driver is an OMAP specific driver, but should be general enough to
independent of any board/SoC specifics.

IMO, all of 1-4 above above belong in the driver.  Evenutally the
enabling/disabling of clocks will be handled by the runtime PM layer,
but the driver will have a similar enable/disable API.

Kevin



      reply	other threads:[~2009-09-11 21:25 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
2009-09-11  6:15   ` Govindraj
2009-09-11 21:25     ` Kevin Hilman [this message]

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=8763bp5g39.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=govindraj.ti@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox