Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 23 7月, 2015 1 次提交
    • D
      regulator: tps6586x: silence pointer-to-int-cast · a70f0d02
      由 Daniel Kurtz 提交于 
      of_regulator_match.driver_data is (void *).  tps6586x uses it to store an
anonymous enum value (those TPS6586X_ID_ values).

Later, it tries to extract the ID by casting directly to an int, which is a
no-no ([-Wpointer-to-int-cast]):

drivers/regulator/tps6586x-regulator.c: In function 'tps6586x_parse_regulator_dt':
drivers/regulator/tps6586x-regulator.c:430:8: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
   id = (int)tps6586x_matches[i].driver_data;
        ^

Instead of casting to int, uintptr_t is better suited for receiving and
comparing integers extracted from void *.  This is especially true on
64-bit systems where sizeof(void *) != sizeof(int).
Signed-off-by: NDaniel Kurtz <djkurtz@chromium.org>
Signed-off-by: NMark Brown <broonie@kernel.org>
      a70f0d02
  3. 20 10月, 2014 1 次提交
  5. 06 6月, 2014 1 次提交
  7. 27 5月, 2014 1 次提交
  9. 26 5月, 2014 2 次提交
  11. 13 3月, 2014 1 次提交
  13. 20 2月, 2014 1 次提交
  15. 21 1月, 2014 1 次提交
    • S
      regulator: tps6586x: Add and use correct voltage table · 844a4f0d
      由 Stefan Agner 提交于 
      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: NStefan Agner <stefan@agner.ch>
Reviewed-by: NThierry Reding <treding@nvidia.com>
Acked-by: NMark Brown <broonie@linaro.org>
Acked-by: NStephen Warren <swarren@nvidia.com>
Signed-off-by: NLee Jones <lee.jones@linaro.org>
      844a4f0d
  17. 10 10月, 2013 1 次提交
  19. 17 9月, 2013 1 次提交
  21. 24 6月, 2013 1 次提交
  23. 23 4月, 2013 1 次提交
  25. 04 3月, 2013 2 次提交
  27. 25 12月, 2012 1 次提交
  29. 28 11月, 2012 1 次提交
  31. 20 11月, 2012 3 次提交
  33. 15 11月, 2012 1 次提交
    • L
      mfd: tps6586x: move regulator dt parsing to regulator driver · 64e48160
      由 Laxman Dewangan 提交于 
      Moving regulator node parsing to regulator driver in place
of parsing it on mfd driver.
The motivation for this change are:
- MFD core driver should not depends on regulator and able
  to instantiate device without regulator.
- The API for matching regulators are in regulator core and
  it is good that regulator driver only calls this API.
- Regulator specific support should be in regulator driver only
  to ease any enhancement/modification for regulators.
- The regulator driver is now registered as mfd sub device and
  all regulator registration is done from single probe call.
Signed-off-by: NLaxman Dewangan <ldewangan@nvidia.com>
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      64e48160
  35. 06 9月, 2012 1 次提交
  37. 29 8月, 2012 1 次提交
  39. 08 8月, 2012 1 次提交
  41. 13 7月, 2012 1 次提交
  43. 08 6月, 2012 1 次提交
  45. 04 5月, 2012 1 次提交
  47. 09 4月, 2012 1 次提交
    • M
      regulator: core: Use a struct to pass in regulator runtime configuration · c172708d
      由 Mark Brown 提交于 
      Rather than adding new arguments to regulator_register() every time we
want to add a new bit of dynamic information at runtime change the function
to take these via a struct. By doing this we avoid needing to do further
changes like the recent addition of device tree support which required each
regulator driver to be updated to take an additional parameter.

The regulator_desc which should (mostly) be static data is still passed
separately as most drivers are able to configure this statically at build
time.
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      c172708d
  49. 01 4月, 2012 3 次提交
  51. 26 3月, 2012 1 次提交
  53. 12 3月, 2012 1 次提交
  55. 24 11月, 2011 1 次提交
  57. 01 11月, 2011 1 次提交
  59. 29 8月, 2011 1 次提交
  61. 12 1月, 2011 1 次提交
  63. 09 12月, 2010 3 次提交