From: Alex Williamson <alex.williamson@hp.com>
To: rmk+serial@arm.linux.org.uk
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] set membase in serial8250_request_port
Date: Thu, 28 Oct 2004 13:24:55 -0600 [thread overview]
Message-ID: <1098991495.2719.8.camel@tdi> (raw)
In-Reply-To: <1098111389.30201.7.camel@tdi>
The iounmap/ioremap path in serial8250_release/request_port is
terribly unbalanced. The UPF_IOREMAP flag is used to determine if a
port gets ioremap'd, but plays no part in whether it gets iounmap'd.
It's easy to see how an MMIO serial port can be passed through
uart_set_info and end up with an unmapped membase. The results is a
non-functional UART or worse. I've tried to generate some discussion on
the proper fix for this, but I haven't succeeded. I propose the patch
below as a safe compromise. An MMIO uart w/ a mapbase, but no membase
doesn't seem viable to me. Thanks,
Alex
--
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
===== drivers/serial/8250.c 1.77 vs edited =====
--- 1.77/drivers/serial/8250.c 2004-10-25 06:05:26 -06:00
+++ edited/drivers/serial/8250.c 2004-10-28 13:18:01 -06:00
@@ -1858,7 +1858,11 @@
/*
* If we have a mapbase, then request that as well.
*/
- if (ret == 0 && up->port.flags & UPF_IOREMAP) {
+ if (ret == 0 && ((up->port.flags & UPF_IOREMAP) ||
+ (up->port.iotype == UPIO_MEM &&
+ up->port.mapbase &&
+ !up->port.membase))) {
+
int size = res->end - res->start + 1;
up->port.membase = ioremap(up->port.mapbase, size);
next prev parent reply other threads:[~2004-10-28 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 18:54 [PATCH] set membase in serial8250_request_port Alex Williamson
2004-10-04 21:04 ` Russell King
2004-10-04 21:43 ` Alex Williamson
2004-10-18 14:56 ` Alex Williamson
2004-10-28 19:24 ` Alex Williamson [this message]
2004-10-30 10:28 ` Russell King
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=1098991495.2719.8.camel@tdi \
--to=alex.williamson@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+serial@arm.linux.org.uk \
/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