Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Nikula, Jarkko" <jarkko.nikula@intel.com>
Subject: Re: Baytrail init file for alsa-utils
Date: Mon, 03 Nov 2014 11:11:13 +0000	[thread overview]
Message-ID: <1415013073.2471.11.camel@loki> (raw)
In-Reply-To: <1415008294.2406.107.camel@hadess.net>

On Mon, 2014-11-03 at 10:51 +0100, Bastien Nocera wrote:
> Hey,
> 
> I've done some work on the community generated "alsa state" file for
> Baytrail tablets, and shrunk it massively:
> https://github.com/AdamWill/baytrail-m/blob/master/alsa/t100_B.state
> 
> Are there any tools, or hints as to how I might convert that to an
> "init" file that alsactl could run to set the default state of the
> mixer?

"alsactl store" should write it to the correct system directory.

> 
> Or have any Intel folks already done that work?
> 

Jarkko has been working on Baytrail so best for him to answer.

> I'll have a few more sound-related questions for that tablet, for which
> I could do with a few hints as to where to direct the questions/bug
> reports:
> - no jack sensing support (driver problem?)
> - left/right headphones output is inverted (another driver bug?)
> - HDMI audio is not detected (Intel video driver bug?)
> 

Liam

  reply	other threads:[~2014-11-03 11:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03  9:51 Baytrail init file for alsa-utils Bastien Nocera
2014-11-03 11:11 ` Liam Girdwood [this message]
2014-11-03 13:03   ` Bastien Nocera
2014-11-18 12:05     ` Bastien Nocera
2014-11-18 12:41       ` Jarkko Nikula
2014-11-20  4:56         ` Bastien Nocera

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=1415013073.2471.11.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=hadess@hadess.net \
    --cc=jarkko.nikula@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox