[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YFfLUWxbfXvjYQgh@google.com>
Date: Sun, 21 Mar 2021 15:40:17 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Dmitry Osipenko <digetx@...il.com>
Cc: Nick Dyer <nick@...anahar.org>, Rob Herring <robh+dt@...nel.org>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Linus Walleij <linus.walleij@...aro.org>,
Jiada Wang <jiada_wang@...tor.com>,
linux-input@...r.kernel.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 2/3] Input: atmel_mxt_ts - support wakeup methods
On Tue, Mar 02, 2021 at 01:21:57PM +0300, Dmitry Osipenko wrote:
> According to datasheets, chips like mXT1386 have a WAKE line, it is used
> to wake the chip up from deep sleep mode before communicating with it via
> the I2C-compatible interface.
>
> If the WAKE line is connected to a GPIO line, the line must be asserted
> 25 ms before the host attempts to communicate with the controller. If the
> WAKE line is connected to the SCL pin, the controller will send a NACK on
> the first attempt to address it, the host must then retry 25 ms later.
>
> Implement the wake-up methods in the driver. Touchscreen now works
> properly on devices like Acer A500 tablet, fixing problems like this:
>
> atmel_mxt_ts 0-004c: __mxt_read_reg: i2c transfer failed (-121)
> atmel_mxt_ts 0-004c: mxt_bootloader_read: i2c recv failed (-121)
> atmel_mxt_ts 0-004c: Trying alternate bootloader address
> atmel_mxt_ts 0-004c: mxt_bootloader_read: i2c recv failed (-121)
> atmel_mxt_ts: probe of 0-004c failed with error -121
>
> Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
> Signed-off-by: Jiada Wang <jiada_wang@...tor.com>
> Signed-off-by: Dmitry Osipenko <digetx@...il.com>
Applied, thank you.
--
Dmitry
Powered by blists - more mailing lists