Hi Jens,

On Fri, Mar 13, 2015 at 2:56 AM, Jens Thiele <[email protected]> wrote:
> Julian Calaby <[email protected]> writes:
>
>>>         Modified   
>>> Documentation/devicetree/bindings/input/touchscreen/sun4i.txt
>>> diff --git a/Documentation/devicetree/bindings/input/touchscreen/sun4i.txt 
>>> b/Documentation/devicetree/bindings/input/touchscreen/sun4i.txt
>>> index aef5779..b4ea9c4 100644
>>> --- a/Documentation/devicetree/bindings/input/touchscreen/sun4i.txt
>>> +++ b/Documentation/devicetree/bindings/input/touchscreen/sun4i.txt
>>> @@ -7,9 +7,13 @@ Required properties:
>>>   - interrupts: interrupt to which the chip is connected
>>>
>>>  Optional properties:
>>> - - allwinner,ts-attached: boolean indicating that an actual touchscreen is
>>> -                         attached to the controller
>>> -
>>> + - allwinner,ts-attached        : boolean indicating that an actual 
>>> touchscreen
>>> +                                  is attached to the controller
>>> + - allwinner,ts-sensitive-adjust : integer (4 bits), adjust sensitivity
>>> +                                  between 0 (least sensitive) and 15
>>> +                                  (defaults to 15)
>>> +                                  todo: added in 4.x?
>>> +                                  is there some "standard" way to track 
>>> this?
>>
>> It's called "Sensitive level" in the FEX files, so I'd recommend
>> calling it that here to help people when they're converting FEX files,
>> however the code calls it sensitive adjust so both are probably
>> equally good.
>
> the A20 manual calls it TP_SENSITIVE_ADJUST
> => changed to tp-sensitive-adjust
>
> see also patch just submitted

Why am I not surprised that Allwinner isn't consistent in naming this parameter?

Thanks,

-- 
Julian Calaby

Email: [email protected]
Profile: http://www.google.com/profiles/julian.calaby/

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to