linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Dave Mitchell <dmitchell@amcc.com>
Cc: linuxppc-dev@ozlabs.org, arnd@arndb.de
Subject: Re: [PATCH] of_serial: Add UPF_FIXED_TYPE flag
Date: Fri, 19 Jun 2009 18:24:21 +1000	[thread overview]
Message-ID: <1245399861.10629.194.camel@concordia> (raw)
In-Reply-To: <1244590787-13716-1-git-send-email-dmitchell@amcc.com>

[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]

On Tue, 2009-06-09 at 18:39 -0500, Dave Mitchell wrote:
> This patch adds the UPF_FIXED_TYPE flag which will bypass the
> 8250's autoconfig probe for uart type. The uart type identified
> by the of_serial's parse of the flat device tree will be utilized
> as defined.
> 
> Signed-off-by: Dave Mitchell <dmitchell@amcc.com>
> ---
>  drivers/serial/of_serial.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/serial/of_serial.c b/drivers/serial/of_serial.c
> index 14f8fa9..3f2027c 100644
> --- a/drivers/serial/of_serial.c
> +++ b/drivers/serial/of_serial.c
> @@ -67,7 +67,7 @@ static int __devinit of_platform_serial_setup(struct of_device *ofdev,
>  	port->type = type;
>  	port->uartclk = *clk;
>  	port->flags = UPF_SHARE_IRQ | UPF_BOOT_AUTOCONF | UPF_IOREMAP
> -		| UPF_FIXED_PORT;
> +		| UPF_FIXED_PORT | UPF_FIXED_TYPE;

I think we /probably/ want a similar change in legacy_serial.c, for soc
ports at least.

Or do people have things that are compatible "ns16550" but aren't?

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-06-19  8:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 23:39 [PATCH] of_serial: Add UPF_FIXED_TYPE flag Dave Mitchell
2009-06-19  8:24 ` Michael Ellerman [this message]
2009-06-19 22:59   ` Benjamin Herrenschmidt

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=1245399861.10629.194.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=arnd@arndb.de \
    --cc=dmitchell@amcc.com \
    --cc=linuxppc-dev@ozlabs.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).