summaryrefslogtreecommitdiffstats
path: root/drivers/gpu
diff options
context:
space:
mode:
authorAndres Salomon <dilinger@queued.net>2010-12-21 13:04:52 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2010-12-23 15:31:48 -0800
commit44658a11f312fb9217674cb90b1a11cbe17fd18d (patch)
tree599549060943c051e8943f85da80e4905d941016 /drivers/gpu
parent001851659354cce436b749a793f3512a53394d80 (diff)
downloadblackbird-op-linux-44658a11f312fb9217674cb90b1a11cbe17fd18d.tar.gz
blackbird-op-linux-44658a11f312fb9217674cb90b1a11cbe17fd18d.zip
cs5535-gpio: handle GPIO regs where higher (clear) bits are set
The default for non-READ_BACK GPIO regs is to have the clear bits set; this means that our original errata fix was too simplistic. This changes it to the following behavior: - when setting GPIOs, ignore the higher order bits (they're for clearing, we don't need to care about them). - when clearing GPIOs, keep all the bits, but unset (via XOR) the lower order bit that negates the clear bit that we care about. That is, if we're clearing GPIO 26 (val = 0x04000000), we first XOR what's currently in the register with 0x0400 (GPIO 26's SET bit), and then OR that with the GPIO 26's CLEAR bit. Tested-by: Daniel Drake <dsd@laptop.org> Signed-off-by: Andres Salomon <dilinger@queued.net> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/gpu')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud