mfd: arizona: Correct handling of device tree gpio defaults
authorCharles Keepax <ckeepax@opensource.wolfsonmicro.com>
Thu, 3 Oct 2013 15:16:01 +0000 (16:16 +0100)
committerLee Jones <lee.jones@linaro.org>
Wed, 23 Oct 2013 15:21:44 +0000 (16:21 +0100)
commit91c739359ac9946a8e74a9640527a3f1034a76a7
tree0e76bf8fa3b51fab52430799372f7473fc8493b1
parent22d7dc8aba3bf34fdf324f43718c238075cc7cf7
mfd: arizona: Correct handling of device tree gpio defaults

When setting GPIO defaults we are required to make a distinction
between writing 0x0000 to the registers and leaving them untouched.

When we receive between 0x0000 and 0xFFFF (inclusive) from either
Platform Data or Device Tree, we should write the provided
configuration to the device. Conversely, when we receive >0xFFFF we
should leave the device configuration at its default setting.

This patch fixes a bug and ensures that configuration 0x0000 isn't
mistakenly written when the intention was to keep the default one.

Reported-by: Heather Lomond <heather.lomond@wolfsonmicro.com>
Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
drivers/mfd/arizona-core.c