public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Juha Yrjola <juha.yrjola@solidboot.com>
To: "Syed Mohammed, Khasim" <x0khasim@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] serial: Add driver for OMAP UARTs
Date: Tue, 10 Apr 2007 13:07:24 +0300	[thread overview]
Message-ID: <461B61DC.6050005@solidboot.com> (raw)
In-Reply-To: <9C23CDD79DA20A479D4615857B2E2C47A1A4FB@dlee13.ent.ti.com>

Hi Khasim,

Syed Mohammed, Khasim wrote:

> One concern I had here was, as we know OMAP supports multiple (3)
> UART  ports and they can be used for IrDA (UART3), Bluetooth (UART2/1),
 > Serial applications etc. All these drivers should configure/use
> similar register sets. So if we could,
> 
> - make the arch/arm/mach-omap2/serial.c more kind of a generic UART
>   API library that can be used by all UART drivers.
> 	- the UART library should handle overall clock /power management policy.
> 	- Centralized interrupt handler.
> 	- DMA / Polling / Interrupt based read/writes.

It is certainly a good idea.  You probably meant to write 
plat-omap/serial.c, since obviously the implementation shouldn't be 
limited to OMAP2.

I suppose the UART library will not be trivial, though.  I don't know 
what kind of special needs Bluetooth and IrDA have, but for example the 
serial console code needs specific handling for the Magic SysRQ 
characters in the RX loop.  The N800 Bluetooth driver does some funky 
stuff related to PM, as well.

Cheers,
Juha

  reply	other threads:[~2007-04-10 10:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 20:44 [PATCH] serial: Add driver for OMAP UARTs Juha Yrjölä
2007-04-10  5:36 ` Syed Mohammed, Khasim
2007-04-10 10:07   ` Juha Yrjola [this message]
2007-04-10 12:28 ` Ville Tervo
2007-04-12 13:37 ` George G. Davis
2007-04-12 14:23   ` Testing SPI on omap5912 Raja Mallik
2007-04-17 20:06   ` [PATCH] serial: Add driver for OMAP UARTs Tony Lindgren

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=461B61DC.6050005@solidboot.com \
    --to=juha.yrjola@solidboot.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=x0khasim@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox