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, Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <rob.herring@calxeda.com>,
devicetree-discuss@vger.kernel.org,
Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: [alsa-devel] [PATCH v3] ARM: kirkwood: extend the kirkwood i2s driver for DT usage
Date: Tue, 23 Jul 2013 16:01:50 +0100 [thread overview]
Message-ID: <20130723150150.GH9858@sirena.org.uk> (raw)
In-Reply-To: <51EE8591.7060005@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
On Tue, Jul 23, 2013 at 03:30:57PM +0200, Sebastian Hesselbarth wrote:
> On 07/23/13 15:20, Mark Brown wrote:
> >Why would this be required? The driver is already asking for multiple
> >clocks...
> The driver is asking for multiple *DT based* clocks. Legacy
> platform_data has never been updated to reflect that. Mainly because
> multiple clocks are only supported on Dove, which has no active non-DT
> board in mainline.
Why would platform data have anything to do with this? To repeat again
the way the clocks are mapped should be totally transparent to the
driver requesting them, if it isn't then the driver is not using the API
properly.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-23 15:02 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 ` [alsa-devel] " Sascha Hauer
2013-07-23 9:39 ` Russell King - ARM Linux
2013-07-23 9:48 ` 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
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 ` Mark Brown [this message]
2013-07-23 15:19 ` Russell King - ARM Linux
2013-07-23 17:16 ` Mark Brown
2013-07-23 15:34 ` 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=20130723150150.GH9858@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