linux-kernel - Re: [PATCH] tmio_mmc: Optionally support using platform clock

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4A6EFFAF.10603@mnementh.co.uk>
Date:	Tue, 28 Jul 2009 14:39:59 +0100
From:	Ian Molton <ian@...menth.co.uk>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
CC:	linux-kernel@...r.kernel.org, Magnus Damm <damm@...nsource.se>,
	akpm@...ux-foundation.org, Matt Fleming <matt@...sole-pimps.org>,
	Philip Langdale <philipl@...rt.org>
Subject: Re: [PATCH] tmio_mmc: Optionally support using platform clock

Guennadi Liakhovetski wrote:
> If the platform device has a clock associated with the tmio-mmc device, 
> use it.

As RMK has stated manny times before now, you cannot pass struct clks to 
devices like this, they should be claimed using the clk api.

The problem for tmio-mmc is that the struct clk is tied to the 
architecture code, so at present we cant create new clk providers. What 
we need is for the clk api to be divorced from the arch code so that the 
TMIO MFD driver can create its own clocks that can be claimed by its 
children.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/