From: Guenter Roeck <linux@roeck-us.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, KT Liao <ktalex.liao@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: elan_i2c - check if device is there before really probing
Date: Mon, 8 May 2017 14:44:25 -0700 [thread overview]
Message-ID: <20170508214425.GA27206@roeck-us.net> (raw)
In-Reply-To: <20170508211031.GA31381@dtor-ws>
On Mon, May 08, 2017 at 02:10:31PM -0700, Dmitry Torokhov wrote:
> On Wed, May 03, 2017 at 11:42:54PM -0700, Guenter Roeck wrote:
> > On 05/03/2017 11:29 PM, Dmitry Torokhov wrote:
> > >Before trying to properly initialize the touchpad and generate bunch of
> > >errors, let's first see it there is anything at the given address. If we
> > >get error, fail silently with -ENXIO.
> > >
> > >Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > >---
> > > drivers/input/mouse/elan_i2c_core.c | 9 +++++++++
> > > 1 file changed, 9 insertions(+)
> > >
> > >diff --git a/drivers/input/mouse/elan_i2c_core.c b/drivers/input/mouse/elan_i2c_core.c
> > >index 5d3b53dd2fa2..0479730e7c5c 100644
> > >--- a/drivers/input/mouse/elan_i2c_core.c
> > >+++ b/drivers/input/mouse/elan_i2c_core.c
> > >@@ -1040,6 +1040,7 @@ static int elan_probe(struct i2c_client *client,
> > > const struct elan_transport_ops *transport_ops;
> > > struct device *dev = &client->dev;
> > > struct elan_tp_data *data;
> > >+ union i2c_smbus_data dummy;
> > > unsigned long irqflags;
> > > int error;
> > >
> > >@@ -1091,6 +1092,14 @@ static int elan_probe(struct i2c_client *client,
> > > return error;
> > > }
> > >
> > >+ /* Make sure there is something at this address */
> > >+ error = i2c_smbus_xfer(client->adapter, client->addr, 0,
> > >+ I2C_SMBUS_READ, 0, I2C_SMBUS_BYTE, &dummy);
> >
> > Can't you just call i2c_smbus_read_byte_data(client, 0); and check if it returns
> > an error ?
>
> Are we guaranteed to get a result from command "0"? I am not sure, and
> looking at least at i2c_smbus_xfer_emulated() I2C_SMBUS_READ with
> I2C_SMBUS_BYTE modifier works differently form
> I2C_SMBUS_READ/I2C_SMBUS_BYTE_DATA (the former uses a single i2c message
> vs 2 for the latter).
>
> Also the form above is what i2c core uses to do detection when adapter
> does not implement I2C_SMBUS_QUICK, so I'd rather leave it as it was.
>
How about i2c_smbus_read_byte() ?
status = i2c_smbus_xfer(client->adapter, client->addr, client->flags,
I2C_SMBUS_READ, 0,
I2C_SMBUS_BYTE, &data);
return (status < 0) ? status : data.byte;
Guenter
next prev parent reply other threads:[~2017-05-08 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 6:29 Dmitry Torokhov
2017-05-04 6:42 ` Guenter Roeck
2017-05-08 21:10 ` Dmitry Torokhov
2017-05-08 21:44 ` Guenter Roeck [this message]
2017-05-08 22:47 ` 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=20170508214425.GA27206@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dmitry.torokhov@gmail.com \
--cc=ktalex.liao@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®