From: Frank Li <Frank.li@nxp.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Luwei Zhou <b45643@freescale.com>,
Vipul Kumar <vipul_kumar@mentor.com>,
Dong Aisheng <aisheng.dong@nxp.com>,
"open list:INPUT (KEYBOARD, MOUSE, JOYSTICK,
TOUCHSCREEN)..." <linux-input@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH 1/1] input: mma8450: Add chip ID check in probe
Date: Mon, 16 Dec 2024 11:30:15 -0500 [thread overview]
Message-ID: <Z2BVlyV8o1dkBUq2@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <bzzzezoon5u5pufpbkn3fnm2dtbrzatx4w4tbdstcdmowvfzzn@cplbmxtgmu6z>
On Sat, Dec 14, 2024 at 12:02:56AM +0100, Uwe Kleine-König wrote:
> Hello Frank,
>
> On Fri, Dec 13, 2024 at 05:23:09PM -0500, Frank Li wrote:
> > From: Luwei Zhou <b45643@freescale.com>
> >
> > Prevent continuous polling error logs by adding a chip ID check in the
> > probe function. This ensures the driver only proceeds when the mma8450 is
> > present, avoiding issues in scenarios like missing add-on cards.
> >
> > Signed-off-by: Luwei Zhou <b45643@freescale.com>
> > Signed-off-by: Fugang Duan <B38611@freescale.com>
> > Signed-off-by: Vipul Kumar <vipul_kumar@mentor.com>
> > Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
> > drivers/input/misc/mma8450.c | 16 +++++++++++++++-
> > 1 file changed, 15 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/input/misc/mma8450.c b/drivers/input/misc/mma8450.c
> > index 08412239b8e69..da941748ed29b 100644
> > --- a/drivers/input/misc/mma8450.c
> > +++ b/drivers/input/misc/mma8450.c
> > @@ -38,6 +38,8 @@
> >
> > #define MMA8450_CTRL_REG1 0x38
> > #define MMA8450_CTRL_REG2 0x39
> > +#define MMA8450_ID 0xc6
> > +#define MMA8450_WHO_AM_I 0x0f
> >
> > static int mma8450_read(struct i2c_client *c, unsigned int off)
> > {
> > @@ -148,8 +150,20 @@ static void mma8450_close(struct input_dev *input)
> > */
> > static int mma8450_probe(struct i2c_client *c)
> > {
> > + struct i2c_adapter *adapter = to_i2c_adapter(c->dev.parent);
>
> + struct i2c_adapter *adapter = c->adapter;
>
> > struct input_dev *input;
> > - int err;
> > + int err, client_id;
> > +
> > + err = i2c_check_functionality(adapter,
> > + I2C_FUNC_SMBUS_BYTE | I2C_FUNC_SMBUS_BYTE_DATA);
> > + if (!err)
> > + return err;
>
> How unusual. I would have expected no ! here.
yes, it should be better
if (!i2c_check_functionality())
....
i2c_check_functionality() return 1 if adapter supports everything we need.
Frank
>
> > + client_id = i2c_smbus_read_byte_data(c, MMA8450_WHO_AM_I);
> > + if (client_id != MMA8450_ID)
> > + return dev_err_probe(&c->dev, -EINVAL,
> > + "read chip ID 0x%x is not equal to 0x%x!\n",
> > + client_id, MMA8450_ID);
>
> Given that here you emit an error message, maybe add an error message
> above, too?
>
> > input = devm_input_allocate_device(&c->dev);
> > if (!input)
>
> Best regards
> Uwe
next prev parent reply other threads:[~2024-12-16 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 22:23 [PATCH 1/1] input: mma8450: Add chip ID check in probe Frank Li
2024-12-13 23:02 ` Uwe Kleine-König
2024-12-16 16:30 ` Frank Li [this message]
2024-12-16 17:14 ` 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=Z2BVlyV8o1dkBUq2@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=b45643@freescale.com \
--cc=dmitry.torokhov@gmail.com \
--cc=imx@lists.linux.dev \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vipul_kumar@mentor.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