Changes in v5:
* Add a fix for get_state
* Fix typo in patch #4 subject line
* Add Rob's review tag on the binding documentation patch
Changes in v4:
* Remove patches that are in LinusW linux-gpio for-next and fixes
* Rename the 'pwm-offset' property to 'marvell,pwm-offset' as suggested by
Rob Herring
The original cover letter follows (with DT property name updated).
The gpio-mvebu driver supports the PWM functionality of the GPIO block for
earlier Armada variants like XP, 370 and 38x. This series extends support to
newer Armada variants that use CP11x and AP80x, like Armada 8K and 7K.
This series adds adds the 'marvell,pwm-offset' property to DT binding.
'marvell,pwm-offset' points to the base of A/B counter registers that
determine the PWM period and duty cycle.
The existing PWM DT binding reflects an arbitrary decision to allocate the A
counter to the first GPIO block, and B counter to the other one. In attempt to
provide better future flexibility, the new 'marvell,pwm-offset' property
always points to the base address of both A/B counters. The driver code still
allocates the counters in the same way, but this might change in the future
with no change to the DT.
Tested AP806 and CP110 (both) on Armada 8040 based system.
Baruch Siach (4):
gpio: mvebu: fix pwm get_state period calculation
gpio: mvebu: add pwm support for Armada 8K/7K
arm64: dts: armada: add pwm offsets for ap/cp gpios
dt-bindings: ap806: document gpio marvell,pwm-offset property
.../arm/marvell/ap80x-system-controller.txt | 8 ++
arch/arm64/boot/dts/marvell/armada-ap80x.dtsi | 3 +
arch/arm64/boot/dts/marvell/armada-cp11x.dtsi | 10 ++
drivers/gpio/gpio-mvebu.c | 117 +++++++++++-------
4 files changed, 95 insertions(+), 43 deletions(-)
--
2.29.2
