From: Takashi Iwai <tiwai@suse.de>
To: Daniel Suchy <danny@danysek.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ALSA: HDA: conexant support for Lenovo T520/W520
Date: Wed, 19 Oct 2011 08:00:51 +0200 [thread overview]
Message-ID: <s5hmxcxy0z0.wl%tiwai@suse.de> (raw)
In-Reply-To: <4E9DF9F1.9040606@danysek.cz>
At Wed, 19 Oct 2011 00:13:05 +0200,
Daniel Suchy wrote:
>
> Hello,
>
> On 10/18/2011 11:04 AM, Takashi Iwai wrote:
> >> There's another issue I observed related to audio outputs, but I'm not
> >> sure about the reason. With docking station, audio isn't working over
> >> audio output on the Minidock 3. Internal speakers are cutted off
> >> properly, but there's no sound output on the connector. Audio output on
> >> T520 directly works as expected, only output on minidock has this
> >> problem. If you have any hints, let me know. This happens even with
> >> autodetection enabled (this was my initial motivation for looking into
> >> the driver source, and also CXT5066_THINKPAD quirk, which I tested
> >> previously has this problem).
> >
> > Might be an EAPD issue? There is another pending patch. Attached
> > below.
> >
>
> I tried all patches you provided, but the problem with output persists.
> Tested on 3.1-rc10. I'll look on the recording issue tomorrow.
OK, then could you give alsa-info.sh outputs (run with --no-upload)
at docked (non-working) and undocked (working) states with model=auto?
If the dock-output works with your patch, give alsa-info.sh output
at that state, too, for comparison.
The alsa-info.sh output is the best material to track down a HD-audio
issue, since I can run an emulator here with it.
thanks,
Takashi
next prev parent reply other threads:[~2011-10-19 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 7:42 Daniel Suchy
2011-10-18 8:17 ` Takashi Iwai
2011-10-18 9:00 ` Daniel Suchy
2011-10-18 9:04 ` Takashi Iwai
2011-10-18 22:13 ` Daniel Suchy
2011-10-19 6:00 ` Takashi Iwai [this message]
2011-10-18 9:08 ` 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=s5hmxcxy0z0.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=danny@danysek.cz \
--cc=linux-kernel@vger.kernel.org \
/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®