[alsa-devel] [PATCH] hda_proc - Add output of Vref, additional pcaps, and proccaps to proc output

Andrew Paprocki andrew at ishiboo.com
Fri Jan 18 04:58:08 CET 2008

I should have known this would happen since the graph tool was just
announced! :) I would gladly help keep the tool up to date, but I
think Claudio is fine with handling it right now:

> Change the format as needed, as long as it is unambiguous and contains
> all the necessary information we'll keep the tool up to date.

If/when the tool is merged into the alsa tree, it would make more
sense for anyone submitting a patch to /proc output to verify and
patch the tool if needed.

If anything needs modification for easier parsing by the tool, it is
very easy to do and I'm willing to help. I would apply this (and any
future /proc enhancements) and if Claudio's tool can be made simpler
by changing the output format, it should be requested and anyone can
help make the patch.


On Jan 17, 2008 12:20 PM, Takashi Iwai <tiwai at suse.de> wrote:
> At Thu, 17 Jan 2008 09:11:00 -0800,
> Tobin Davis wrote:
> >
> > On Thu, 2008-01-17 at 17:58 +0100, Takashi Iwai wrote:
> >
> >     At Thu, 17 Jan 2008 09:46:06 -0400,
> >     Andrew Paprocki wrote:
> >     >
> >     > This adds additional pincaps which were not previously output. Also, Vref
> >     > capabilities are output per-pin along with the current Vref pinctl setting
> >     > if the NID supports Vref. Also added: processing widgets and proccaps, as
> >     > well as processing coefficient and coefficient index from the Realtek Define
> >     > Registers per the ALC883 datasheet.
> >     >
> >     > Signed-off-by: Andrew Paprocki <andrew at ishiboo.com>
> >
> >     Did you check whether this doesn't break Claudio's codecgraph parser?
> >     If it's OK, I'd like to apply it, of course...
> >
> >     Takashi
> >
> > You're kidding, right?  Adding more details about a codec is more useful at this
> > point than making sure a non-essential script (that can be easily modified)
> > isn't broken.
> Well, now we have some parser program, then it's the high time to
> think about the proc output consistent in a certain level.  So far,
> it's just written to be readable for human being.  But, now we'd need
> to make it also easily readable by dumb programs, too.

More information about the Alsa-devel mailing list