regulator: dt-bindings: pwm-regulator: Add missing type for "pwm-dutycycle-unit"
Subsystems (2)
Rob Herring
maintainerPATCH 1/1 regulator: dt-bindings: pwm-regulator: Add missing type for "pwm-dutycycle-unit"
"pwm-dutycycle-unit" is missing a type, add it.
--- Documentation/devicetree/bindings/regulator/pwm-regulator.yaml | 1 + 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/regulator/pwm-regulator.yaml +1 -0
@@ -64,6 +64,7 @@ properties: defined, <100> is assumed, meaning that pwm-dutycycle-range contains values expressed in percent. + $ref: /schemas/types.yaml#/definitions/uint32 default: 100 pwm-dutycycle-range:
Signature · 1 line
2.39.2
Quoted 6 lines · Rob Herring
"pwm-dutycycle-unit" is missing a type, add it.
Signed-off-by Rob Herring <[email protected]>--- Documentation/devicetree/bindings/regulator/pwm-regulator.yaml | 1 + 1 file changed, 1 insertion(+)
Quoted 3 lines · Rob Herring
"pwm-dutycycle-unit" is missing a type, add it.
Signed-off-by Rob Herring <[email protected]>
Cheers,
Conor.
Mark Brown
maintainerQuoted 3 lines · Rob Herring
"pwm-dutycycle-unit" is missing a type, add it.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: dt-bindings: pwm-regulator: Add missing type for "pwm-dutycycle-unit"
commit: 2b026eabc3152592be75b7d7e73e9536b9eeb794
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark