From: Oder <oder_chiou@realtek.com>
To: Mark Brown <broonie@kernel.org>
Cc: Oder Chiou <oder_chiou@realtek.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
jarkko.nikula@linux.intel.com, Bard Liao <bardliao@realtek.com>,
Flove <flove@realtek.com>
Subject: Re: [PATCH v2] ASoC: rt5640: Add minimal support for RT5642
Date: Tue, 22 Apr 2014 22:14:47 +0800 [thread overview]
Message-ID: <CAD+35SMF1jtB_W1uY-8fhfbpd7-2yXp08Bz_vr3r5+DMDGiDWA@mail.gmail.com> (raw)
In-Reply-To: <20140422115347.GR12304@sirena.org.uk>
2014-04-22 19:53 GMT+08:00 Mark Brown <broonie@kernel.org>:
> 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.
We've sent the patch of binding document to
"/Documentation/devicetree/bindings/sound/rt5640.txt" for rt5639.
If it is not satisfied, please kindly tell us what we need to do,
thank you very much.
next prev parent reply other threads:[~2014-04-22 14:15 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
2014-04-22 14:14 ` Oder [this message]
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=CAD+35SMF1jtB_W1uY-8fhfbpd7-2yXp08Bz_vr3r5+DMDGiDWA@mail.gmail.com \
--to=oder_chiou@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=flove@realtek.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=lgirdwood@gmail.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.