From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
Misael Lopez Cruz <misael.lopez@ti.com>
Subject: Re: [PATCH 4/4] ASoC: omap-abe-twl6040: Add device tree support
Date: Wed, 09 May 2012 14:45:17 +0300 [thread overview]
Message-ID: <4FAA58CD.5010609@ti.com> (raw)
In-Reply-To: <20120508135912.GR15893@opensource.wolfsonmicro.com>
On 05/08/2012 04:59 PM, Mark Brown wrote:
> On Tue, May 08, 2012 at 03:15:14PM +0300, Peter Ujfalusi wrote:
>
>> abe-twl6040,jack_detection = <0>;
>
> Shouldn't this be a boolean property that simply needs to be present to
> flag detection?
It does work like that as well. This property only need to be there (and
to be set to 1) if the board can detect the jack.
>
>> dai-link1,codec = <&twl6040_codec>;
>> dai-link1,dai = <&mcpdm>;
>
> This seems like it ought to be an array of nodes, one per link, instead
> of having an index in the property name. It should certainly be easier
> to parse.
Very true. We can handle this in a similar way as we handle the
routings. It might be a good idea to add this as a generic ASoC core
feature?
Something like:
abe-twl6040,dai-link =
<&twl6040_codec>, <&mcpdm>;
Other platforms could use this and we could handle it with the same code
in the core.
> It also seems like it's not at all board specific and should be factored
> out.
>
>> abe-twl6040,audio-routing =
>> "Headset Stereophone", "HSOL",
>> "Headset Stereophone", "HSOR",
>
> Binding should document what the board-defined nodes are.
OK, I'll update the documentation (also covering the codec)
>
>> +Example:
>> +
>> +sound { /* ASoC */
>> + compatible = "ti,abe-twl6040";
>> + abe-twl6040,model = "SDP4430";
>
> Please don't repeat your binding documentation in the changelog, it's
> already in the patch and means it comes after the documentation.
OK, I'll remove the examples from the changelog.
--
Péter
next prev parent reply other threads:[~2012-05-09 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 12:15 [PATCH 0/4] omap-abe-twl6040: Device tree support Peter Ujfalusi
2012-05-08 12:15 ` [PATCH 1/4] ASoC: omap-abe-twl6040: Keep only one snd_soc_dai_link structure Peter Ujfalusi
2012-05-08 15:52 ` Mark Brown
2012-05-08 12:15 ` [PATCH 2/4] ASoC: omap-abe-twl6040: Move Digital Mic widget into dapm table Peter Ujfalusi
2012-05-08 18:30 ` Mark Brown
2012-05-08 12:15 ` [PATCH 3/4] ASoC: omap-abe-twl6040: Introduce driver data for runtime parameters Peter Ujfalusi
2012-05-08 18:31 ` Mark Brown
2012-05-08 12:15 ` [PATCH 4/4] ASoC: omap-abe-twl6040: Add device tree support Peter Ujfalusi
2012-05-08 13:59 ` Mark Brown
2012-05-09 11:45 ` Peter Ujfalusi [this message]
2012-05-09 15:59 ` 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=4FAA58CD.5010609@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=misael.lopez@ti.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).