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:	Thu, 30 Jul 2009 10:59:56 +0100
From:	Ian Molton <ian@...menth.co.uk>
To:	pHilipp Zabel <philipp.zabel@...il.com>
CC:	Paul Mundt <lethal@...ux-sh.org>,
	Magnus Damm <magnus.damm@...il.com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Guennadi Liakhovetski <g.liakhovetski@....de>,
	linux-kernel@...r.kernel.org, Pierre Ossman <drzeus@...eus.cx>,
	Magnus Damm <damm@...nsource.se>
Subject: Re: MMC: Make the configuration memory resource optional

Ok I've spent some time thinking on this.

There is _no_ clean solution at present and Im not happy with having 
more than one clocking system co-existing in the mmc driver.

I will produce a patch to  completely remove all clocking and power 
control from the driver and make it use callbacks in order to achieve 
this. This will leave us with a clean driver that will be simple to 
adapt to the clock API.

I wont have time to work on it until next week, however, so if anyone 
wants to take a stab at it in the meantime, feel free to do so, and I'll 
review it next week.

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