Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: pci_disable_device warning
Date: Thu, 18 Nov 2004 14:08:25 +0100	[thread overview]
Message-ID: <s5hr7mrqp86.wl@alsa2.suse.de> (raw)
In-Reply-To: <1100716849.6930.31.camel@krustophenia.net>

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

At Wed, 17 Nov 2004 13:40:48 -0500,
Lee Revell wrote:
> 
> I get this warning when removing ALSA modules.  I believe the warning is
> going away, so maybe we should address the issue now.  Is this something
> that could be done by the ALSA middle layer? 
 
Possible, but I think better in each driver code.

> Nov 16 23:32:09 krustophenia kernel: EMU10K1_Audigy 0000:00:14.0: Device
> was removed without properly calling pci_disable_device(). This may need
> fixing.
> 
> I tried adding a call to pci_disable_device and the warning persisted,
> maybe I did not add it in the right place.

Does the patch below fix?


Takashi

[-- Attachment #2: Type: text/plain, Size: 554 bytes --]

Index: alsa-kernel/pci/emu10k1/emu10k1_main.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c,v
retrieving revision 1.38
diff -u -r1.38 emu10k1_main.c
--- alsa-kernel/pci/emu10k1/emu10k1_main.c	30 Jul 2004 12:44:58 -0000	1.38
+++ alsa-kernel/pci/emu10k1/emu10k1_main.c	18 Nov 2004 13:05:28 -0000
@@ -561,6 +561,7 @@
 		free_irq(emu->irq, (void *)emu);
 	if (emu->port)
 		pci_release_regions(emu->pci);
+	pci_disable_device(emu->pci);
 	kfree(emu);
 	return 0;
 }

      reply	other threads:[~2004-11-18 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17 18:40 pci_disable_device warning Lee Revell
2004-11-18 13:08 ` Takashi Iwai [this message]

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=s5hr7mrqp86.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rlrevell@joe-job.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