summaryrefslogtreecommitdiff
path: root/mm
diff options
context:
space:
mode:
authorMatti J. Aaltonen <matti.j.aaltonen@nokia.com>2011-02-25 14:44:19 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2011-02-25 15:07:36 -0800
commitac3c8304190ed0daaa2fb01ce2a069be5e2a52a7 (patch)
treebaebdd925a0f9d2b959b116e50d107c9dfee69e7 /mm
parentd73fa4b914eab332d9919132b273b6797b8aface (diff)
downloadlinux-3.10-ac3c8304190ed0daaa2fb01ce2a069be5e2a52a7.tar.gz
linux-3.10-ac3c8304190ed0daaa2fb01ce2a069be5e2a52a7.tar.bz2
linux-3.10-ac3c8304190ed0daaa2fb01ce2a069be5e2a52a7.zip
drivers/nfc/pn544.c: add missing regulator
The regulator framework is used for power management. The regulators are only named in the driver code, the actual control stuff is in the board file for each architecture or use case. The PN544 chip has three regulators that can be controlled or not - depending on the architecture where the chip is being used. So some of the regulators may not be controllable. In our current case the third regulator, which was missing from the code, went unnoticed because we didn't need to control it. To be as general as possible - in this respect - the driver needs to list all regulators. Then the board file can be used to actually set the usage. Signed-off-by: Matti J. Aaltonen <matti.j.aaltonen@nokia.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions