From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 20/21] ASoC: codecs: Enable AB8500 CODEC for Device Tree
Date: Thu, 26 Jul 2012 12:50:55 +0100 [thread overview]
Message-ID: <20120726115055.GD3099@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1343298534-13611-21-git-send-email-lee.jones@linaro.org>
On Thu, Jul 26, 2012 at 11:28:53AM +0100, Lee Jones wrote:
> drivers/mfd/ab8500-core.c | 1 +
> include/linux/mfd/abx500/ab8500-codec.h | 6 ++-
> sound/soc/codecs/ab8500-codec.c | 79 +++++++++++++++++++++++++++++++
> 3 files changed, 84 insertions(+), 2 deletions(-)
Yet again no binding documentation....
> {
> .name = "ab8500-codec",
> + .of_compatible = "stericsson,ab8500-codec",
> },
Why are we doing this? The MFD cells are a totally Linux specific
thing, there's no reason to represent them in the device tree unless
they're in some way reusable and the "ab8500-codec" name suggests that's
unlikely. Just put the properties on the parent node and instantiate
the MFD cell as normal.
> + /* Has a non-standard Vamic been requested? */
> + if(of_get_property(np, "stericsson,amic1a-bias-vamic2", NULL))
Coding style.
> + if (!of_property_read_u32(np, "stericsson,earpeice-cmv", &value)) {
> + switch (value) {
> + case 950 :
> + codec->ear_cmv = EAR_CMV_0_95V;
> + break;
> + case 1100 :
> + codec->ear_cmv = EAR_CMV_1_10V;
> + break;
> + case 1270 :
> + codec->ear_cmv = EAR_CMV_1_27V;
> + break;
> + case 1580 :
> + codec->ear_cmv = EAR_CMV_1_58V;
> + break;
> + default :
> + codec->ear_cmv = EAR_CMV_UNKNOWN;
> + dev_err(dev, "Unsuitable earpiece voltage found in DT\n");
The platform data code picks a default, can't the DT code do the same?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120726/a86beb69/attachment.sig>
next prev parent reply other threads:[~2012-07-26 11:50 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 10:28 [PATCH 00/21] Some fixes and DT enablement for ux500 audio Lee Jones
2012-07-26 10:28 ` [PATCH 01/21] ARM: ux500: Remove unused snowball_of_platform_devs struct Lee Jones
2012-07-26 10:28 ` [PATCH 02/21] MFD: db8500-prcmu: Ensure AB8500 platform data is passed through MFD Core Lee Jones
2012-07-26 10:28 ` [PATCH 03/21] ARM: ux500: Clean-up MSP platform code Lee Jones
2012-07-26 10:28 ` [PATCH 04/21] ASoC: ux500: Strengthen error checking after memory allocation Lee Jones
2012-07-26 11:57 ` Mark Brown
2012-07-26 10:28 ` [PATCH 05/21] ASoC: ux500: Include the correct header files Lee Jones
2012-07-26 11:58 ` Mark Brown
2012-07-26 10:28 ` [PATCH 06/21] ASoC: dapm: If one widget fails, do not force all subsequent widgets to fail too Lee Jones
2012-07-26 11:54 ` Mark Brown
2012-07-26 10:28 ` [PATCH 07/21] ASoC: io: Prevent use of regmap if request fails Lee Jones
2012-07-26 11:32 ` Mark Brown
2012-07-26 11:38 ` Lee Jones
2012-07-26 11:42 ` Mark Brown
2012-07-26 14:51 ` Lee Jones
2012-07-26 15:12 ` Mark Brown
2012-07-26 15:23 ` Lee Jones
2012-07-26 15:25 ` Mark Brown
2012-07-26 16:05 ` Lee Jones
2012-07-26 20:23 ` Mark Brown
2012-07-26 10:28 ` [PATCH 08/21] ARM: ux500: Add AB8500 CODEC node to DB8500 Device Tree Lee Jones
2012-07-26 10:28 ` [PATCH 09/21] ARM: ux500: Add MSP devices " Lee Jones
2012-07-26 10:28 ` [PATCH 10/21] ARM: ux500: Add ux500 PCM " Lee Jones
2012-07-26 10:28 ` [PATCH 11/21] ARM: ux500: Add all encompassing Sound node " Lee Jones
2012-07-26 10:28 ` [PATCH 12/21] ARM: ux500: Fork MSP platform registration for step-by-step DT enablement Lee Jones
2012-07-26 10:28 ` [PATCH 13/21] ARM: ux500: Ensure probing of Audio devices when Device Tree is enabled Lee Jones
2012-07-26 10:28 ` [PATCH 14/21] ARM: ux500: Enable HIGHMEM on all mop500 platforms Lee Jones
2012-07-26 10:28 ` [PATCH 15/21] ARM: ux500: Pass MSP DMA platform data though AUXDATA Lee Jones
2012-07-26 10:28 ` [PATCH 16/21] ASoC: Ux500: Enable MOP500 driver for Device Tree Lee Jones
2012-07-26 11:37 ` Mark Brown
2012-07-26 13:51 ` Lee Jones
2012-07-26 13:53 ` Mark Brown
2012-07-26 14:51 ` Lee Jones
2012-07-26 10:28 ` [PATCH 17/21] ASoC: Ux500: Enable ux500 PCM " Lee Jones
2012-07-26 11:38 ` Mark Brown
2012-07-26 13:52 ` Lee Jones
2012-07-26 14:22 ` Mark Brown
2012-07-26 14:55 ` Lee Jones
2012-07-26 10:28 ` [PATCH 18/21] ASoC: Ux500: Move MSP pinctrl setup into the MSP driver Lee Jones
2012-07-26 10:28 ` [PATCH 19/21] ASoC: Ux500: Enable ux500 MSP driver for Device Tree Lee Jones
2012-07-26 11:45 ` Mark Brown
2012-07-26 10:28 ` [PATCH 20/21] ASoC: codecs: Enable AB8500 CODEC " Lee Jones
2012-07-26 11:50 ` Mark Brown [this message]
2012-07-26 14:00 ` Lee Jones
2012-07-26 14:28 ` Mark Brown
2012-07-26 15:01 ` Lee Jones
2012-07-26 15:14 ` Mark Brown
2012-07-26 15:17 ` Lee Jones
2012-07-26 14:15 ` Lee Jones
2012-07-26 14:43 ` Mark Brown
2012-07-26 15:19 ` Lee Jones
2012-07-26 15:24 ` Mark Brown
2012-07-26 10:28 ` [PATCH 21/21] ARM: ux500: Rename MSP board file to something more meaningful Lee Jones
2012-07-26 11:28 ` [PATCH 00/21] Some fixes and DT enablement for ux500 audio Mark Brown
2012-07-26 11:36 ` Lee Jones
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=20120726115055.GD3099@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).