public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Adam Belay <abelay@MIT.EDU>
Cc: Takashi Iwai <tiwai@suse.de>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	alsa-devel@alsa-project.org
Subject: Re: snd-cs4236 (possibly all isa-pnp cards or all alsa isa-pnp	cards) broken in 2.6.16-rc4
Date: Tue, 21 Feb 2006 16:37:36 +0100	[thread overview]
Message-ID: <43FB33C0.2090004@keyaccess.nl> (raw)
In-Reply-To: <1140499646.21116.30.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 939 bytes --]

Adam Belay wrote:

[ pnp_card_driver.remove() not called ]

> Hopefully this email account will work better.  In any case, thanks
> for bringing this bug to my attention.  I may have stumbled across it
> a couple days ago, and would appreciate if you would try this patch: 
> (there may be some fuzz)

Reject even. I've attached this patch regenerated against 2.6.16-rc4.

> -       if (drv->link.driver.probe) {
> -               if (drv->link.driver.probe(&dev->dev)) {

> +       if (pnp_bus_type.probe(&dev->dev)) {

Yes, this works, thanks. If it's also the correct fix, I guess this 
should go into 2.6.16?

I by the way also tested with a driver that uses pnp_driver instead of 
pnp_card_driver, and that also works.

> It's possible that the attach mechanism isn't working correctly
> because of recent driver model changes.  If this is the case, it
> would also explain the detach-not-called issues.

The bustype stuff...

Rene.


[-- Attachment #2: pnp_bus_type_adam.diff --]
[-- Type: text/plain, Size: 796 bytes --]

Index: local/drivers/pnp/card.c
===================================================================
--- local.orig/drivers/pnp/card.c	2006-02-11 00:34:01.000000000 +0100
+++ local/drivers/pnp/card.c	2006-02-21 14:06:21.000000000 +0100
@@ -303,13 +303,11 @@ found:
 	down_write(&dev->dev.bus->subsys.rwsem);
 	dev->card_link = clink;
 	dev->dev.driver = &drv->link.driver;
-	if (drv->link.driver.probe) {
-		if (drv->link.driver.probe(&dev->dev)) {
-			dev->dev.driver = NULL;
-			dev->card_link = NULL;
-			up_write(&dev->dev.bus->subsys.rwsem);
-			return NULL;
-		}
+	if (pnp_bus_type.probe(&dev->dev)) {
+		dev->dev.driver = NULL;
+		dev->card_link = NULL;
+		up_write(&dev->dev.bus->subsys.rwsem);
+		return NULL;
 	}
 	device_bind_driver(&dev->dev);
 	up_write(&dev->dev.bus->subsys.rwsem);

  reply	other threads:[~2006-02-21 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 17:18 snd-cs4236 (possibly all isa-pnp cards or all alsa isa-pnp cards) broken in 2.6.16-rc4 Rene Herman
2006-02-21  5:27 ` Adam Belay
2006-02-21 15:37   ` Rene Herman [this message]
2006-02-21 14:18 ` Takashi Iwai
2006-02-21 15:51   ` Rene Herman
2006-02-21 17:43     ` Takashi Iwai
2006-02-21 19:35       ` Rene Herman
  -- strict thread matches above, loose matches on Subject: below --
2006-02-20 16:54 Rene Herman

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=43FB33C0.2090004@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=abelay@MIT.EDU \
    --cc=akpm@osdl.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@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