From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Simon Budig <simon.budig@kernelconcepts.de>
Cc: "Lothar Waßmann" <LW@KARO-electronics.de>,
"Henrik Rydberg" <rydberg@euromail.se>,
"Grant Likely" <grant.likely@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Fugang Duan" <B38611@freescale.com>,
"Jingoo Han" <jg1.han@samsung.com>,
linux-input@vger.kernel.org, kernel-janitors@vger.kernel.org,
"Robert Wörle" <rwoerle@mibtec.de>
Subject: Re: [patch] Input: edt-ft5x06 - fix an i2c write for M09 support
Date: Sun, 08 Jun 2014 05:36:41 +0000 [thread overview]
Message-ID: <20140608053641.GB24310@core.coreip.homeip.net> (raw)
In-Reply-To: <5393A60C.8040207@kernelconcepts.de>
On Sun, Jun 08, 2014 at 01:53:48AM +0200, Simon Budig wrote:
> Hi all.
>
> I received notice from Robert Wörle who spotted a bug in the ft5x06
> driver (M09 support) which can result in bogus values being written into
> the configuration registers.
>
> Paul wrote:
> > I think i found the problem, as the driver sends 3 bytes instead of 2
> > when accessing a register on the M09 firmware.
> > Therefore , writing to gain seems to overflow into the offset register.
> >
> > This seems to be even in the lastet upstream driver so i created a patch
> > for this driver which you find attached.
> >
> > @Simon Budig
> >
> > Find attached a patch to fix this edt driver bug, feel free to comment ,
> > test and commit upstream ;-)
>
> He is right, his fix is correct. Please include his patch into the
> repository.
>
> Acked-By: Simon Budig <simon.budig@kernelconcepts.de>
Applied, thank you.
>
> Thanks,
> Simon
> --
> Simon Budig kernel concepts GmbH
> simon.budig@kernelconcepts.de Sieghuetter Hauptweg 48
> +49-271-771091-17 D-57072 Siegen
>
> From 36b9ac0e8206efefc8795c925b0f3b63ab29fd08 Mon Sep 17 00:00:00 2001
> From: Robert Woerle <robert@linuxdevelopment.de>
> Date: Wed, 28 May 2014 13:22:09 +0200
> Subject: [PATCH] Input: edt-ft5x06 - fix i2c writes to 2 bytes on M09
> firmware
>
> Signed-off-by: Robert Woerle <robert@linuxdevelopment.de>
> ---
> drivers/input/touchscreen/edt-ft5x06.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/touchscreen/edt-ft5x06.c b/drivers/input/touchscreen/edt-ft5x06.c
> index f8815be..d4f3399 100644
> --- a/drivers/input/touchscreen/edt-ft5x06.c
> +++ b/drivers/input/touchscreen/edt-ft5x06.c
> @@ -271,7 +271,7 @@ static int edt_ft5x06_register_write(struct edt_ft5x06_ts_data *tsdata,
> wrbuf[0] = addr;
> wrbuf[1] = value;
>
> - return edt_ft5x06_ts_readwrite(tsdata->client, 3,
> + return edt_ft5x06_ts_readwrite(tsdata->client, 2,
> wrbuf, 0, NULL);
>
> default:
> --
> 1.7.9.5
>
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-06-08 5:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 23:53 [patch] Input: edt-ft5x06 - fix an i2c write for M09 support Simon Budig
2014-06-08 5:36 ` Dmitry Torokhov [this message]
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=20140608053641.GB24310@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=B38611@freescale.com \
--cc=LW@KARO-electronics.de \
--cc=grant.likely@linaro.org \
--cc=jg1.han@samsung.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rwoerle@mibtec.de \
--cc=rydberg@euromail.se \
--cc=simon.budig@kernelconcepts.de \
/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