Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: "Ardelean, Andrei" <Andrei.Ardelean@idt.com>
Cc: David Daney <ddaney@caviumnetworks.com>, linux-mips@linux-mips.org
Subject: Re: Is it any serial8250 platform driver available?
Date: Mon, 25 Oct 2010 18:53:34 +0400	[thread overview]
Message-ID: <4CC599EE.2000102@mvista.com> (raw)
In-Reply-To: <AEA634773855ED4CAD999FBB1A66D0760126B6FC@CORPEXCH1.na.ads.idt.com>

Hello.

[Resending to the list as I've only replied to Andrei -- due to stupid keyboard 
layout switcher in  OpenSUSE preventing Ctrl-Shift-R in Thunderbird from 
working... :-/]

On 25-10-2010 19:37, 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.

    Of course, .iobase is for I/O port mapped UARTs (think PC), .mapbase and 
.membase are for the memory mapped UARTs (like your case).

> My UART is located at 0x1bf01000, can I put this value in all those
> fields?

    You only need to put that into ,mapbase.

> Thanks,
> Andrei

WBR, Sergei

  reply	other threads:[~2010-10-25 16:56 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 [this message]
2010-10-25 15:37     ` Ardelean, Andrei
2010-10-25 16:43     ` David Daney

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=4CC599EE.2000102@mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=Andrei.Ardelean@idt.com \
    --cc=ddaney@caviumnetworks.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