From: Romain Perier <romain.perier@collabora.com>
To: Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Kumar Gala <galak@codeaurora.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org
Cc: Romain Perier <romain.perier@collabora.com>,
linux-rockchip@lists.infradead.org,
Sjoerd Simons <sjoerd.simons@collabora.co.uk>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] SoC: es8328-i2c: Add compatible for ES8323
Date: Mon, 23 Jan 2017 14:47:45 +0100 [thread overview]
Message-ID: <20170123134747.1385-2-romain.perier@collabora.com> (raw)
In-Reply-To: <20170123134747.1385-1-romain.perier@collabora.com>
This commit adds a compatible string for everest,es8323. This is an
audio codec that is compatible with es8328 and can be found for example
on the Firefly-RK3288 board.
Signed-off-by: Romain Perier <romain.perier@collabora.com>
---
Changes in v2: None
Documentation/devicetree/bindings/sound/es8328.txt | 5 ++++-
sound/soc/codecs/es8328-i2c.c | 2 ++
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/sound/es8328.txt b/Documentation/devicetree/bindings/sound/es8328.txt
index 33fbf05..86b6d6e 100644
--- a/Documentation/devicetree/bindings/sound/es8328.txt
+++ b/Documentation/devicetree/bindings/sound/es8328.txt
@@ -4,7 +4,10 @@ This device supports both I2C and SPI.
Required properties:
- - compatible : Should be "everest,es8328" or "everest,es8388"
+ - compatible : Should be one of the following:
+ - "everest,es8323"
+ - "everest,es8328"
+ - "everest,es8388"
- DVDD-supply : Regulator providing digital core supply voltage 1.8 - 3.6V
- AVDD-supply : Regulator providing analog supply voltage 3.3V
- PVDD-supply : Regulator providing digital IO supply voltage 1.8 - 3.6V
diff --git a/sound/soc/codecs/es8328-i2c.c b/sound/soc/codecs/es8328-i2c.c
index 318ab28..be3f03c 100644
--- a/sound/soc/codecs/es8328-i2c.c
+++ b/sound/soc/codecs/es8328-i2c.c
@@ -19,6 +19,7 @@
#include "es8328.h"
static const struct i2c_device_id es8328_id[] = {
+ { "es8323", 0 },
{ "es8328", 0 },
{ "es8388", 0 },
{ }
@@ -26,6 +27,7 @@ static const struct i2c_device_id es8328_id[] = {
MODULE_DEVICE_TABLE(i2c, es8328_id);
static const struct of_device_id es8328_of_match[] = {
+ { .compatible = "everest,es8323", },
{ .compatible = "everest,es8328", },
{ .compatible = "everest,es8388", },
{ }
--
2.9.3
next prev parent reply other threads:[~2017-01-23 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 13:47 [PATCH v2 0/3] Add support for es8323 and hdmi audio to the firefly-rk3288 Romain Perier
2017-01-23 13:47 ` Romain Perier [this message]
2017-01-23 13:47 ` [PATCH v2 2/3] arm: dts: rockchip: Don't set otp-gpio pinctrl by default in rk3288.dtsi Romain Perier
2017-01-23 13:47 ` [PATCH v2 3/3] arm: dts: Add support for ES8323 to the Firefly-RK3288 Romain Perier
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=20170123134747.1385-2-romain.perier@collabora.com \
--to=romain.perier@collabora.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=sjoerd.simons@collabora.co.uk \
--cc=tiwai@suse.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).