linux-kernel - Re: MMC: Make the configuration memory resource optional

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]

Date:	Wed, 05 Aug 2009 13:07:07 +0100
From:	Ian Molton <ian@...menth.co.uk>
To:	Magnus Damm <magnus.damm@...il.com>
CC:	Guennadi Liakhovetski <g.liakhovetski@....de>,
	pHilipp Zabel <philipp.zabel@...il.com>,
	Paul Mundt <lethal@...ux-sh.org>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	linux-kernel@...r.kernel.org, Pierre Ossman <drzeus@...eus.cx>,
	Magnus Damm <damm@...nsource.se>
Subject: Re: MMC: Make the configuration memory resource optional

Magnus Damm wrote:

> Sorry for not answering your question earlier. This may sound starnge,
> but I don't have any datasheet. I do however think that you can assume
> a 1:1 host/card clock capability, at least to begin with.

Im not so sure I can - the 1:1 clock on MFD is selected via the CNF IO 
area and as such the other users of the driver that dont have CNF areas 
cannot possibly be using this method. Do you have your own method for 
clock selection, or are you using the routine in tmio-mmc.c - if the 
latter then you are certainly not running a 1:1 clock

> So please use the clock framework to enable/disable the clock and get
> the rate, and we'll do our best to adjust the architecture code after
> that. And I'll cook up a patch for Runtime PM on top of that if that's
> ok with you.

I _cant_ use the clock framework by itself in tmio-mmc because that 
would break each and every MFD user of the driver.

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