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]

Message-ID: <aec7e5c30908041908p568f413albef7dede3fd2cb83@mail.gmail.com>
Date:	Wed, 5 Aug 2009 11:08:21 +0900
From:	Magnus Damm <magnus.damm@...il.com>
To:	Ian Molton <ian@...menth.co.uk>
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

Hi Ian,

On Wed, Aug 5, 2009 at 3:21 AM, Ian Molton<ian@...menth.co.uk> wrote:
> I still do not have info from people about wether non MFD users of the
> tmio-mmc driver have a 1:1 host/card clock capability.
>
> I could really use the information if anyone expects me to sort this
> situation out.

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.

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.

Thanks.

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