From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Dave Wang <dave.wang@emc.com.tw>
Cc: Linux-input@vger.kernel.org, Linux-kernel@vger.kernel.org,
phoenix@emc.com.tw, josh.chen@emc.com.tw, jingle.wu@emc.com.tw,
kai.heng.feng@canonical.com
Subject: Re: [PATCH 1/3] Input: elan_i2c - Do no operation for elan_smbus_set_mode function
Date: Tue, 21 Jul 2020 09:12:36 -0700 [thread overview]
Message-ID: <20200721161236.GI1665100@dtor-ws> (raw)
In-Reply-To: <20191209111107.32239-1-dave.wang@emc.com.tw>
Hi Dave,
On Mon, Dec 09, 2019 at 06:11:07AM -0500, Dave Wang wrote:
> Some touchpads might get error while triggerring the set_mode command
> in SMBus interface. Do no operation for elan_smbus_set_mode function.
Are there devices that do not trigger errors? How do we put SMbus
devices into low power mode?
>
> Signed-off-by: Dave Wang <dave.wang@emc.com.tw>
> ---
> drivers/input/mouse/elan_i2c_smbus.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/input/mouse/elan_i2c_smbus.c b/drivers/input/mouse/elan_i2c_smbus.c
> index 8c3185d54c73..bcb9ec4a7a6b 100644
> --- a/drivers/input/mouse/elan_i2c_smbus.c
> +++ b/drivers/input/mouse/elan_i2c_smbus.c
> @@ -84,10 +84,7 @@ static int elan_smbus_initialize(struct i2c_client *client)
>
> static int elan_smbus_set_mode(struct i2c_client *client, u8 mode)
> {
> - u8 cmd[4] = { 0x00, 0x07, 0x00, mode };
> -
> - return i2c_smbus_write_block_data(client, ETP_SMBUS_IAP_CMD,
> - sizeof(cmd), cmd);
> + return 0; /* A no-op */
> }
>
> static int elan_smbus_sleep_control(struct i2c_client *client, bool sleep)
> --
> 2.17.1
>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2020-07-21 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 11:11 [PATCH 1/3] Input: elan_i2c - Do no operation for elan_smbus_set_mode function Dave Wang
2020-07-21 16:12 ` Dmitry Torokhov [this message]
2020-07-22 2:19 ` Dave.Wang
2020-07-22 2:55 ` Dave.Wang
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=20200721161236.GI1665100@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=Linux-input@vger.kernel.org \
--cc=Linux-kernel@vger.kernel.org \
--cc=dave.wang@emc.com.tw \
--cc=jingle.wu@emc.com.tw \
--cc=josh.chen@emc.com.tw \
--cc=kai.heng.feng@canonical.com \
--cc=phoenix@emc.com.tw \
/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;
as well as URLs for NNTP newsgroup(s).