From: Greg KH <greg@kroah.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [PATCH] sysfs sound class patches - [0/2]
Date: Fri, 09 Jan 2004 08:00:13 +0000 [thread overview]
Message-ID: <20040109080012.GB15962@kroah.com> (raw)
In-Reply-To: <s5hvfnmxs3r.wl@alsa2.suse.de>
On Thu, Jan 08, 2004 at 06:33:44PM +0100, Takashi Iwai wrote:
> At Wed, 7 Jan 2004 15:21:37 -0800,
> Greg KH wrote:
> >
> > Here are 2 sysfs sound class patches against 2.6.1-rc2 (but should apply
> > to 2.6.0) that add sysfs support for OSS and ALSA drivers. This enables
> > udev to see sound devices and create nodes for them.
> >
> > I've divided it up into 2 patches:
> > - sound support for OSS drivers
> > - sound support for ALSA drivers
> >
> > The ALSA driver patch requires the OSS driver (due to where struct
> > sound_class is declared),
>
> oh, sound_core.c is not the OSS driver ;)
Heh, but the changes I made to it are in the OSS specific parts :)
> > and it also modifies the i810 ALSA sound
> > driver to provide a symlink in sysfs to the pci device being controlled
> > by the device node.
>
> it looks nice and easy. i'll do that for all pci drivers, too, once
> when these patches are merged.
Thanks.
> > I can provide patches to the other ALSA drivers to also add this
> > information, as it's quite useful if you have more than one sound device
> > in your system at once.
>
> not only pci but also isapnp devices can provide dev pointer.
Exactly. So does USB.
> in that case, should the driver gives symlinks of each isapnp devices,
> too?
Yes. If the dev pointer is valid, the driver core will create the
symlinks.
> a module usually holds one isapnp card struct and several isapnp
> devices below it. but, hmm, it will need far more codes...
Just set the dev pointer to the device that is associated with the sound
device. That's the best you can do.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-01-09 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 23:21 [PATCH] sysfs sound class patches - [0/2] Greg KH
2004-01-07 23:23 ` [PATCH] sysfs sound class patch for OSS drivers - [1/2] Greg KH
2004-01-07 23:24 ` [PATCH] sysfs sound class patch for ALSA drivers - [2/2] Greg KH
2004-01-08 20:08 ` [PATCH] sysfs sound class patch for OSS drivers - [1/2] Andreas Jellinghaus
2004-01-08 12:41 ` [PATCH] sysfs sound class patches - [0/2] Kristof vansant
2004-01-08 13:40 ` Kristof vansant
2004-01-08 17:33 ` Takashi Iwai
2004-01-09 8:00 ` Greg KH [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=20040109080012.GB15962@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).