On Freitag, 12. April 2019 17:06:23 CEST Luca Weiss wrote: > Provide a simple driver for GPIO controllable vibrators. > It will be used by the Fairphone 2. > > Signed-off-by: Luca Weiss <[email protected]> > --- > .../bindings/input/gpio-vibrator.txt | 20 +++++++++++++++++++ > 1 file changed, 20 insertions(+) > create mode 100644 > Documentation/devicetree/bindings/input/gpio-vibrator.txt > > diff --git a/Documentation/devicetree/bindings/input/gpio-vibrator.txt > b/Documentation/devicetree/bindings/input/gpio-vibrator.txt new file mode > 100644 > index 000000000000..93e5a8e7622d > --- /dev/null > +++ b/Documentation/devicetree/bindings/input/gpio-vibrator.txt > @@ -0,0 +1,20 @@ > +* GPIO vibrator device tree bindings > + > +Registers a GPIO device as vibrator, where the vibration motor just has the > +capability to turn on or off. If the device is connected to a pwm, you > should +use the pwm-vibrator driver instead. > + > +Required properties: > +- compatible: should contain "gpio-vibrator" > +- enable-gpios: Should contain a GPIO handle > + > +Optional properties: > +- vcc-supply: Phandle for the regulator supplying power > + > +Example from Fairphone 2: > + > +vibrator { > + compatible = "gpio-vibrator"; > + enable-gpios = <&msmgpio 86 GPIO_ACTIVE_HIGH>; > + vcc-supply = <&pm8941_l18>; > +};
I see that the yaml based device tree binding docs seem to be the new hotness? Is there any "policy" / preference about new drivers? Luca
