All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jan Pokorny <lists@t.poki.me>
Cc: alsa-devel@alsa-project.org, Kailang Yang <kailang@realtek.com>,
	Mark Pearson <mpearson@lenovo.com>
Subject: Re: Lenovo P520/Realtek ALC662 - front jack & mic in [FIXED]
Date: Fri, 05 Jun 2020 10:35:18 +0200	[thread overview]
Message-ID: <s5hd06d9agp.wl-tiwai@suse.de> (raw)
In-Reply-To: <f9cdb458-9e2e-c23b-675b-8b3ea55a8b51@poki.me>

On Tue, 02 Jun 2020 13:59:31 +0200,
Jan Pokorny wrote:
> 
> I wonder why there are no pointers anywhere, at least in alsa-info.sh
> output that would perhaps make the case clear for the experts amongst
> you.  Or somewhere else, where it could be raised as a suggestion:
> 
>   It appears as if you have a card/coded that relies on UCM for it
>   to be used to the full extent, and UCM does not appear to be
>   installed.  Try installing that software, commonly packaged as
>   alsa-ucm.  Having it up-to-date may also help.

Unfortunately it's not so trivial for now.  The UCM is optional, and
there is no specific indicator that mandates UCM profile from the
driver side, so far.

We might need to introduce some more hints for UCM profile, e.g. via
ALSA component string.


thanks,

Takashi

  reply	other threads:[~2020-06-05  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31 14:05 Cannot get Lenovo P520/Realtek ALC662 (rev 3) to produce sound Jan Pokorny
2020-05-31 16:07 ` Lenovo P520/Realtek ALC662 - front jack & mic in (Was: Cannot get Lenovo P520/Realtek ALC662 to produce sound) Jan Pokorny
2020-06-01 21:36   ` Lenovo P520/Realtek ALC662 - front jack & mic in Jan Pokorny
2020-06-02 11:59     ` Lenovo P520/Realtek ALC662 - front jack & mic in [FIXED] Jan Pokorny
2020-06-05  8:35       ` Takashi Iwai [this message]
2020-06-05  9:44       ` Jaroslav Kysela
2020-06-14  9:45         ` Jan Pokorny

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=s5hd06d9agp.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kailang@realtek.com \
    --cc=lists@t.poki.me \
    --cc=mpearson@lenovo.com \
    /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.