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>] [day] [month] [year] [list]
Date:	Mon, 14 Dec 2009 10:57:52 -0800
From:	Robert Emanuele <rob@...nuele.us>
To:	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	linux-kernel@...r.kernel.org
Subject: Enhanced MMC/SD Card Power Control

Greetings once again,

Over the summer I had submitted a series of patches for the atmel-mci
driver.  One of these was for power control of each mci slot.

http://lists.arm.linux.org.uk/lurker/message/20090617.005438.eb1570d9.en.html

I'd like to resubmit this and enhance it slightly.  The current work
I'm doing is on Atmel's AT91SAM9G45.  In the patch above I include a
power control pin and the state it needs to be pulled.  I'd like to
change this to two platform defined functions for power on and power
off.  This way given which ever platform this is being used on that
platforn can concisely define how to move from a power on state to a
power off and vice versa.

For example, on my platform I would pull some GPIO high to turn off a
FET to the power of the slot and then change the function of all the
pins going to the card (except for the detect pin of course) to open
drains.  Then on power up I would do the reverse.

Given what I have described here, where would be the most logical
place to put such code?  I was assuming that it would go into the
platform configuration into the board file (board-mynewboard.c in
arch/arm/mach-at91/).

Thank you for your help and comments,

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