All of lore.kernel.org
 help / color / mirror / Atom feed
From: matthew@wil.cx (Matthew Wilcox)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH,RFC] PCI: deal with device incorrectly reporting I/O decoding being enabled
Date: Sat, 7 Nov 2009 08:03:05 -0700	[thread overview]
Message-ID: <20091107150305.GQ10555@parisc-linux.org> (raw)
In-Reply-To: <20091107135615.GE18639@mail.wantstofly.org>

On Sat, Nov 07, 2009 at 02:56:15PM +0100, Lennert Buytenhek wrote:
> At least the Lava Quattro quad-port 16550A card can incorrectly report
> I/O decoding being enabled while it is in fact not, which means that
> the check in pcibios_enable_device() to see whether the new command
> word that we're intending to write into the device is different from
> the old current can trigger inadvertently, resulting in the write to
> enable I/O decoding never being done, and I/O decoding never being
> enabled.
> 
> Work around this by doing the write unconditionally (while still
> only doing the printk if the new word is different from the old one,
> to avoid dmesg spam).
> 
> Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
> --
> This is probably at least slightly controversial.  Any thoughts?

I'm OK with this ... it might provoke bugs in some _other_ piece of hardware,
but that seems pretty unlikely.

Reviewed-by: Matthew Wilcox <willy@linux.intel.com>

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2009-11-07 15:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-07 13:56 [PATCH, RFC] PCI: deal with device incorrectly reporting I/O decoding being enabled Lennert Buytenhek
2009-11-07 15:03 ` Matthew Wilcox [this message]
2009-11-08  9:04   ` [PATCH,RFC] " Russell King - ARM Linux
2009-11-08 15:23     ` Matthew Wilcox
2009-11-08 15:41       ` Russell King - ARM Linux
2009-11-08 16:15         ` Matthew Wilcox
2009-11-10  0:35         ` Dan Williams

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=20091107150305.GQ10555@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=linux-arm-kernel@lists.infradead.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.