From: Mark Brown <broonie@kernel.org>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Jean-Francois Moine <moinejf@free.fr>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Liam Girdwood <lgirdwood@gmail.com>,
devicetree-discuss@vger.kernel.org,
Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: [PATCH v3] ARM: kirkwood: extend the kirkwood i2s driver for DT usage
Date: Tue, 23 Jul 2013 14:20:16 +0100 [thread overview]
Message-ID: <20130723132016.GC9858@sirena.org.uk> (raw)
In-Reply-To: <51EE7E1A.3040301@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1345 bytes --]
On Tue, Jul 23, 2013 at 02:59:06PM +0200, Sebastian Hesselbarth wrote:
> On 07/23/13 14:34, Mark Brown wrote:
> >As others have pointed out if you need to change the clock get code
> >there's something wrong here, DT should be handled transparently by the
> >clock API.
> IMHO the reason why of_clk_get() was/is mis-used in that way is mostly
> compatibility with legacy platform_data based setup.
I'm sorry, but this doesn't make a great deal of sense to me. Can you
be more specific?
> As Sascha Hauer pointed out, clocks should be distinguished by names
> (clock-names property) instead of position and then use
> devm_clk_get(&pdev->dev, "internal") and
> devm_clk_get(&pdev->dev, "external") respectively.
> This will possibly also require to update platform_data and legacy
> users of kirkwood-i2s or have different setup functions for non-DT
> and DT.
Why would this be required? The driver is already asking for multiple
clocks...
> Also, while ASoC API separates the audio-controller into cpu-side
> and codec-side parts, the DT should not. IIRC and as Russell repeated
You mean DAI and DMA here? I already commented on that in my review of
the DMA binding.
> again, we mentioned to merge kirkwood-i2s.c and kirkwood-dma.c into
> a single file, didn't we?
That's been discussed several times but nobody's actually done it.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-07-23 13:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 8:46 [PATCH v3] ARM: kirkwood: extend the kirkwood i2s driver for DT usage Jean-Francois Moine
2013-07-23 8:53 ` Russell King - ARM Linux
2013-07-23 9:03 ` Lars-Peter Clausen
2013-07-23 9:08 ` Sascha Hauer
2013-07-23 9:39 ` Russell King - ARM Linux
2013-07-23 9:48 ` [alsa-devel] " Sascha Hauer
2013-07-23 12:34 ` Mark Brown
2013-07-23 12:59 ` [alsa-devel] " Sebastian Hesselbarth
2013-07-23 13:20 ` Mark Brown [this message]
2013-07-23 13:30 ` Sebastian Hesselbarth
2013-07-23 13:50 ` Russell King - ARM Linux
2013-07-23 17:04 ` Mark Brown
2013-07-23 15:01 ` [alsa-devel] " Mark Brown
2013-07-23 15:19 ` Russell King - ARM Linux
2013-07-23 17:16 ` Mark Brown
2013-07-23 15:34 ` [alsa-devel] " Jean-Francois Moine
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=20130723132016.GC9858@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree-discuss@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tiwai@suse.de \
/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).