From: Takashi Iwai <tiwai@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Arjan van de Ven <arjanv@redhat.com>,
greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: Resume enhancement: restore pci config space
Date: Tue, 01 Jun 2004 18:18:50 +0200 [thread overview]
Message-ID: <s5h3c5fqmj9.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040601160234.GB1899@atrey.karlin.mff.cuni.cz>
At Tue, 1 Jun 2004 18:02:34 +0200,
Pavel Machek wrote:
>
> [It seems to me like ALSA can't easily put NULL into suspend/resume
> fields, because they have additional layer of abstraction between them
> and kernel.]
It does indeed. ALSA provides the "common" PCI suspend/resume
callbacks, which call the internal suspend/resume callbacks.
It's for handling the power status from the external program, too.
These are defined as SND_PCI_PM_CALLBACKS. If CONFIG_PM is not set,
it's expanded to empty. So, typically the code looks like the
following:
static struct pci_driver driver = {
.name = "Intel ICH",
.id_table = snd_intel8x0_ids,
.probe = snd_intel8x0_probe,
.remove = __devexit_p(snd_intel8x0_remove),
SND_PCI_PM_CALLBACKS
};
Takashi
next prev parent reply other threads:[~2004-06-01 16:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 20:35 Resume enhancement: restore pci config space Arjan van de Ven
2004-05-26 22:39 ` Greg KH
2004-05-27 9:44 ` Takashi Iwai
2004-05-30 18:40 ` Pavel Machek
2004-05-31 13:38 ` Arjan van de Ven
2004-06-01 13:54 ` Takashi Iwai
2004-06-01 15:06 ` Arjan van de Ven
2004-06-01 15:26 ` Takashi Iwai
2004-06-01 15:38 ` Arjan van de Ven
2004-06-01 15:58 ` Takashi Iwai
2004-06-01 16:02 ` Pavel Machek
2004-06-01 16:18 ` Takashi Iwai [this message]
2004-05-31 16:38 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2004-05-26 21:44 Nakajima, Jun
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=s5h3c5fqmj9.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=arjanv@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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