From: Mark Brown <broonie@kernel.org>
To: mengdong.lin@intel.com
Cc: bardliao@realtek.com, alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 1/3] ASoC: rt5670: redefine ASRC control registers 0x84 and 0x85
Date: Wed, 7 Jan 2015 17:42:44 +0000 [thread overview]
Message-ID: <20150107174244.GD2634@sirena.org.uk> (raw)
In-Reply-To: <1420597146-4101-1-git-send-email-mengdong.lin@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 319 bytes --]
On Wed, Jan 07, 2015 at 10:19:06AM +0800, mengdong.lin@intel.com wrote:
> From: Bard Liao <bardliao@realtek.com>
>
> The previous definition of registers 0x84 and 0x85 doesn't match the datasheet.
> So this patch removes the wrong definition and writes a new one for the two
> registers.
Applied all, thanks.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-01-07 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 9:48 [PATCH 1/3] ASoC: rt5670: fix bit definition for ASRC control mengdong.lin
2015-01-05 9:48 ` [PATCH 2/3] ASoC: rt5670: add API to select ASRC clock source mengdong.lin
2015-01-05 9:48 ` [PATCH 3/3] ASoC: Intel: Select RT5672 ASRC clock source on Cherrytrail and Braswell mengdong.lin
2015-01-05 18:17 ` [PATCH 1/3] ASoC: rt5670: fix bit definition for ASRC control Mark Brown
2015-01-06 2:08 ` Bard Liao
2015-01-06 11:03 ` Mark Brown
2015-01-07 2:16 ` Lin, Mengdong
2015-01-07 2:19 ` [PATCH v2 1/3] ASoC: rt5670: redefine ASRC control registers 0x84 and 0x85 mengdong.lin
2015-01-07 17:42 ` Mark Brown [this message]
2015-01-07 2:19 ` [PATCH v2 2/3] ASoC: rt5670: add API to select ASRC clock source mengdong.lin
2015-01-07 2:19 ` [PATCH v2 3/3] ASoC: Intel: Select RT5672 ASRC clock source on Cherrytrail and Braswell mengdong.lin
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=20150107174244.GD2634@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=mengdong.lin@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;
as well as URLs for NNTP newsgroup(s).