From: Takashi Iwai <tiwai@suse.de>
To: Stas Sergeev <stsp@aknet.ru>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: patch driver-core-warn-about-duplicate-driver-names-on-the-same-bus.patch added to gregkh-2.6 tree
Date: Fri, 02 May 2008 18:35:43 +0200 [thread overview]
Message-ID: <s5hd4o4oe8w.wl%tiwai@suse.de> (raw)
In-Reply-To: <481B3FBF.9070004@aknet.ru>
At Fri, 02 May 2008 20:22:23 +0400,
Stas Sergeev wrote:
>
> Hello.
>
> Takashi Iwai wrote:
> >> Another point is PM callbacks. Somehow
> >> snd-pcsp will have to register them with
> >> pcspkr.
> > Hmm, isn't platform PM hook enough?
> > pcspkr.c just sends an event at suspend or shutdown to the event
> > handler. So, if the event was shut up at the beginning in the
> > handler, nothing would be needed.
> I don't think I understand what you mean...
> Currently, pcspkr.c just stops the timer
> counter to shut up the beep.
> snd-pcsp needs more. snd_pcm_suspend_all()
> for instance. Since it doesn't register
> itself as a platform driver any more, he
> have to register itself into pcspkr.c.
> Or?
If snd-pcsp can hook up input pcspkr dynamically, you can (should)
register snd-pcsp as a different name, as an individual platform
driver. Then the whole PM stuff would still belong to snd-pcsp.
Takashi
prev parent reply other threads:[~2008-05-02 16:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <12094266793898@kroah.org>
2008-04-29 4:48 ` Stas Sergeev
2008-04-29 4:58 ` Greg KH
2008-04-29 10:41 ` Takashi Iwai
2008-04-29 15:14 ` Greg KH
2008-04-29 16:41 ` Takashi Iwai
2008-04-29 16:56 ` Greg KH
2008-04-29 19:28 ` Stas Sergeev
2008-04-30 6:34 ` Takashi Iwai
2008-04-30 17:45 ` Stas Sergeev
2008-05-02 14:07 ` Takashi Iwai
2008-05-02 15:38 ` Stas Sergeev
2008-05-02 16:00 ` Takashi Iwai
2008-05-02 16:22 ` Stas Sergeev
2008-05-02 16:35 ` 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=s5hd4o4oe8w.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@aknet.ru \
/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®