From: Jiri Slaby <jslaby@suse.cz>
To: Sergei Shtylyov <sshtylyov@mvista.com>
Cc: jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
jirislaby@gmail.com, Bjorn Helgaas <bjorn.helgaas@hp.com>,
"David S. Miller" <davem@davemloft.net>,
Thomas Renninger <trenn@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH option B 2/2] PCI: do not create quirk I/O regions below PCIBIOS_MIN_IO for ICH
Date: Fri, 11 Feb 2011 15:16:35 +0100 [thread overview]
Message-ID: <4D5544C3.8040306@suse.cz> (raw)
In-Reply-To: <4D552704.1000509@ru.mvista.com>
On 02/11/2011 01:09 PM, Sergei Shtylyov wrote:
>> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
>> index 8db2426..b3ab2f7 100644
>> --- a/drivers/pci/quirks.c
>> +++ b/drivers/pci/quirks.c
>> @@ -554,18 +554,30 @@ static void __devinit quirk_ich4_lpc_acpi(struct
>> pci_dev *dev)
>> u32 region;
>> u8 enable;
>>
>> + /*
>> + * The check for PCIBIOS_MIN_IO is to ensure we won't create a
>> conflict
>> + * with low legacy (and fixed) ports. We don't know the decoding
>> + * priority and can't tell whether the legacy device or the one
>> created
>> + * here is really at that address. This happens on boards with
>> broken
>> + * BIOSes.
>> + */
>> +
>> pci_read_config_byte(dev, ICH_ACPI_CNTL,&enable);
>> if (enable& ICH4_ACPI_EN) {
>> pci_read_config_dword(dev, ICH_PMBASE,®ion);
>> - quirk_io_region(dev, region, 128, PCI_BRIDGE_RESOURCES,
>> - "ICH4 ACPI/GPIO/TCO");
>> + region &= PCI_BASE_ADDRESS_IO_MASK;
>
> Why don't you do the masking right in the patch #1? And is it really
> necessary if the region size is known to be 128 bytes?
The region here contains also the low flag bits. Yes, it can be a part
of 1/1. But I don't think it matters.
regards,
--
js
suse labs
next prev parent reply other threads:[~2011-02-11 14:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 15:17 [PATCH 1/1] PCI: tune up ICH4 quirk for broken BIOSes Jiri Slaby
2011-01-06 19:24 ` Bjorn Helgaas
2011-01-07 20:44 ` Jiri Slaby
2011-01-07 22:37 ` Jesse Barnes
2011-01-07 23:13 ` Jiri Slaby
2011-01-07 23:03 ` Bjorn Helgaas
2011-01-07 23:29 ` Jiri Slaby
2011-01-08 0:16 ` Bjorn Helgaas
2011-01-08 9:58 ` Jiri Slaby
2011-01-10 18:40 ` Bjorn Helgaas
2011-01-13 10:07 ` Jiri Slaby
2011-01-13 23:19 ` Bjorn Helgaas
2011-01-14 0:15 ` Linus Torvalds
2011-01-14 10:31 ` Jiri Slaby
2011-01-14 10:32 ` [PATCH 1/2] PCI: add more checking to ICH region quirks Jiri Slaby
2011-01-14 10:32 ` [PATCH option B 2/2] PCI: do not create quirk I/O regions below PCIBIOS_MIN_IO for ICH Jiri Slaby
2011-02-11 12:09 ` Sergei Shtylyov
2011-02-11 14:16 ` Jiri Slaby [this message]
2011-01-14 10:32 ` [PATCH option A 2/2] PCI: do not create quirk I/O regions below PCIBIOS_MIN_IO Jiri Slaby
2011-01-14 16:10 ` [PATCH 1/1] PCI: tune up ICH4 quirk for broken BIOSes Bjorn Helgaas
2011-01-15 15:39 ` Robert Hancock
2011-02-08 9:55 ` Jiri Slaby
2011-02-08 21:20 ` Jesse Barnes
2011-02-11 10:32 ` Jiri Slaby
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=4D5544C3.8040306@suse.cz \
--to=jslaby@suse.cz \
--cc=bjorn.helgaas@hp.com \
--cc=davem@davemloft.net \
--cc=jbarnes@virtuousgeek.org \
--cc=jirislaby@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sshtylyov@mvista.com \
--cc=torvalds@linux-foundation.org \
--cc=trenn@suse.de \
/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).