All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Govindraj <govindraj.ti@gmail.com>
Cc: "Govindraj.R" <govindraj.raja@ti.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCHv3 1/3] OMAP UART: Add omap-serial driver support.
Date: Wed, 09 Dec 2009 14:33:15 -0800	[thread overview]
Message-ID: <87ljhbu6ac.fsf@deeprootsystems.com> (raw)
In-Reply-To: <d6a0f7aa0912020543s7f8310fdueb0a3a6c52df1326@mail.gmail.com> (Govindraj's message of "Wed\, 2 Dec 2009 19\:13\:25 +0530")

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

> On Wed, Nov 25, 2009 at 12:18 AM, Kevin Hilman
> <khilman@deeprootsystems.com> wrote:
>> "Govindraj.R" <govindraj.raja@ti.com> writes:
>>
>>> From 4756e3743c7acd2de1030b2bd432c1b19f0b9ff5 Mon Sep 17 00:00:00 2001
>>> From: Govindraj R <govindraj.raja@ti.com>
>>> Date: Fri, 13 Nov 2009 12:01:54 +0530
>>> Subject: [PATCH] OMAP UART: Add omap-serial driver support.
>>>
>>> This patch adds support for OMAP3430-HIGH SPEED UART Controller.
>>>
>>> It adds support for the following features:
>>> 1. It supports Interrupt mode and DMA mode of operation.
>>> 2. Supports Hardware flow control and sofware flow control.
>>> 3. Debug Console support on all UARTs.
>>>
>>> Signed-off-by: Govindraj R <govindraj.raja@ti.com>
>>
>> Some general comments.
>>
>> This should summarize how this is different from the 8250 driver on
>> which it was based, as it's clear that it was based on 8250 but not
>> clear at all what the changes are.
>>
>> At first glance, you've dropped several features from the 8250 driver
>> which we currently use.  Namely, the ability for platform code to
>> override some of the defaults:
>>
>> - change irq_flags
>> - serial_in function
>> - optional ioremapping (omap_hwmod layer will have done ioremap already)
>
>
> Agree. uart_port_info [should be renamed to omap_uart_port_info]
> should grow with fields like irqflags, membase and mapbase feilds.
>
> adding these would need rework on the patch:
> http://patchwork.kernel.org/patch/62555/
>
> Should I work on top of above patch?

Yes.

> Serial in function might not be necessary for omap-serial driver,
> this function was added to handle RX reading by checking if DR bit set
> in LSR reg.
>
> This is taken care in omap-serial driver.

OK, I didn't look closely at that but I'd like to be sure that the
extra checking can be optimized out on the SoCs that don't need it.

Kevin

--
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

  reply	other threads:[~2009-12-09 22:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <35817.192.168.10.88.1256713980.squirrel@dbdmail.itg.ti.com>
2009-11-13  6:53 ` [PATCHv3 1/3] OMAP UART: Add omap-serial driver support Govindraj.R
2009-11-23 17:11   ` Artem Bityutskiy
2009-11-26  4:55     ` Govindraj
2009-11-24 18:48   ` Kevin Hilman
2009-12-02 13:43     ` Govindraj
2009-12-09 22:33       ` Kevin Hilman [this message]
2009-11-24 19:58   ` 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=87ljhbu6ac.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=govindraj.raja@ti.com \
    --cc=govindraj.ti@gmail.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 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.