From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: HDA: Fix jack creation for codecs with front and rear Line In
Date: Wed, 01 Feb 2012 09:19:25 +0100 [thread overview]
Message-ID: <4F28F58D.4060707@canonical.com> (raw)
In-Reply-To: <s5h62frop7t.wl%tiwai@suse.de>
On 01/31/2012 04:40 PM, Takashi Iwai wrote:
> At Tue, 31 Jan 2012 16:28:14 +0100,
> David Henningsson wrote:
>>
>> On 01/31/2012 03:17 PM, Takashi Iwai wrote:
>>> At Tue, 31 Jan 2012 09:04:15 +0100,
>>> David Henningsson wrote:
>>>>
>>>> If a codec has both a front and a rear Line In, two controls both
>>>> named "Line Jack" will be created, which causes parsing to fail.
>>>> While a long term solution might be to name the jacks differently,
>>>> this extra check is consistent with what is already being done in many
>>>> auto-parsers, and will also protect against other cases when two
>>>> inputs have the same label.
>>>>
>>>> BugLink: https://bugs.launchpad.net/bugs/923409
>>>> Signed-off-by: David Henningsson<david.henningsson@canonical.com>
>>>
>>> Thanks, applied now.
>>>
>>> BTW, any chance to change apport to gather alsa-info.sh output?
This has now been provided:
http://www.alsa-project.org/db/?f=f4a8312f34573a24f60011109e18f0c7371129e0
>>> It'd be a great help, so that we can check it via hda-emu.
>>
>> I have asked for this particular bug reporter to supply alsa-info as
>> well, but may I ask you...do you have some kind of regression test
>> script, and if so, are they public? Or could it a part of hda-emu?
>
> The checks I often do are scripts like below. Run for all files
> and check the difference before and after the patch.
>
>> It would be nice if you could run "make tests" or something from the
>> hda-emu source directory, and it would parse all codecs and report error
>> if parsing fails (or pm fails, etc).
>
> Yeah, any patch is welcome ;)
Thanks for the small test scripts! It's good to be on the same page.
Hopefully I get around some day to write a "make tests", but not right
now unfortunately.
I quickly ran test2 and noticed that
- We have quite a lot of work to do before all errors are fixed!
- The error I got from hda-emu for the codec above, 'Control element
Line Jack:0 already exists!' was already present for one of the codecs.
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2012-02-01 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 8:04 [PATCH] ALSA: HDA: Fix jack creation for codecs with front and rear Line In David Henningsson
2012-01-31 8:29 ` Raymond Yau
2012-01-31 10:18 ` David Henningsson
2012-01-31 11:52 ` Raymond Yau
2012-01-31 14:17 ` Takashi Iwai
2012-01-31 15:28 ` David Henningsson
2012-01-31 15:40 ` Takashi Iwai
2012-02-01 8:19 ` David Henningsson [this message]
2012-02-01 8:39 ` Takashi Iwai
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=4F28F58D.4060707@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.