From: Inha Song <ideal.song@samsung.com>
To: broonie@kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
alsa-devel@alsa-project.org, sameo@linux.intel.com,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
cw00.choi@samsung.com, robh+dt@kernel.org, galak@codeaurora.org,
ckeepax@opensource.wolfsonmicro.com, lee.jones@linaro.org
Subject: [PATCH 1/2] mfd: arizona: Add support for INn_MODE register control
Date: Sat, 09 Aug 2014 17:31:38 +0900 [thread overview]
Message-ID: <20140809173138.767b97fd@songinha-Samsung-DeskTop-System> (raw)
Some boards need to set the INn_MODE[1:0] register to change
the input signal patch. This wlf,inmode property is optional.
If present values must be specified by the number of
ARIZONA_MAX_INPUT.
Example:
- wlf,inmode = <2 0 2 0>; /* IN1, IN3 use DMIC */
Signed-off-by: Inha Song <ideal.song@samsung.com>
---
drivers/mfd/arizona-core.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c
index 10a0cb9..4b2eb73 100644
--- a/drivers/mfd/arizona-core.c
+++ b/drivers/mfd/arizona-core.c
@@ -560,6 +560,10 @@ static int arizona_of_get_core_pdata(struct arizona *arizona)
ret);
}
+ of_property_read_u32_array(arizona->dev->of_node,
+ "wlf,inmode",
+ arizona->pdata.inmode,
+ ARRAY_SIZE(arizona->pdata.inmode));
return 0;
}
--
2.0.0.390.gcb682f8
next reply other threads:[~2014-08-09 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 8:31 Inha Song [this message]
2014-08-12 8:28 ` [alsa-devel] [PATCH 1/2] mfd: arizona: Add support for INn_MODE register control Charles Keepax
[not found] ` <20140812082811.GB15833-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2014-08-13 0:26 ` Inha Song
2014-08-13 11:49 ` [alsa-devel] [PATCH v2 1/2] mfd: arizona: Add support for INn_Mode " Inha Song
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=20140809173138.767b97fd@songinha-Samsung-DeskTop-System \
--to=ideal.song@samsung.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.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