public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Clouter <alex@digriz.org.uk>
To: linux-kernel@vger.kernel.org
Cc: linux-serial@vger.kernel.org,
	linux-mips@linux-mips.orglinux-serial@vger.kernel.org
Subject: Re: [PATCH 8/8] 8250: add Texas Instruments AR7 internal UART
Date: Thu, 11 Jun 2009 12:27:19 +0100	[thread overview]
Message-ID: <n967g6-i6b.ln1@woodchuck.wormnet.eu> (raw)
In-Reply-To: 20090611093022.GA14510@alpha.franken.de

In gmane.linux.ports.mips.general Thomas Bogendoerfer <tsbogend@alpha.franken.de> wrote:
>
> On Thu, Jun 11, 2009 at 10:28:39AM +0200, Florian Fainelli wrote:
>> Le Friday 05 June 2009 00:20:20 Thomas Bogendoerfer, vous avez écrit :
>> > On Thu, Jun 04, 2009 at 04:22:46PM +0200, Florian Fainelli wrote:
>> > > We discussed that in private, there are a couple of things
>> > > to fix in order to get 8250 working properly with TI AR7 HW.
>> > > If you can still merge that bit, this would ease future work, thanks !
>> >
>> > I still have a tree here, which works without any changes to the 8250
>> > serial driver on a TNETD7300 device.
>> 
>> Could you show me how you register the 8250 driver ? Without the 8250-specific 
> 
> static struct plat_serial8250_port uart0_data = {
>        .mapbase = AR7_REGS_UART0,
>        .irq = AR7_IRQ_UART0,
>        .regshift = 2,
>        .iotype = UPIO_MEM,
>        .flags = UPF_BOOT_AUTOCONF | UPF_IOREMAP,
> };
> 
>        uart_port[0].type = PORT_16550A;
>        uart_port[0].line = 0;
>        uart_port[0].irq = AR7_IRQ_UART0;
>        uart_port[0].uartclk = ar7_bus_freq() / 2;
>        uart_port[0].iotype = UPIO_MEM;
>        uart_port[0].mapbase = AR7_REGS_UART0 + 3;
>        uart_port[0].membase = ioremap(uart_port[0].mapbase, 256);
>        uart_port[0].regshift = 2;
>        res = early_serial_setup(&uart_port[0]);
>        if (res)
>                return res;
> 
> 
> the +3 comes from the fact, that this machine is configured to run big
> endian.
>
Alternatively you could not use the byte ordering macro/functions as per 
the 'Byte Order' section in:

http://lwn.net/images/pdf/LDD3/ch11.pdf

Makes the code portable, understandable and...well neater.

Cheers

-- 
Alexander Clouter
.sigmonster says: Life is like a diaper -- short and loaded.

  reply	other threads:[~2009-06-11 11:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 14:22 [PATCH 8/8] 8250: add Texas Instruments AR7 internal UART Florian Fainelli
2009-06-04 22:20 ` Thomas Bogendoerfer
2009-06-05 13:52   ` Florian Fainelli
2009-06-06 17:25   ` Florian Fainelli
2009-06-11  8:28   ` Florian Fainelli
2009-06-11  9:30     ` Thomas Bogendoerfer
2009-06-11 11:27       ` Alexander Clouter [this message]
2009-06-11 12:41         ` Alexander Clouter
2009-06-14 11:18       ` Florian Fainelli

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=n967g6-i6b.ln1@woodchuck.wormnet.eu \
    --to=alex@digriz.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.orglinux-serial \
    --cc=linux-serial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox