From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: tegra: add Acer Chromebook 13 device tree
Date: Thu, 15 Jan 2015 08:50:07 +0100 [thread overview]
Message-ID: <20150115075006.GA30799@ulmo> (raw)
In-Reply-To: <CAAObsKBo13fEy72EQe3V409fEEYpw0kQss5UgaOhk=GOVEEeYg@mail.gmail.com>
On Wed, Jan 14, 2015 at 08:02:25AM +0100, Tomeu Vizoso wrote:
> On 14 January 2015 at 01:32, Dylan Reid <dgreid@chromium.org> wrote:
> > On Tue, Jan 13, 2015 at 9:49 AM, Tomeu Vizoso <tomeu@tomeuvizoso.net> wrote:
> >> On 13 August 2014 at 03:56, Dylan Reid <dgreid@chromium.org> wrote:
> >>> The Acer Chromebook 13, codenamed "Big", contains an NVIDIA tegra124
> >>> processor and is similar to the Venice2 reference platform.
> >>>
> >>> The keyboard, USB 2, audio, HDMI, sdcard and emmc have been tested
> >>> and work on the 1366x768 models. I haven't tried on the HD systems
> >>> yet.
> >>
> >> Hi Dylan,
> >>
> >> do you have any notes on how you tested audio? I have been fiddling a
> >> bit with amixer but haven't been able to get any sound from the
> >> speakers nor the headphones.
> >
> > I don't have any notes, and it's been a while since I tried it. To
> > the best of my knowledge, I loaded the UCM config from the ChromeOS
> > tree manually with alsaucm, then enabled/disabled headphones from
> > there.
> >
> > https://chromium.googlesource.com/chromiumos/third_party/adhd/+/master/ucm-config/nyan/NVIDIA%20Tegra%20Venice2/
> >
> > The important stuff is all in the enable sequence of HiFi.conf
> >
> > Let me know if that helps.
>
> Thanks, it does work fine now. Will submit that conf file upstream.
Out of curiosity, where is "upstream" for UCM configuration files? It'd
be interesting to collect files for other Tegra boards there. I find it
rather tedious figuring out time and time again what control needs to be
toggled to enable a certain output.
Stephen, since you undoubtedly have the most experience with upstream
audio, do you happen to know if we have something like that for the
other upstream-supported boards?
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150115/3f2dafcd/attachment-0001.sig>
next prev parent reply other threads:[~2015-01-15 7:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 1:56 [PATCH 1/2] ARM: tegra: add Acer Chromebook 13 device tree Dylan Reid
2014-08-13 8:53 ` Thierry Reding
2014-08-13 16:23 ` Andrew Bresticker
2014-08-13 16:51 ` Olof Johansson
2014-08-13 16:57 ` Stephen Warren
2014-08-13 16:51 ` Stephen Warren
2014-08-13 16:55 ` Olof Johansson
2014-08-13 17:04 ` Andrew Bresticker
2014-08-13 17:12 ` Stephen Warren
2014-08-13 17:17 ` Andrew Bresticker
2014-08-13 18:42 ` Dylan Reid
2014-08-13 17:10 ` Stephen Warren
2014-08-13 17:23 ` Olof Johansson
2014-08-13 17:31 ` Stephen Warren
2014-08-13 17:37 ` Olof Johansson
2014-08-13 20:17 ` Stephen Warren
2014-08-13 19:07 ` Dylan Reid
2014-08-13 19:56 ` Stephen Warren
2014-08-14 8:40 ` Dylan Reid
2015-01-13 17:49 ` Tomeu Vizoso
2015-01-14 0:32 ` Dylan Reid
2015-01-14 7:02 ` Tomeu Vizoso
2015-01-15 7:50 ` Thierry Reding [this message]
2015-01-15 12:18 ` Tomeu Vizoso
2015-01-15 17:18 ` Stephen Warren
2015-01-19 9:01 ` Tomeu Vizoso
2015-01-19 19:29 ` Andrew Bresticker
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=20150115075006.GA30799@ulmo \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).