From: Martin Kepplinger <martin.kepplinger@ginzinger.com>
To: Rob Herring <robh@kernel.org>, <dmitry.torokhov@gmail.com>
Cc: <simon.budig@kernelconcepts.de>,
<daniel.wagener@kernelconcepts.de>, <mchehab@kernel.org>,
<linux-input@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
Schoefegger Stefan <stefan.schoefegger@ginzinger.com>,
Manfred Schlaegl <manfred.schlaegl@ginzinger.com>
Subject: Re: [PATCH] input: edt-ft5x06: increase allowed data range for threshold parameter
Date: Wed, 17 May 2017 14:39:16 +0200 [thread overview]
Message-ID: <33877b30-e903-c0ce-37d7-ec344a03da58@ginzinger.com> (raw)
In-Reply-To: <2a2d6377-1d3c-8639-0f28-d9519965296c@ginzinger.com>
On 2017-05-11 10:32, Martin Kepplinger wrote:
> On 2017-05-08 18:11, Rob Herring wrote:
>> On Tue, May 02, 2017 at 05:00:59PM +0200, Martin Kepplinger wrote:
>>> The datasheet and application note does not mention an allowed range for
>>> the M09_REGISTER_THRESHOLD parameter. One of our customers needs to set
>>> lower values than 20 and they seem to work just fine on EDT EP0xx0M09 with
>>> T5x06 touch.
>>>
>>> So, lacking a known lower limit, we increase the range for thresholds,
>>> and set the lower limit to 0. The documentation is updated accordingly.
>>>
>>> Signed-off-by: Schoefegger Stefan <stefan.schoefegger@ginzinger.com>
>>> Signed-off-by: Manfred Schlaegl <manfred.schlaegl@ginzinger.com>
>>> Signed-off-by: Martin Kepplinger <martin.kepplinger@ginzinger.com>
>>> ---
>>> Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt | 2 +-
>>> Documentation/input/devices/edt-ft5x06.rst | 2 +-
>>> drivers/input/touchscreen/edt-ft5x06.c | 2 +-
>>> 3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> Acked-by: Rob Herring <robh@kernel.org>
>>
>
> Dmitry, any objections or thoughts?
Hey Dmitry, this still applies to today's -next and wouldn't take too
long for you to review :)
thanks
martin
next prev parent reply other threads:[~2017-05-17 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 15:00 Martin Kepplinger
2017-05-08 16:11 ` Rob Herring
2017-05-11 8:32 ` Martin Kepplinger
2017-05-17 12:39 ` Martin Kepplinger [this message]
2017-05-23 0:20 ` Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33877b30-e903-c0ce-37d7-ec344a03da58@ginzinger.com \
--to=martin.kepplinger@ginzinger.com \
--cc=daniel.wagener@kernelconcepts.de \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred.schlaegl@ginzinger.com \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=simon.budig@kernelconcepts.de \
--cc=stefan.schoefegger@ginzinger.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome