From: Ralf Baechle <ralf@linux-mips.org>
To: "Steven J. Hill" <sjhill@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [v2,4/5] MIPS: Malta PCI changes for PCI 2.1 compatibility and conflicts.
Date: Thu, 24 May 2012 12:25:03 +0100 [thread overview]
Message-ID: <20120524112503.GA2337@linux-mips.org> (raw)
In-Reply-To: <1333742869-17373-1-git-send-email-sjhill@mips.com>
On Fri, Apr 06, 2012 at 03:07:49PM -0500, Steven J. Hill wrote:
> diff --git a/arch/mips/mti-malta/malta-pci.c b/arch/mips/mti-malta/malta-pci.c
> index bf80921..afeb619 100644
> --- a/arch/mips/mti-malta/malta-pci.c
> +++ b/arch/mips/mti-malta/malta-pci.c
> @@ -241,8 +241,9 @@ void __init mips_pcibios_init(void)
> return;
> }
>
> - if (controller->io_resource->start < 0x00001000UL) /* FIXME */
> - controller->io_resource->start = 0x00001000UL;
> + /* Change start address to avoid conflicts with ACPI and SMB devices */
> + if (controller->io_resource->start < 0x00002000UL) /* FIXME */
> + controller->io_resource->start = 0x00002000UL;
I think raising this value to 0x2000 solves the FIXME which is there since
Maciej's 66d9ad704b25287bfee7e86a5af50b92642b9c72 commit in 2005. Maciej,
do you recall you added the FIXME?
> iomem_resource.end &= 0xfffffffffULL; /* 64 GB */
> ioport_resource.end = controller->io_resource->end;
> diff --git a/arch/mips/mti-malta/malta-setup.c b/arch/mips/mti-malta/malta-setup.c
> index b7f37d4..b45b343 100644
> --- a/arch/mips/mti-malta/malta-setup.c
> +++ b/arch/mips/mti-malta/malta-setup.c
> @@ -222,3 +222,17 @@ void __init plat_mem_setup(void)
> board_be_init = malta_be_init;
> board_be_handler = malta_be_handler;
> }
> +
> +/* Enable PCI 2.1 compatibility in PIIX4. */
> +static void __init quirk_dlcsetup(struct pci_dev *dev)
> +{
> + u8 dlc;
> +
> + /* Enable passive releases and delayed transactions. */
> + (void) pci_read_config_byte(dev, 0x82, &dlc);
> + dlc |= 7;
> + (void) pci_write_config_byte(dev, 0x82, dlc);
> +}
> +
> +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82371AB_0,
> + quirk_dlcsetup);
See 9ead526ca4e6f3d9c7e6b79bb3fda113bd3b0eeb. It would appear that your
patch turned stale about two and a half years before it was posted ;-)
Ralf
next prev parent reply other threads:[~2012-05-24 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 20:07 [v2,4/5] MIPS: Malta PCI changes for PCI 2.1 compatibility and conflicts Steven J. Hill
2012-05-24 11:25 ` Ralf Baechle [this message]
2012-05-24 12:56 ` Maciej W. Rozycki
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=20120524112503.GA2337@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=sjhill@mips.com \
/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