From: Mark Brown <broonie@kernel.org>
To: bardliao@realtek.com
Cc: oder_chiou@realtek.com, alsa-devel@alsa-project.org,
jarkko.nikula@linux.intel.com, lgirdwood@gmail.com,
flove@realtek.com
Subject: Re: [PATCH v2] ASoC: rt5640: Add minimal support for RT5642
Date: Tue, 22 Apr 2014 12:53:47 +0100 [thread overview]
Message-ID: <20140422115347.GR12304@sirena.org.uk> (raw)
In-Reply-To: <1397701446-11977-1-git-send-email-bardliao@realtek.com>
[-- Attachment #1.1: Type: text/plain, Size: 628 bytes --]
On Thu, Apr 17, 2014 at 10:24:06AM +0800, bardliao@realtek.com wrote:
> From: Bard Liao <bardliao@realtek.com>
>
> We have been using rt5640.c codec driver with RT5642 codec chip before commit
> 022d21f004c1 ("ASoC: rt5640: add rt5639 support"). That commits starts using
> device ID reading in reset register for adding device specific controls and
> routes runtime.
Applied, thanks. Now I look again and remember that it exists I see
there's no update to the DT portions of the code - please submit a
followup patch adding the device to the DT bindings and to the OF match
table. rt5639 is also missing there.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-04-22 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 2:24 [PATCH v2] ASoC: rt5640: Add minimal support for RT5642 bardliao
2014-04-17 19:01 ` Mark Brown
2014-04-22 6:01 ` Jarkko Nikula
2014-04-22 11:53 ` Mark Brown [this message]
2014-04-22 14:14 ` Oder
2014-04-22 17:12 ` Mark Brown
2014-04-25 22:08 ` Stephen Warren
2014-04-26 0:22 ` Mark Brown
2014-04-28 6:47 ` Jarkko Nikula
2014-04-27 14:57 ` [PATCH v2] ASoC: rt5640: Add minimal supportforRT5642 Bard Liao
2014-04-28 8:52 ` 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=20140422115347.GR12304@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=flove@realtek.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.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