linux-kernel - Re: sysfs & ALSA card

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061007062458.GF23366@kroah.com>
Date:	Fri, 6 Oct 2006 23:24:58 -0700
From:	Greg KH <greg@...ah.com>
To:	Jaroslav Kysela <perex@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>, Takashi Iwai <tiwai@...e.de>
Subject: Re: sysfs & ALSA card

On Fri, Oct 06, 2006 at 04:00:27PM +0200, Jaroslav Kysela wrote:
> Hi,
> 
> 	I would like to discuss where is the right root for soundcards in 
> the sysfs tree. I would like to put card specific variables like id there 
> (see /proc/asound/card0/id).

That would be nice to have in sysfs, I agree.

> Also, I plan to create link from 
> /sys/class/sound tree to the appropriate card to show relationship. 
> Something like:
> 
> /sys/<somewhere>/soundcard/0
> 
> /sys/class/sound/controlC0/soundcard -> ../../../<somewhere>/soundcard/0
> 
> 	Any comments and suggestions?

Yeah, this isn't that hard right now.  Just create a new struct device
for every card, point the parent of this new device to the device that
represents the card, and then point the other different sound specific
devices to the new card.

Hm, let me go hack at it and see what I come up with, code is so much
better for an example...

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/