public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: david@lang.hm
Cc: trenn@suse.de, linux-acpi <linux-acpi@vger.kernel.org>,
	Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [Fwd: Re: long-term regression - Parallel Port broken?]
Date: Tue, 24 Jul 2007 15:40:43 -0600	[thread overview]
Message-ID: <200707241540.43868.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707211905450.6747@asgard.lang.hm>

On Saturday 21 July 2007 08:09:11 pm david@lang.hm wrote:
> On Fri, 6 Jul 2007, Bjorn Helgaas wrote:
> > Ultimately, you should have CONFIG_ACPI=y and CONFIG_PNPACPI=y, and you
> > should not have to boot with "noisapnp" or "pnpacpi=off".  My guess is
> > that you only need "pnpacpi=off" to work around the current problem.
> 
> these two options are enabled and pnpacpi=off does solve the problem.
> ...
> there's now a dmesg.pnpacpi_off which works, and you are correct that the 
> dmesg that's there is the non working one.

Thanks.  Here's what I glean from that.  With no arguments, it doesn't work:

    parport_pc 00:0a: reported by Plug and Play ACPI
    parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
    parport0: Printer, Brother HL-5040 series
    lp0: using parport0 (interrupt-driven).

With pnpacpi=off, it works:

    parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
    parport0: irq 7 detected
    parport0: Printer, Brother HL-5040 series
    lp0: using parport0 (polling).

With pnpacpi=off, or a kernel without PNPACPI, we just probe at 0x378
and use the port in polling mode, and it works.

PNPACPI claims the device supports interrupts, so we try to use it in
interrupt mode, and it doesn't work.  It's possible that ACPI is lying
to us, and the interrupt really doesn't work.  Or maybe the interrupt
*does* work, but the BIOS left it half-configured.

Could you try the attached patch and collect the dmesg log and contents
of /proc/interrupts?

Thanks,
  Bjorn

Index: w/drivers/pnp/pnpacpi/core.c
===================================================================
--- w.orig/drivers/pnp/pnpacpi/core.c	2007-07-24 15:05:25.000000000 -0600
+++ w/drivers/pnp/pnpacpi/core.c	2007-07-24 15:29:50.000000000 -0600
@@ -216,6 +216,13 @@
 	pnp_add_device(dev);
 	num ++;
 
+	if (dev->active) {
+		printk("%s: configuring %s (%s)\n", __FUNCTION__, dev->dev.bus_id, dev_id->id);
+		pnp_disable_dev(dev);
+		pnp_init_resource_table(&dev->res);
+		pnp_activate_dev(dev);
+	}
+
 	return AE_OK;
 err1:
 	kfree(dev_id);

  reply	other threads:[~2007-07-24 21:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 11:28 [Fwd: Re: long-term regression - Parallel Port broken?] Thomas Renninger
2007-07-06 16:38 ` Bjorn Helgaas
2007-07-06 21:20   ` Bjorn Helgaas
2007-07-17 22:08     ` Bjorn Helgaas
2007-07-22  2:09   ` david
2007-07-24 21:40     ` Bjorn Helgaas [this message]
2007-07-30  1:22       ` david
2007-07-30  3:41         ` Bjorn Helgaas
2007-07-30  3:46           ` david
2007-07-30  3:59           ` david
2007-07-30 14:08             ` Bjorn Helgaas
2008-05-27 23:11               ` Bjorn Helgaas
2008-05-28  9:19                 ` david
2008-06-13 17:45                   ` Bjorn Helgaas
2007-07-22  2:04 ` david
2007-07-22  2:44   ` Thomas Renninger
2007-07-22 22:05     ` david

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=200707241540.43868.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=david@lang.hm \
    --cc=linux-acpi@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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