From: Shmulik Ladkani <shmulik@jungo.com>
To: linux-serial@vger.kernel.org
Cc: shmulik@jungo.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: copy UART properties of UPF_FIXED_TYPE ports provisioned using early_serial_setup
Date: Tue, 27 Oct 2009 13:52:05 +0200 [thread overview]
Message-ID: <20091027135205.74bbf5f7@pixies.home.jungo.com> (raw)
In-Reply-To: <dzvMe-7Mg-3@gated-at.bofh.it>
On Mon, 26 Oct 2009 12:20:02 +0100 Shmulik Ladkani <shmulik@jungo.com> wrote:
> Augment the UPF_FIXED_TYPE logic, which currently applies to UART ports
> provisioned using platform_device_register.
>
> The suggested patch applies same logic into 'serial8250_register_ports',
> making UART ports provisioned using early_serial_setup inherit their
> properties from the uart_config entry.
>
> The patch applies to linux-2.6.32-rc5
Re-submit (previous mailer messed-up whitespace).
Signed-off-by: Shmulik Ladkani <shmulik@jungo.com>
---
diff -upr linux-2.6.32-rc5.clean/drivers/serial/8250.c linux-2.6.32-rc5/drivers/serial/8250.c
--- linux-2.6.32-rc5.clean/drivers/serial/8250.c 2009-10-16 02:41:50.000000000 +0200
+++ linux-2.6.32-rc5/drivers/serial/8250.c 2009-10-26 11:36:09.000000000 +0200
@@ -2704,6 +2704,14 @@ serial8250_register_ports(struct uart_dr
struct uart_8250_port *up = &serial8250_ports[i];
up->port.dev = dev;
+
+ if (up->port.flags & UPF_FIXED_TYPE) {
+ up->port.fifosize =
+ uart_config[up->port.type].fifo_size;
+ up->capabilities = uart_config[up->port.type].flags;
+ up->tx_loadsz = uart_config[up->port.type].tx_loadsz;
+ }
+
uart_add_one_port(drv, &up->port);
}
}
--
Shmulik Ladkani Jungo Ltd.
next parent reply other threads:[~2009-10-27 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dzvMe-7Mg-3@gated-at.bofh.it>
2009-10-27 11:52 ` Shmulik Ladkani [this message]
2009-10-26 10:50 [PATCH] serial: copy UART properties of UPF_FIXED_TYPE ports provisioned using early_serial_setup Shmulik Ladkani
2009-10-29 5:47 ` Andrew Morton
2009-10-29 17:07 ` Shmulik Ladkani
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=20091027135205.74bbf5f7@pixies.home.jungo.com \
--to=shmulik@jungo.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).