From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: "David Härdeman" <david@hardeman.nu>,
"Sean Young" <sean@mess.org>, "Jarod Wilson" <jarod@wilsonet.com>,
"Alan Cox" <alan@linux.intel.com>,
linux-media@vger.kernel.org, linux-serial@vger.kernel.org,
lirc-list@lists.sourceforge.net
Subject: Re: [PATCH] [media] winbond-cir: Fix initialization
Date: Sun, 19 Aug 2012 17:00:04 +0100 [thread overview]
Message-ID: <20120819170004.579ee640@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <5026BE78.80902@redhat.com>
> > +#ifdef CONFIG_SERIAL_8250
Coule be modular
> > + if (!io) {
> > + struct uart_port port = { .iobase = data->sbase };
> > + int line = serial8250_find_port(&port);
> > + if (line >= 0) {
> > + serial8250_unregister_port(line);
>
> Hmm... Not sure if it makes sense, but perhaps the unregistering code
> should be reverting serial8250_unregister_port(line).
Can't do that anyway it may well be busy.
> > --- a/drivers/tty/serial/8250/8250.c
> > +++ b/drivers/tty/serial/8250/8250.c
> > @@ -2914,6 +2914,7 @@ int serial8250_find_port(struct uart_port *p)
> > }
> > return -ENODEV;
> > }
> > +EXPORT_SYMBOL(serial8250_find_port);
No - this leaks all the uart internal abstractions into the tree. We
really don't want that happening.
The right way to fix this (and a couple of other uglies) is to make 8250
on x86 scan for PnP ports *before* generic ports and to make a note of
any ports to skip on the PnP scan (so that the port poking scan ignores
them too)
Alan
next prev parent reply other threads:[~2012-08-19 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 10:37 [PATCH] [media] winbond-cir: Fix initialization Sean Young
2012-08-11 20:20 ` Mauro Carvalho Chehab
2012-08-19 16:00 ` Alan Cox [this message]
2012-08-16 16:19 ` Greg KH
2012-08-16 21:16 ` Sean Young
2012-08-18 22:46 ` David Härdeman
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=20120819170004.579ee640@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@linux.intel.com \
--cc=david@hardeman.nu \
--cc=jarod@wilsonet.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lirc-list@lists.sourceforge.net \
--cc=mchehab@redhat.com \
--cc=sean@mess.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.