summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorAnton Vorontsov <avorontsov@ru.mvista.com>2008-12-03 22:27:38 +0300
committerKumar Gala <galak@kernel.crashing.org>2008-12-30 11:13:43 -0600
commit1b9e89046c31fd39d08742915b6bd72f6c239608 (patch)
tree0fbb35ccfd0c0645db7b304277d48aa95b2375b5 /Documentation
parent78c7705037ed9f107660178e17aa73f8bc4127e8 (diff)
downloadkernel-crypto-1b9e89046c31fd39d08742915b6bd72f6c239608.tar.gz
kernel-crypto-1b9e89046c31fd39d08742915b6bd72f6c239608.tar.xz
kernel-crypto-1b9e89046c31fd39d08742915b6bd72f6c239608.zip
powerpc/qe: Implement QE Pin Multiplexing API
With this API we're able to set a QE pin to the GPIO mode or a dedicated peripheral function. The API relies on the fact that QE gpio controllers are registered. If they aren't, the API won't work (gracefully though). There is one caveat though: if anybody occupied the node->data before us, or overwrote it, then bad things will happen. Luckily this is all in the platform code that we fully control, so this should never happen. I could implement more checks (for example we could create a list of successfully registered QE controllers, and compare the node->data in the qe_pin_request()), but this is unneeded if nobody is going to do silly things behind our back. Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions