From: David Daney <ddaney@caviumnetworks.com>
To: "Ardelean, Andrei" <Andrei.Ardelean@idt.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Is it any serial8250 platform driver available?
Date: Mon, 25 Oct 2010 09:43:53 -0700 [thread overview]
Message-ID: <4CC5B3C9.60000@caviumnetworks.com> (raw)
In-Reply-To: <AEA634773855ED4CAD999FBB1A66D0760126B6FC@CORPEXCH1.na.ads.idt.com>
On 10/25/2010 08:37 AM, Ardelean, Andrei wrote:
> Hi David,
>
> I studied this driver and few other examples and I have one question
> regarding the driver configuration:
> Which field must be initialized in the plat_serial8250_port structure:
> unsigned long iobase; /* io base address */
> void __iomem *membase; /* ioremap cookie or NULL */
> resource_size_t mapbase; /* resource base */
> Some drivers init only one of them, other two fields.
>
> My UART is located at 0x1bf01000, can I put this value in all those
> fields?
>
As with many things in life, it depends.
In this case it depends on the flags you pass as well as any serial_in()
and serial_out() functions you may have. It is fortunate you have the
source code available, you can use it to see how the different options
affect things.
David Daney
> Thanks,
> Andrei
>
>
> -----Original Message-----
> From: David Daney [mailto:ddaney@caviumnetworks.com]
> Sent: Friday, October 22, 2010 3:31 PM
> To: Ardelean, Andrei
> Cc: linux-mips@linux-mips.org
> Subject: Re: Is it any serial8250 platform driver available?
>
> On 10/22/2010 12:23 PM, Ardelean, Andrei wrote:
>> Hi,
>>
>> I am porting MIPS Linux from MALTA to a new board. I ported early
>> console code from malta_console.c and I am looking now to use a
>> interrupt driven driver for TTY. My UART is compatible with 8250 (1
> UART
>> port only) but the UART registers are directly mapped in CPU memory
> map.
>> There is no PCI bus. My problem is that the driver implemented in
> 8250.c
>> is very complex and it seems to be hardcode for ISA bus, is it any
>> simple platform UART driver available to be directly mapped in the CPU
>> space? Can you give me some advice what would be a good approach for
> my
>> case?
>>
>
> Many chips have 8250 compatible ports and use 8250.c.
>
> See arch/mips/cavium-octeon/serial.c
>
> David Daeny
>
prev parent reply other threads:[~2010-10-25 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 19:23 Is it any serial8250 platform driver available? Ardelean, Andrei
2010-10-22 19:23 ` Ardelean, Andrei
2010-10-22 19:31 ` David Daney
2010-10-25 15:37 ` Ardelean, Andrei
2010-10-25 14:53 ` Sergei Shtylyov
2010-10-25 15:37 ` Ardelean, Andrei
2010-10-25 16:43 ` David Daney [this message]
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=4CC5B3C9.60000@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=Andrei.Ardelean@idt.com \
--cc=linux-mips@linux-mips.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