mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Avuton Olrich <avuton@gmail.com>,
	Rene Herman <rene.herman@gmail.com>,
	Len Brown <len.brown@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 53052feb6 (PNP: remove pnp_mem_flags() as an lvalue) breaks my ALSA intel8x0 sound card regression
Date: Mon, 2 Jun 2008 16:05:13 -0600	[thread overview]
Message-ID: <200806021605.14519.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <484444A4.80206@keyaccess.nl>

On Monday 02 June 2008 01:06:12 pm Rene Herman wrote:
> On 02-06-08 05:25, Avuton Olrich wrote:
> 
> > On Sun, Jun 1, 2008 at 9:20 AM, Rene Herman <rene.herman@keyaccess.nl> wrote:
> >> On 01-06-08 16:42, Avuton Olrich wrote:
> >>
> >>> My intel8x0 card stops working due to a regression; bisection and
> >>> information below.

Thank you very much for doing all the work to bisect this and write
up such a complete report.

Can you try the patch below, please?

PNP: mark resources that conflict with PCI devices "disabled"

Both the PNP/PCI conflict detection quirk and the PNP system
driver must use the same mechanism to mark resources as disabled.

I think it's best to keep the resource and to keep the type bit
(IORESOURCE_MEM, etc), so that we match the list from firmware
as closely as possible.

Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>

Index: work11/drivers/pnp/quirks.c
===================================================================
--- work11.orig/drivers/pnp/quirks.c	2008-06-02 14:59:03.000000000 -0600
+++ work11/drivers/pnp/quirks.c	2008-06-02 15:42:35.000000000 -0600
@@ -286,7 +286,7 @@ static void quirk_system_pci_resources(s
 					pci_name(pdev), i,
 					(unsigned long long) pci_start,
 					(unsigned long long) pci_end);
-				res->flags = 0;
+				res->flags |= IORESOURCE_DISABLED;
 			}
 		}
 	}
Index: work11/drivers/pnp/system.c
===================================================================
--- work11.orig/drivers/pnp/system.c	2008-06-02 14:58:56.000000000 -0600
+++ work11/drivers/pnp/system.c	2008-06-02 15:44:36.000000000 -0600
@@ -81,7 +81,7 @@ static void reserve_resources_of_dev(str
 	}
 
 	for (i = 0; (res = pnp_get_resource(dev, IORESOURCE_MEM, i)); i++) {
-		if (res->flags & IORESOURCE_UNSET)
+		if (res->flags & IORESOURCE_DISABLED)
 			continue;
 
 		reserve_range(dev, res->start, res->end, 0);

  reply	other threads:[~2008-06-02 22:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01 14:42 Avuton Olrich
2008-06-01 16:20 ` Rene Herman
2008-06-02  3:25   ` Avuton Olrich
2008-06-02 19:06     ` Rene Herman
2008-06-02 22:05       ` Bjorn Helgaas [this message]
2008-06-02 22:23         ` Avuton Olrich
2008-06-02 22:42           ` Bjorn Helgaas
2008-06-02 23:49             ` Andrew Morton
2008-06-02 23:58               ` Rene Herman
2008-06-03  0:03                 ` Andrew Morton
2008-06-03  0:31                   ` Rene Herman
2008-06-03  0:15                 ` Rene Herman
2008-06-03 18:40               ` Bjorn Helgaas
2008-06-04 23:38             ` Tony Luck
2008-06-05 16:18               ` Bjorn Helgaas

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=200806021605.14519.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=avuton@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@gmail.com \
    --cc=rene.herman@keyaccess.nl \
    --cc=rjw@sisk.pl \
    /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®