From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Helge Deller <deller@gmx.de>,
Frank Scheiner <frank.scheiner@web.de>,
linux-parisc@vger.kernel.org,
John David Anglin <dave.anglin@bell.net>,
linux-serial@vger.kernel.org
Cc: debian-hppa@lists.debian.org
Subject: Re: Have my PA8800 back online... (serial port missing on v4.14)
Date: Wed, 13 Dec 2017 17:16:50 +0200 [thread overview]
Message-ID: <1513178210.7000.34.camel@linux.intel.com> (raw)
In-Reply-To: <43eb21b5-75d9-1142-1307-c2e2d218b362@gmx.de>
On Tue, 2017-12-12 at 21:11 +0100, Helge Deller wrote:
> On 11.12.2017 09:26, Andy Shevchenko wrote:
> > On Fri, 2017-12-08 at 20:06 +0100, Helge Deller wrote:
> Before your patch this check was inside the function
> serial_pci_guess_board()
> and if (ent->driver_data != pbn_default) the pci serial port got
> registered
> and initialized *even* if it's *not* of class SERIAL or MODEM.
Ah, okay, it explains indeed.
Though PCI devices with wrong class should have their own quirks for my
p.o.v.
> > (Of course, I agree this is regression and needs to be fixed ASAP)
>
> I don't know if it's easy to fix without reverting your patch.
As I explained earlier it's about pci_enable_device() called twice for
the same device which basically calls pcibios_enable_irq() twice which
might be a problem on some platforms. (At least I have such use case).
Perhaps it's possible to workaround the issue on those platforms, though
I didn't come up with the better solution that time.
> Thanks for the offer to accept this patch, but maybe we are able
> to come up with another patch which simply hides those unsupported
> devices (serial port and ATI graphics card device on the Diva card).
> I posted a proposed patch here:
> http://www.spinics.net/lists/linux-parisc/msg08187.html
Reading briefly that one I guess it's even better (now I realized you
even do not have connectors of those devices outside).
> But I wonder if we are the only platform which notice this different
> behavior now. I assume others will notice it soon too.
Why so? Most of the 8250 PCI devices are enumerated by class. Others
have no such misclassification.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-12-13 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53815372-58e8-70e2-bab4-1777e848cf5e@web.de>
2017-12-08 19:06 ` Have my PA8800 back online... (serial port missing on v4.14) Helge Deller
2017-12-11 8:26 ` Andy Shevchenko
2017-12-12 20:11 ` Helge Deller
2017-12-13 15:16 ` Andy Shevchenko [this message]
2017-12-18 20:07 ` Helge Deller
2017-12-19 10:53 ` Andy Shevchenko
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=1513178210.7000.34.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dave.anglin@bell.net \
--cc=debian-hppa@lists.debian.org \
--cc=deller@gmx.de \
--cc=frank.scheiner@web.de \
--cc=linux-parisc@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).