From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Robert Hancock <hancockr@shaw.ca>,
Andrew Morton <akpm@linux-foundation.org>,
avuton@gmail.com, yakui.zhao@intel.com, shaohua.li@intel.com,
trenn@suse.de,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: a7839e96 (PNP: increase max resources) breaks my ALSA intel8x0 sound card
Date: Thu, 14 Feb 2008 13:07:58 -0700 [thread overview]
Message-ID: <200802141307.59120.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802141141470.6110@woody.linux-foundation.org>
On Thursday 14 February 2008 12:42:52 pm Linus Torvalds wrote:
>
> On Thu, 14 Feb 2008, Bjorn Helgaas wrote:
> >
> > Sorry for the delay. I did work on this, but I don't see how this
> > can work. pcibios_init() marks its reservations as not busy, so the
> > subsequent PNP request doesn't fail, even if it clashes.
>
> It *shouldn't* fail.
>
> Things should fail only when two different drivers have requested the same
> region. NOT when something tells the system that a region _exists_.
The sound driver doesn't fail because two different drivers have
requested the same region; it fails because PNP told us a region
exists, and the sound region crosses the edge of the PNP region.
You wrote earlier that:
> On Tue, 5 Feb 2008, Bjorn Helgaas wrote:
> > > - PnP/ACPI resource allocation *after* it, but before driver
> > > loading (which wll cause new resources to be allocated). This
> > > could be fs_initcall, or whatever (that's what things like
> > > "acpi_event_init" already do).
> >
> > If we put the PNP system driver here, we can easily do a quirk
> > that ignores PNP resources that overlap PCI resources.
>
> No, you don't need any quirks: you just do an "insert_resource()"
> and ignore the error return. If the (bogus) PnP resource clashes
> with the (correct) hardware PCI resource, the insert will simply
> fail. No quirks needed.
I thought you were suggesting here that the PNP system driver would
do an insert_resource(), and it would fail if it clashed with the
PCI resource.
Can you be more explicit about how you think I should fix this?
Bjorn
next prev parent reply other threads:[~2008-02-14 20:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.Kmpf0B4W44W1VefIME7+BnfUouY@ifi.uio.no>
2008-01-27 18:17 ` Robert Hancock
2008-01-31 22:58 ` Andrew Morton
2008-02-01 0:14 ` Robert Hancock
2008-02-01 0:50 ` Linus Torvalds
2008-02-04 17:39 ` Bjorn Helgaas
2008-02-04 18:18 ` Linus Torvalds
2008-02-04 20:41 ` Bjorn Helgaas
2008-02-04 21:16 ` Linus Torvalds
2008-02-05 7:03 ` Bjorn Helgaas
2008-02-05 16:46 ` Avuton Olrich
2008-02-05 18:15 ` Linus Torvalds
2008-02-05 20:12 ` Bjorn Helgaas
2008-02-13 22:33 ` Avuton Olrich
2008-02-14 18:51 ` Bjorn Helgaas
2008-02-14 19:42 ` Linus Torvalds
2008-02-14 20:07 ` Bjorn Helgaas [this message]
2008-02-14 20:26 ` Linus Torvalds
2008-02-14 21:01 ` Bjorn Helgaas
2008-02-14 21:37 ` Linus Torvalds
2008-02-14 22:28 ` Bjorn Helgaas
2008-02-14 22:57 ` Linus Torvalds
2008-02-14 23:14 ` Linus Torvalds
2008-02-15 0:13 ` Bjorn Helgaas
2008-02-15 0:40 ` Linus Torvalds
2008-02-27 17:43 ` Bjorn Helgaas
2008-01-27 14:40 Avuton Olrich
2008-01-27 21:50 ` Linus Torvalds
2008-01-28 1:15 ` Shaohua Li
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=200802141307.59120.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=avuton@gmail.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=trenn@suse.de \
--cc=yakui.zhao@intel.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
all inboxes | Powered by JetHome®