From: Alexander <subaparts@yandex.ru>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, ryan@bluewatersys.com,
linux-arm-kernel@lists.infradead.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH 2/3] ASoC: CS4271 codec support
Date: Thu, 09 Dec 2010 01:59:26 +0300 [thread overview]
Message-ID: <1291849166.31916.74.camel@r60e> (raw)
In-Reply-To: <20101208130558.GE16418@rakim.wolfsonmicro.main>
Dear Mark,
On Wed, 2010-12-08 at 13:05 +0000, Mark Brown wrote:
> > +static const char *cs4271_de_texts[] = {"None", "44.1KHz", "48KHz", "32KHz"};
> > +static const struct soc_enum cs4271_de_enum =
> > + SOC_ENUM_SINGLE(CS4271_DACCTL, 4, 4, cs4271_de_texts);
>
> Ideally the deemphasis would be managed based on the sample rate.
>
I'm not sure if it's necessary feature at all. And the way it should be
managed is something unclear to me )
All other issues were corrected, the patch will follow soon...
Best regards,
Alexander A. Sverdlin.
WARNING: multiple messages have this Message-ID (diff)
From: subaparts@yandex.ru (Alexander)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ASoC: CS4271 codec support
Date: Thu, 09 Dec 2010 01:59:26 +0300 [thread overview]
Message-ID: <1291849166.31916.74.camel@r60e> (raw)
In-Reply-To: <20101208130558.GE16418@rakim.wolfsonmicro.main>
Dear Mark,
On Wed, 2010-12-08 at 13:05 +0000, Mark Brown wrote:
> > +static const char *cs4271_de_texts[] = {"None", "44.1KHz", "48KHz", "32KHz"};
> > +static const struct soc_enum cs4271_de_enum =
> > + SOC_ENUM_SINGLE(CS4271_DACCTL, 4, 4, cs4271_de_texts);
>
> Ideally the deemphasis would be managed based on the sample rate.
>
I'm not sure if it's necessary feature at all. And the way it should be
managed is something unclear to me )
All other issues were corrected, the patch will follow soon...
Best regards,
Alexander A. Sverdlin.
next prev parent reply other threads:[~2010-12-08 22:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 12:02 [PATCH 2/3] ASoC: CS4271 codec support Alexander
2010-12-08 12:02 ` Alexander
2010-12-08 13:05 ` Mark Brown
2010-12-08 13:05 ` Mark Brown
2010-12-08 22:59 ` Alexander [this message]
2010-12-08 22:59 ` Alexander
2010-12-08 23:16 ` Mark Brown
2010-12-08 23:16 ` Mark Brown
2010-12-08 13:07 ` Jamie Iles
2010-12-08 13:07 ` Jamie Iles
2010-12-08 13:39 ` Mark Brown
2010-12-08 13:39 ` Mark Brown
2010-12-08 14:47 ` Jamie Iles
2010-12-08 14:47 ` Jamie Iles
2010-12-08 14:58 ` Mark Brown
2010-12-08 14:58 ` Mark Brown
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=1291849166.31916.74.camel@r60e \
--to=subaparts@yandex.ru \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@slimlogic.co.uk \
--cc=ryan@bluewatersys.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.