From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-sh@vger.kernel.org
Subject: Re: IORESOURCE_PCI_FIXED usage in pcibios_fixup_device_resources()
Date: Fri, 04 Jun 2010 16:04:30 +0000 [thread overview]
Message-ID: <201006041004.32197.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <201006031638.33726.bjorn.helgaas@hp.com>
On Thursday, June 03, 2010 06:42:53 pm Paul Mundt wrote:
> On Thu, Jun 03, 2010 at 04:38:32PM -0600, Bjorn Helgaas wrote:
> > The SH implementation of pcibios_fixup_device_resources() does the
> > equivalent of pcibios_bus_to_resource() for all the resources of a
> > device, except that it skips resources with the IORESOURCE_PCI_FIXED
> > flag set.
> >
> > This looks like a bug to me. IORESOURCE_PCI_FIXED means the resource
> > cannot be moved, not that we should skip pcibios_bus_to_resource().
> >
> > Does anybody know why pcibios_fixup_device_resources() does this check?
> >
> > The only other IORESOURCE_PCI_FIXED reference I see in arch/sh is in
> > gapspci_fixup_resources(), so maybe it has something to do with that?
> >
> gapspci is a very special case, in that it's not really PCI but a bit of
> mangling logic in a custom ASIC that interfaces an 8139 ethernet device
> directly on to an ISA-style bus. If you take a look at
> arch/sh/drivers/pci/fixups-dreamcast.c you can see where the flag is set
> and the rationale behind it.
Yes, using IORESOURCE_PCI_FIXED in gapspci_fixup_resources() sounds
reasonable; it's just that it doesn't make sense to test for it in
pcibios_fixup_device_resources() or pcibios_bus_to_resource().
> Looking at the code again though it seems like pcibios_bus_to_resource()
> will not cause any problems, especially given that the io and mem offsets
> are both cleared to 0 for that controller. I'll kill off the test from
> pcibios_fixup_device_resources(), I assume this was a remnant from the
> old pci-auto code which we moved off of some time ago.
Thanks. I'll watch for your checkin. I'm working on some patches
to move the generic parts of pcibios_fixup_bus() out of the arches
and into drivers/pci, and that depends on this change.
Bjorn
next prev parent reply other threads:[~2010-06-04 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 22:38 IORESOURCE_PCI_FIXED usage in pcibios_fixup_device_resources() Bjorn Helgaas
2010-06-04 0:42 ` Paul Mundt
2010-06-04 16:04 ` Bjorn Helgaas [this message]
2010-06-07 3:05 ` Paul Mundt
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=201006041004.32197.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=linux-sh@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