* [GIT PULL] regulator updates for v4.7
@ 2016-05-16 12:27 Mark Brown
2016-05-17 2:38 ` Linus Torvalds
0 siblings, 1 reply; 4+ messages in thread
From: Mark Brown @ 2016-05-16 12:27 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, Liam Girdwood
[-- Attachment #1: Type: text/plain, Size: 11997 bytes --]
The following changes since commit 9689dab30a52f5df313771e07206d7b3d8ca44f7:
Merge remote-tracking branches 'regulator/fix/axp20x', 'regulator/fix/da9063', 'regulator/fix/gpio' and 'regulator/fix/s2mps11' into regulator-linus (2016-05-13 11:11:08 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-v4.7
for you to fetch changes up to 4f38c566a0967ce9291537ba04891391681a7661:
Merge remote-tracking branches 'regulator/topic/tps6524x' and 'regulator/topic/twl' into regulator-next (2016-05-13 14:23:49 +0100)
----------------------------------------------------------------
regulator: Updates for v4.7
A few core enhancements to deal with some of the slightly more
complicated edge cases that have started cropping up in systems, both
new ones and old ones that people started worrying about upstream, but
otherwise a quiet release for the regulator API:
- When applying constraints at system image if we have a voltage range
specified and the regulator is currently configured outside the
bounds of that range bring the regulator to the nearest end of the
range.
- When regulators are in non-regulating bypass modes make sure that we
always use the voltage from the parent regulator.
- Support for LP873x, PV88080, PM8894 and FAN53555 chips.
----------------------------------------------------------------
Arnd Bergmann (1):
regulator: rk808: remove unused rk808_reg_ops_ranges
Boris Brezillon (3):
regulator: reorder initialization steps in regulator_register()
pwm: Introduce the pwm_args concept
regulator: pwm: Use pwm_get_args() where appropriate
Dan Carpenter (2):
regulator: lp3971: Silence uninitialized variable warning
regulator: lp3972: Silence uninitialized variable warning
Geert Uytterhoeven (1):
regulator: ti-abb: DT spelling s/#{address,size}-cell/#{address,size}-cells/
Hans de Goede (1):
regulator: axp20x: Fix axp22x ldo_io voltage ranges
Ivaylo Dimitrov (4):
regulator: twl: Make sure we have access to powerbus before trying to write to it
regulator: twl: Regulator mode should not depend on regulator enabled state
regulator: twl: Provide of_map_mode for twl4030
regulator: twl: Fix a typo in twl4030_send_pb_msg
James Ban (1):
regulator: pv88080: new regulator driver
Javier Martinez Canillas (6):
regulator: Remove unneded check for regulator supply
regulator: Try to resolve regulators supplies on registration
regulator: Rename files for Maxim PMIC drivers
regulator: s2mps11: Use module_platform_driver() instead subsys initcall
regulator: max77686: Use module_platform_driver() instead subsys initcall
MAINTAINERS: Add DT bindings to regulator framework entry
Jon Hunter (7):
regulator: Fix deadlock during regulator registration
regulator: as3722: Add bypass support for LDO6
regulator: core: Don't terminate supply resolution early
regulator: core: Clear the supply pointer if enabling fails
regulator: core: Move registration of regulator device
regulator: helpers: Ensure bypass register field matches ON value
regulator: core: Add early supply resolution for regulators
Keerthy (1):
regulator: lp873x: Add support for lp873x PMIC regulators
Krzysztof Kozlowski (3):
regulator: max8997/max77802: Fix misspelled Samsung address
regulator: s2mps11: Set default ramp delay for S2MPS11 LDOs
regulator: max77686: Configure enable time to properly handle regulator enable
Laxman Dewangan (6):
regulator: pwm: Prints error number along with detail
regulator: pwm: Try to avoid voltage error in duty cycle calculation
regulator: max8973: add DT binding details for junction warn temp
regulator: max8973: add support for junction thermal warning
regulator: max77620: Add details of device specific ramp rate setting
regulator: max77620: Add support for device specific ramp rate setting
Luis de Bethencourt (2):
regulator: add missing descriptions in regulator_desc
regulator: add missing description for set_over_current_protection
Maarten ter Huurne (4):
regulator: act8865: Remove redundant dev lookups
regulator: act8865: Remove "too many regulators" error handler
regulator: act8865: Pass of_node via act8865_regulator_data
regulator: act8865: Configure register access for act8600
Mark Brown (26):
regulator: core: Always flag voltage constraints as appliable
regulator: core: Ensure we are at least in bounds for our constraints
regulator: core: Log when we bring constraints into range
regulator: of: Don't flag voltage change as possible for exact voltages
regulator: Deprecate regulator_can_change_voltage()
regulator: core: Use parent voltage from the supply when bypassed
regulator: core: Fix locking of GPIO list on free
regulator: tps6524x: Fix broken use of spi_dev_get()
regulator: core: Use a bitfield for continuous_voltage_range
Merge branch 'topic/sysfs-init' of git://git.kernel.org/.../broonie/regulator into regulator-supply
Merge branch 'topic/bypass' of git://git.kernel.org/.../broonie/regulator into regulator-supply
Merge branch 'fix/axp20x' of git://git.kernel.org/.../broonie/regulator into regulator-axp20x
Merge branch 'for-4.7/pwm-regulator' of git://git.kernel.org/.../thierry.reding/linux-pwm into regulator-pwm
Merge tag 'regulator-fix-v4.6-rc7' into regulator-linus
Merge remote-tracking branch 'regulator/fix/bypass' into regulator-linus
Merge remote-tracking branch 'regulator/fix/core' into regulator-linus
Merge remote-tracking branches 'regulator/fix/constrain' and 'regulator/fix/defer' into regulator-linus
Merge remote-tracking branch 'regulator/topic/bypass' into regulator-next
Merge remote-tracking branch 'regulator/topic/core' into regulator-next
Merge remote-tracking branch 'regulator/topic/supply' into regulator-next
Merge remote-tracking branches 'regulator/topic/abb', 'regulator/topic/act8865', 'regulator/topic/as3722' and 'regulator/topic/axp20x' into regulator-next
Merge remote-tracking branches 'regulator/topic/can-change', 'regulator/topic/constrain', 'regulator/topic/debugfs' and 'regulator/topic/doc' into regulator-next
Merge remote-tracking branches 'regulator/topic/fan53555', 'regulator/topic/lp3971', 'regulator/topic/lp3972', 'regulator/topic/lp873x' and 'regulator/topic/max77620' into regulator-next
Merge remote-tracking branches 'regulator/topic/max77686', 'regulator/topic/max8973', 'regulator/topic/maxim', 'regulator/topic/palmas' and 'regulator/topic/pv88080' into regulator-next
Merge remote-tracking branches 'regulator/topic/pwm', 'regulator/topic/qcom-spmi', 'regulator/topic/rk808' and 'regulator/topic/s2mps11' into regulator-next
Merge remote-tracking branches 'regulator/topic/tps6524x' and 'regulator/topic/twl' into regulator-next
Nishanth Menon (5):
regulator: tps65917/palmas: Add bypass "On" value
regulator: tps65917/palmas: Simplify multiple dereference of ddata->palmas_matches[idx]
regulator: tps65917/palmas: Simplify multiple dereference of pdata->reg_init[idx]
regulator: tps65917/palmas: Handle possible memory allocation failure
regulator: tps65917/palmas: Simplify multiple dereference of match->of_node
Richard Fitzgerald (1):
regulator: core: Add debugfs to show constraint flags
Stephen Boyd (5):
regulator: qcom_spmi: Add support for pm8994
regulator: qcom_spmi: Keep trying to add regulators if read fails
regulator: qcom_spmi: Add slewing delays for all SMPS types
regulator: qcom_spmi: Only use selector based regulator ops
regulator: qcom_spmi: Always return a selector when asked
Tero Kristo (1):
regulator: core: remove lockdep assert from suspend_prepare
Thierry Reding (2):
regulator: as3722: Constify regulator ops
Merge branch 'for-4.7/pwm-args' into for-4.7/pwm-regulator
Vladimir Zapolskiy (1):
regulator: core: Remove duplicate copy of active-discharge parsing
WEN Pingbo (1):
regulator: refactor valid_ops_mask checking code
Wadim Egorov (5):
regulator: fan53555: Add support for FAN53555BUC18X type
regulator: fan53555: Add support for FAN53555UC13X type
regulator: rk808: remove linear range definitions with a single range
regulator: rk808: Add rk808_reg_ops_ranges for LDO3
regulator: rk808: Migrate to regulator core's simplified DT parsing code
.../bindings/regulator/max8973-regulator.txt | 7 +
.../devicetree/bindings/regulator/pv88080.txt | 49 +++
.../bindings/regulator/qcom,spmi-regulator.txt | 37 ++
.../bindings/regulator/regulator-max77620.txt | 22 ++
.../bindings/regulator/ti-abb-regulator.txt | 10 +-
.../bindings/regulator/twl-regulator.txt | 6 +
MAINTAINERS | 6 +-
drivers/pwm/core.c | 21 +-
drivers/pwm/pwm-clps711x.c | 2 +-
drivers/pwm/pwm-pxa.c | 2 +-
drivers/regulator/Kconfig | 17 +
drivers/regulator/Makefile | 8 +-
drivers/regulator/act8865-regulator.c | 113 ++++--
drivers/regulator/as3722-regulator.c | 65 +++-
drivers/regulator/core.c | 279 ++++++++------
drivers/regulator/fan53555.c | 24 ++
drivers/regulator/helpers.c | 2 +-
drivers/regulator/lp3971.c | 2 +-
drivers/regulator/lp3972.c | 2 +-
drivers/regulator/lp873x-regulator.c | 241 ++++++++++++
.../regulator/{max14577.c => max14577-regulator.c} | 0
drivers/regulator/max77620-regulator.c | 83 ++--
drivers/regulator/max77686-regulator.c | 17 +-
.../regulator/{max77693.c => max77693-regulator.c} | 0
drivers/regulator/max77802-regulator.c | 2 +-
drivers/regulator/max8973-regulator.c | 97 +++++
.../regulator/{max8997.c => max8997-regulator.c} | 2 +-
drivers/regulator/of_regulator.c | 6 +-
drivers/regulator/palmas-regulator.c | 67 ++--
drivers/regulator/pv88080-regulator.c | 419 +++++++++++++++++++++
drivers/regulator/pv88080-regulator.h | 92 +++++
drivers/regulator/pwm-regulator.c | 78 ++--
drivers/regulator/qcom_spmi-regulator.c | 275 +++++++++-----
drivers/regulator/rk808-regulator.c | 310 ++++++---------
drivers/regulator/s2mps11.c | 13 +-
drivers/regulator/tps6524x-regulator.c | 2 +-
drivers/regulator/twl-regulator.c | 106 +++++-
include/linux/mfd/as3722.h | 1 +
include/linux/mfd/samsung/core.h | 3 +
include/linux/pwm.h | 33 ++
include/linux/regulator/act8865.h | 2 +
include/linux/regulator/consumer.h | 4 +-
include/linux/regulator/driver.h | 7 +-
include/linux/regulator/machine.h | 1 +
include/linux/regulator/max8973-regulator.h | 5 +
45 files changed, 1960 insertions(+), 580 deletions(-)
create mode 100644 Documentation/devicetree/bindings/regulator/pv88080.txt
create mode 100644 drivers/regulator/lp873x-regulator.c
rename drivers/regulator/{max14577.c => max14577-regulator.c} (100%)
rename drivers/regulator/{max77693.c => max77693-regulator.c} (100%)
rename drivers/regulator/{max8997.c => max8997-regulator.c} (99%)
create mode 100644 drivers/regulator/pv88080-regulator.c
create mode 100644 drivers/regulator/pv88080-regulator.h
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [GIT PULL] regulator updates for v4.7
2016-05-16 12:27 [GIT PULL] regulator updates for v4.7 Mark Brown
@ 2016-05-17 2:38 ` Linus Torvalds
2016-05-17 10:18 ` Mark Brown
0 siblings, 1 reply; 4+ messages in thread
From: Linus Torvalds @ 2016-05-17 2:38 UTC (permalink / raw)
To: Mark Brown; +Cc: Linux Kernel Mailing List, Liam Girdwood
On Mon, May 16, 2016 at 5:27 AM, Mark Brown <broonie@kernel.org> wrote:
>
> Mark Brown (26):
> regulator: Deprecate regulator_can_change_voltage()
This needs to be fixed.
It causes a build warning, and it's just not acceptable. We've had
driver subsystems do this before, and then the warning stays around
for years and nothing gets done.
The warning is not just ugly, it ends up often hiding real problems
when people get used to seeing warnings during the build.
The whole "__deprecated" crap has been a bigger problem in itself than
it has ever actually solved.
So don't do it. Either remove bad interfaces or leave them alone. None
of this "let's annoy everybody else with our deprecation messages
whether they care about it or not".
Linus
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [GIT PULL] regulator updates for v4.7
2016-05-17 2:38 ` Linus Torvalds
@ 2016-05-17 10:18 ` Mark Brown
2016-05-17 15:57 ` Mark Brown
0 siblings, 1 reply; 4+ messages in thread
From: Mark Brown @ 2016-05-17 10:18 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List, Liam Girdwood
[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]
On Mon, May 16, 2016 at 07:38:23PM -0700, Linus Torvalds wrote:
> On Mon, May 16, 2016 at 5:27 AM, Mark Brown <broonie@kernel.org> wrote:
> > Mark Brown (26):
> > regulator: Deprecate regulator_can_change_voltage()
> This needs to be fixed.
> It causes a build warning, and it's just not acceptable. We've had
> driver subsystems do this before, and then the warning stays around
> for years and nothing gets done.
> The warning is not just ugly, it ends up often hiding real problems
> when people get used to seeing warnings during the build.
I agree, it's not great, I wouldn't normally do it and it's certainly
not good to just shove the annotation on there with no other action. In
this case a combination of this and pushing patches at people seems to
be working - I am expecting all the broken users to be fixed during the
merge window (-next looks OK) at which point I can send a patch to you
dropping the API.
> The whole "__deprecated" crap has been a bigger problem in itself than
> it has ever actually solved.
> So don't do it. Either remove bad interfaces or leave them alone. None
> of this "let's annoy everybody else with our deprecation messages
> whether they care about it or not".
I was also trying to remove the users via other means so I could delete
the function. The reason I added the warning was that all the users
were in the embedded graphics drivers and for whatever reason it's
historically been suprisingly difficult to get any attention on issues
there that don't show up during the build so I hoped this would help
push things along faster and avoid new attempts to use it. Like I say
something seems to have worked better this time around, though I don't
know how much of it is down to the warning of course.
I'll send a patch either deleting the interface or reverting this after
-rc1 (or earlier if the users are gone from your tree before then) if
that's OK?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [GIT PULL] regulator updates for v4.7
2016-05-17 10:18 ` Mark Brown
@ 2016-05-17 15:57 ` Mark Brown
0 siblings, 0 replies; 4+ messages in thread
From: Mark Brown @ 2016-05-17 15:57 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List, Liam Girdwood
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
On Tue, May 17, 2016 at 11:18:08AM +0100, Mark Brown wrote:
> I'll send a patch either deleting the interface or reverting this after
> -rc1 (or earlier if the users are gone from your tree before then) if
> that's OK?
Turns out the OMAP fixes aren't in -next so they shouldn't hit mainline
this time around, I'll send the revert after my next meeting.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-05-17 15:57 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-16 12:27 [GIT PULL] regulator updates for v4.7 Mark Brown
2016-05-17 2:38 ` Linus Torvalds
2016-05-17 10:18 ` Mark Brown
2016-05-17 15:57 ` Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).