From: Rodolfo Giometti <giometti@linux.it>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] 8250_early console support for au1x00 (again)
Date: Wed, 30 Aug 2006 12:53:12 +0200 [thread overview]
Message-ID: <20060830105312.GF27010@gundam.enneenne.com> (raw)
In-Reply-To: <44F302D5.8050809@ru.mvista.com>
> Sorry for follwing up 2 month ago, I just happen to stumble on some
> issues addresses by these patches as well. I assume you haven't tried
> sending them to Russel King?
Not yet, I just waiting for some comments. :)
> >+ switch (port->iotype) {
> >+ case UPIO_HUB6:
> >+ outb(port->hub6 - 1 + offset, port->iobase);
> >+ return inb(port->iobase + 1);
>
> This module can't handle HAB6 otherwise, so whay add it here?
Ok. I'm going to remove it.
> >+ case UPIO_MEM32:
> >+ case UPIO_AU:
> >+ return readl(port->membase + offset);
>
> NAK. readl() can't be used to read from Alchemy SOC peripherals because
> it'll break in BE mode. Alchemy automagically handles byteswap for the SOC
> peripherals.
Ok. I'm going to fix it by using au_readl() but in this case I have to
add an ifdef with au1xxx include file. Can it be acceptable?
> >@@ -142,6 +266,7 @@ static int __init parse_options(struct e
> > port->uartclk = BASE_BAUD * 16;
> > if (!strncmp(options, "mmio,", 5)) {
> > port->iotype = UPIO_MEM;
> >+ port->regshift = 0;
>
> Maybe regshift even deserves the separate (but optional) field in the
> boot option...
Mmm... I don't know. However I have to set a default value.
> >+ (port->iotype == UPIO_MEM) ? "MMIO" : \
> >+ (port->iotype == UPIO_AU) ? "AU" : "I/O port",
> >+ (port->iotype == UPIO_MEM) || \
> >+ (port->iotype == UPIO_AU) ? port->mapbase :
> > (unsigned long) port->iobase);
>
> I'd simply map UPIO_AU to "MMIO" in the message because it's memory
> mapped UART after all...
Yes, but in the kernel command line we must supply "au"... That's why
I used different string, so the user can verify whatever he/she passed
to the kernel.
> >index 17839e7..9e27aee 100644
> >--- a/drivers/serial/serial_core.c
> >+++ b/drivers/serial/serial_core.c
> >@@ -2367,6 +2367,7 @@ int uart_match_port(struct uart_port *po
> > return (port1->iobase == port2->iobase) &&
> > (port1->hub6 == port2->hub6);
> > case UPIO_MEM:
> >+ case UPIO_AU:
>
> Also needs cases for UPIO_MEM32 and UPIO_TSI.
I just added the code for au1xxx. Why should I consider those cases
also?
> >-#ifdef CONFIG_SERIAL_8250_AU1X00
> > case UPIO_AU:
> >- __raw_writel(value, up->port.membase + offset);
> >+ writel(value, up->port.membase + offset);
> > break;
> >-#endif
>
> Ditto writel().
Is __raw_writel() correct?
> WBR, Sergei
Thanks for your suggestions.
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@gnudd.com
Embedded Systems giometti@linux.it
UNIX programming phone: +39 349 2432127
next prev parent reply other threads:[~2006-08-30 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 13:45 [PATCH] 8250_early console support for au1x00 Rodolfo Giometti
2006-05-04 14:35 ` Sergei Shtylyov
2006-05-04 15:20 ` Rodolfo Giometti
2006-05-04 15:48 ` Sergei Shtylyov
2006-05-04 16:33 ` Rodolfo Giometti
2006-05-22 20:50 ` [PATCH] 8250_early console support for au1x00 (again) Rodolfo Giometti
2006-08-28 14:51 ` Sergei Shtylyov
2006-08-30 10:53 ` Rodolfo Giometti [this message]
2006-08-30 12:41 ` Sergei Shtylyov
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=20060830105312.GF27010@gundam.enneenne.com \
--to=giometti@linux.it \
--cc=linux-mips@linux-mips.org \
--cc=sshtylyov@ru.mvista.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