Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Eldred HABERT <stuff@eldred.fr>, alsa-devel@alsa-project.org
Subject: Re: Dual simulatenous output on single card not recognized
Date: Tue, 30 Nov 2021 08:40:25 -0600	[thread overview]
Message-ID: <8dc22d20-9d16-6114-03d1-da22f72ac81c@linux.intel.com> (raw)
In-Reply-To: <a006b912-71e1-548a-22ef-8f315e3be281@eldred.fr>



On 11/30/21 1:44 AM, Eldred HABERT wrote:
> 
> On 29/11/2021 19:18, Pierre-Louis Bossart wrote:
>> You may want to run 'alsa-info' and provide a link to the uploaded
>> results. It's hard to comment without any information on 'hardware
>> configurations like mine'.
>> Thanks.
> Sorry, I thought the output of `aplay -l` would be enough. The results
> are here;
> http://alsa-project.org/db/?f=bc64421df5181d1ba3bdf157c40d06dd52a7224b

ok, so you have a CNL-H chipset and no digital mics, so the legacy
HDaudio driver is used (not SOF w/ the DSP enabled).

There's nothing at the driver level that would prevent the use of
independent outputs, such as built-in speakers and HDMI concurrently.
You can verify this assertion by opening different terminals and trying

speaker-test -Dhw:0,0 -c2 -r48000

speaker-test -Dhw:0,3 -c2 -r48000 (use 0,7 8 9 10 as needed, depending
on which device is tagged as connected to a valid HDMI output in the
mixer 'Jack' status)

I am not sure though how the Gnome settings would let you do this. This
seems like a user-space problem to me?


      reply	other threads:[~2021-11-30 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 13:28 Dual simulatenous output on single card not recognized Eldred HABERT
2021-11-29 18:18 ` Pierre-Louis Bossart
2021-11-30  7:44   ` Eldred HABERT
2021-11-30 14:40     ` Pierre-Louis Bossart [this message]

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=8dc22d20-9d16-6114-03d1-da22f72ac81c@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=stuff@eldred.fr \
    /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