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: <4A70DE01.4030905@mnementh.co.uk>
Date:	Thu, 30 Jul 2009 00:40:49 +0100
From:	Ian Molton <ian@...menth.co.uk>
To:	pHilipp Zabel <philipp.zabel@...il.com>
CC:	Guennadi Liakhovetski <g.liakhovetski@....de>,
	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

pHilipp Zabel wrote:

>>>  struct tmio_mmc_data {
>>>        const unsigned int              hclk;
>>> +       const char                      *clk_name;
>> Drop that.
> 
> Actually, this struct can be dropped completely and the HCLK rate can
> be determined with clk_get_rate.

Actually it cant because MFD devices have different hclk frequencies, 
and the mmc driver needs to know this. MFD drivers cannot pass the hclk 
rate in using the clk API at present.

-Ian

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ