summaryrefslogtreecommitdiffstats
path: root/drivers/mfd/axp20x-i2c.c
diff options
context:
space:
mode:
authorMaxime Ripard <maxime.ripard@bootlin.com>2019-03-18 13:55:48 +0100
committerLee Jones <lee.jones@linaro.org>2019-05-14 08:13:26 +0100
commit4f799e47adb35e1e0e7a598eb856f3ac6c18b4aa (patch)
tree8f780d63e75d1c437b8dc98c3d7c2250e99f565a /drivers/mfd/axp20x-i2c.c
parent54349b3ce82e3369a7c7b2960f19c1bea876c5fb (diff)
downloadblackbird-op-linux-4f799e47adb35e1e0e7a598eb856f3ac6c18b4aa.tar.gz
blackbird-op-linux-4f799e47adb35e1e0e7a598eb856f3ac6c18b4aa.zip
mfd: axp20x: Allow the AXP223 to be probed by I2C
The AXP223 can be used both using the RSB proprietary bus, or a more traditional I2C bus. The RSB is a faster bus and provides more features (like some integrity checks on the messages), so it's usually preferrable to use it, but since it's proprietary, when we want to use the PMIC in a multi-master setup, the i2c might make sense as well. Let's add that possibility. Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com> Acked-by: Chen-Yu Tsai <wens@csie.org> Signed-off-by: Lee Jones <lee.jones@linaro.org>
Diffstat (limited to 'drivers/mfd/axp20x-i2c.c')
-rw-r--r--drivers/mfd/axp20x-i2c.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/mfd/axp20x-i2c.c b/drivers/mfd/axp20x-i2c.c
index a7b7c5423ea5..c2e8a0dee7f8 100644
--- a/drivers/mfd/axp20x-i2c.c
+++ b/drivers/mfd/axp20x-i2c.c
@@ -65,6 +65,7 @@ static const struct of_device_id axp20x_i2c_of_match[] = {
{ .compatible = "x-powers,axp202", .data = (void *)AXP202_ID },
{ .compatible = "x-powers,axp209", .data = (void *)AXP209_ID },
{ .compatible = "x-powers,axp221", .data = (void *)AXP221_ID },
+ { .compatible = "x-powers,axp223", .data = (void *)AXP223_ID },
{ .compatible = "x-powers,axp806", .data = (void *)AXP806_ID },
{ },
};
@@ -75,6 +76,7 @@ static const struct i2c_device_id axp20x_i2c_id[] = {
{ "axp202", 0 },
{ "axp209", 0 },
{ "axp221", 0 },
+ { "axp223", 0 },
{ "axp806", 0 },
{ },
};
OpenPOWER on IntegriCloud