diff options
author | Stefan Agner <stefan@agner.ch> | 2013-12-06 13:51:46 +0100 |
---|---|---|
committer | Lee Jones <lee.jones@linaro.org> | 2014-01-21 08:28:01 +0000 |
commit | 844a4f0d8a5ae075e06b6a673bbc0596510046df (patch) | |
tree | 5a02a6de3bd27ced52e31b049d45e4068c63dd91 /drivers/mfd/mc13xxx-core.c | |
parent | e0a3da80c65dc427c30829eb3e361507f843778f (diff) | |
download | blackbird-op-linux-844a4f0d8a5ae075e06b6a673bbc0596510046df.tar.gz blackbird-op-linux-844a4f0d8a5ae075e06b6a673bbc0596510046df.zip |
regulator: tps6586x: Add and use correct voltage table
Depending on the regulator version, the voltage table might be
different. Use version specific regulator tables in order to select
correct voltage table. For the following regulator versions different
voltage tables are now used:
* TPS658623: Use correct voltage table for SM2
* TPS658643: New voltage table for SM2
Both versions are in use on the Colibri T20 module. Make use of the
correct tables by requesting the correct SM2 voltage of 1.8V.
This change is not backward compatible since an old driver is not able
to correctly set that value. The value 1.8V is out of range for the old
driver and will refuse to probe the device. The regulator starts with
default settings and the driver shows appropriate error messages.
On Colibri T20, the old value used to work with TPS658623 since the
driver applied a wrong voltage table too. However, the TPS658643 used
on V1.2 devices uses yet another voltage table and those broke that
pseudo-compatibility. The regulator driver now has the correct voltage
table for both regulator versions and those the correct voltage can be
used in the device tree.
Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-by: Thierry Reding <treding@nvidia.com>
Acked-by: Mark Brown <broonie@linaro.org>
Acked-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
Diffstat (limited to 'drivers/mfd/mc13xxx-core.c')
0 files changed, 0 insertions, 0 deletions