From: Andreas Mohr <andi@lisas.de>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: Andreas Mohr <andi@lisas.de>,
alsa-devel@alsa-project.org, krzysztof.h1@wp.pl,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] ES938 support for ES18xx driver
Date: Sun, 15 Sep 2013 23:23:58 +0200 [thread overview]
Message-ID: <20130915212358.GB32375@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <201309152304.27585.linux@rainbow-software.org>
On Sun, Sep 15, 2013 at 11:04:26PM +0200, Ondrej Zary wrote:
> On Sunday 15 September 2013 22:35:20 Andreas Mohr wrote:
> > What!?!? I didn't quite expect any kernel dev to have that one, too ;)
>
> Don't remember where I got it from but it looked nice so I bought it :)
Yup, e.g. the builtin amp is quite nice.
> > Thanks for hinting at the TLV control dB values thingy! Didn't know that
> > such thing existed, thus azt3328 does not have it (yet?).
>
> It's a nice thing, especially for cards that can go above 0 dB. You then know
> that the sound can be distorted when you set e.g. PCM volume too high.
Hmm, any hint how to precisely do dB values normalization scaling,
for a card where this is not documented? Or perhaps that's actually easy -
haven't thought about it...
> > Is there any chip ID/version register to be identified?
>
> No, there are only 8 registers, all(? - haven't tested) R/W.
OK, but possibly they happen to be creating another virtual register mapping range?
(i.e. index/data register combo?)
Andreas Mohr
next prev parent reply other threads:[~2013-09-15 21:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 20:40 Ondrej Zary
2013-09-15 18:49 ` Andreas Mohr
2013-09-15 20:25 ` Ondrej Zary
2013-09-15 20:35 ` Andreas Mohr
2013-09-15 21:04 ` Ondrej Zary
2013-09-15 21:23 ` Andreas Mohr [this message]
2013-09-16 16:14 ` Ondrej Zary
2013-09-16 20:20 ` Ondrej Zary
2013-09-19 17:36 ` Andreas Mohr
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=20130915212358.GB32375@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=alsa-devel@alsa-project.org \
--cc=krzysztof.h1@wp.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.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®