xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Chen Baozi <baozich@gmail.com>,
	Xen Developer List <xen-devel@lists.xen.org>
Subject: Re: [PATCH v8 4/6] xen/arm: Add the new OMAP UART driver.
Date: Thu, 22 Aug 2013 14:21:03 +0100	[thread overview]
Message-ID: <5216103F.2070803@linaro.org> (raw)
In-Reply-To: <1377166823.31937.105.camel@hastur.hellion.org.uk>

On 08/22/2013 11:20 AM, Ian Campbell wrote:
> On Tue, 2013-08-13 at 19:14 +0800, Chen Baozi wrote:
>> TI OMAP UART introduces some features such as register access modes, which
>> makes its configuration and interrupt handling differs from 8250 compatible
>> UART. Thus, we seperate this driver from ns16550's implementation.
>>
>> Signed-off-by: Chen Baozi <baozich@gmail.com>
> 
> Acked-by: Ian Campbell <ian.campbell@citrix.com>
> 
>> @@ -11,6 +11,7 @@ CFLAGS += -marm
>>  
>>  HAS_PL011 := y
>>  HAS_EXYNOS4210 := y
>> +HAS_OMAP := y
> 
> All three of these would be better with a _UART suffix IMHO, the
> HAS_OMAP makes it particularly obvious...
> 
> Would you mind making this change (in a follow up patch)?
> 
> [...]
>> +static int __init omap_uart_irq(struct serial_port *port)
>> +{
>> +    struct omap_uart *uart = port->uart;
>> +
>> +    return ((uart->irq.irq > 0) ? uart->irq.irq : -1);
>> +}
>> +[..]
>> +static struct uart_driver __read_mostly omap_uart_driver = {
> [...]
>> +    .irq = omap_uart_irq,
>> +    .dt_irq_get = omap_uart_dt_irq,
> [...]
> 
> This is really a question for Julien: Does a driver which is DT only
> need to provide the irq hook or is dt_irq sufficient?

dt_irq callback is enough. Other other DT drivers implement the irq
callback, which is not used by Xen on ARM.

I'm wondering if we can ifdef the irq callback (and so serial_irq) in
this case for ARM?

-- 
Julien Grall

  reply	other threads:[~2013-08-22 13:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 11:14 [PATCH v8 8/5] Add UART support and arch timer initialization for OMAP5 Chen Baozi
2013-08-13 11:14 ` [PATCH v8 1/6] xen: rename ns16550-uart.h to 8250-uart.h and fix some typos Chen Baozi
2013-08-13 11:14 ` [PATCH v8 2/6] xen/arm: add 8250 compatible UART support for early_printk Chen Baozi
2013-08-22 10:14   ` Ian Campbell
2013-08-13 11:14 ` [PATCH v8 3/6] xen: Introduce a helper to read a u32 property in device tree Chen Baozi
2013-08-13 11:14 ` [PATCH v8 4/6] xen/arm: Add the new OMAP UART driver Chen Baozi
2013-08-22 10:20   ` Ian Campbell
2013-08-22 13:21     ` Julien Grall [this message]
2013-08-22 14:03       ` Ian Campbell
2013-08-23  0:05     ` Chen Baozi
2013-08-13 11:14 ` [PATCH v8 5/6] xen/arm: Add support for device tree specified arch_timer clock frequency Chen Baozi
2013-08-13 11:14 ` [PATCH v8 6/6] xen/arm: Platform recognition and initialize arch_timer for the OMAP5 Chen Baozi
2013-08-22 12:52 ` [PATCH v8 8/5] Add UART support and arch timer initialization for OMAP5 Ian Campbell
2013-08-22 23:58   ` Chen Baozi

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=5216103F.2070803@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=baozich@gmail.com \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).