linux-kernel - Re: [alsa-devel] [PATCH v3] ARM: kirkwood: extend the kirkwood i2s driver for DT usage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130723150150.GH9858@sirena.org.uk>
Date:	Tue, 23 Jul 2013 16:01:50 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Cc:	Jean-Francois Moine <moinejf@...e.fr>, alsa-devel@...a-project.org,
	Takashi Iwai <tiwai@...e.de>, linux-kernel@...r.kernel.org,
	Liam Girdwood <lgirdwood@...il.com>,
	Rob Herring <rob.herring@...xeda.com>,
	devicetree-discuss@...r.kernel.org,
	Russell King <rmk+kernel@....linux.org.uk>
Subject: Re: [alsa-devel] [PATCH v3] ARM: kirkwood: extend the kirkwood i2s
 driver for DT usage

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.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)