On Fri, Mar 31, 2017 at 12:15:34PM -0400, Damien Riegel wrote: > The driver uses a hardcoded value for the register, so the parameter set > in the device tree is not actually used. > > Cc: Rob Herring <robh+dt@xxxxxxxxxx> > Cc: Mark Rutland <mark.rutland@xxxxxxx> > Signed-off-by: Damien Riegel <damien.riegel@xxxxxxxxxxxxxxxxxxxx> > --- > Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.txt | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.txt b/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.txt > index 4ed467b1e402..86ce95fc6cf8 100644 > --- a/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.txt > +++ b/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.txt > @@ -12,7 +12,8 @@ PROPERTIES > - reg: > Usage: required > Value type: <prop-encoded-array> > - Definition: address of vibration control register > + Definition: address of vibration control register. This value is > + actually ignored and hardcoded in the driver to value 0x4a I do not think we need to commit that the value is hard coded, it is implementation detail of current version of Linux driver, whereas DT bindings should be independent of OS as much as reasonably possible. Also, I think you can change the code to actually read and use it from DT to support your other device use case. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
