linux/drivers/regulator, branch v3.18

Merge remote-tracking branches 'regulator/fix/max1586', 'regulator/fix/max77686', 'regulator/fix/max77693', 'regulator/fix/max77802', 'regulator/fix/max8860' and 'regulator/fix/s2mpa01' into regulator-linus

2014-11-05T14:59:25Z

Merge remote-tracking branch 'regulator/fix/core' into regulator-linus

2014-11-05T14:59:24Z

regulator: s2mpa01: zero-initialize regulator match table array

2014-11-03T15:56:16Z

The struct of_regulator_match rmatch[] is declared as a non-static local variable so the structure members are not auto-initialized. Initialize the array at declaration time to avoid the structure members values to be indeterminate and have sane defaults instead. Signed-off-by: Javier Martinez Canillas Signed-off-by: Mark Brown

regulator: max8660: zero-initialize regulator match table array

2014-11-03T15:55:53Z

regulator: max77802: zero-initialize regulator match table

2014-11-03T15:55:27Z

The struct of_regulator_match is declared as a non-static local variable so the structure members are not auto-initialized. Initialize the struct at declaration time to avoid the structure members values to be indeterminate and have sane defaults instead. Signed-off-by: Javier Martinez Canillas Signed-off-by: Mark Brown

regulator: max77686: zero-initialize regulator match table

2014-11-03T15:46:46Z

regulator: max1586: zero-initialize regulator match table array

2014-11-03T15:36:50Z

regulator: max77693: Fix use of uninitialized regulator config

2014-11-03T14:36:02Z

Driver allocated on stack struct regulator_config but didn't initialize it fully. Few fields (driver_data, ena_gpio) were left untouched. This lead to using random ena_gpio values as GPIOs for max77693 regulators. On occasion these values could match real GPIO numbers leading to interfering with other drivers and to unsuccessful enable/disable of regulator. Signed-off-by: Krzysztof Kozlowski Fixes: 80b022e29bfd ("regulator: max77693: Add max77693 regualtor driver.") Cc: Signed-off-by: Mark Brown

regulator: of: Lower the severity of the error with no container

2014-10-29T12:36:21Z

Description of regulators should generally be optional so if there is no DT node for the regulators container then we shouldn't print an error message. Lower the severity of the message to debug level (it might help someone work out what went wrong) and while we're at it say what we were looking for. Reported-by: Guenter Roeck Signed-off-by: Mark Brown

Merge remote-tracking branch 'regulator/fix/rk808' into regulator-linus

2014-10-27T11:26:24Z