From: Jean Delvare <khali@linux-fr.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Input <linux-input@vger.kernel.org>,
Christopher Heiny <cheiny@synaptics.com>,
Allie Xiong <axiong@synaptics.com>,
William Manson <wmanson@synaptics.com>,
Joerie de Gram <j.de.gram@gmail.com>
Subject: Re: [RFC PATCH 1/1] input/touchscreen: Synaptics Touchscreen Driver
Date: Sat, 29 May 2010 14:32:06 +0200 [thread overview]
Message-ID: <20100529143206.1b3343d7@hyperion.delvare> (raw)
In-Reply-To: <1275092980-29208-2-git-send-email-cheiny@synaptics.com>
Hi Christopher,
On Fri, 28 May 2010 17:29:40 -0700, Christopher Heiny wrote:
> Initial driver for Synaptics touchscreens using RMI4 protocol.
>
> Signed-off-by: William Manson <WManson@synaptics.com>
> Signed-off-by: Allie Xiong <axiong@synaptics.com>
> Signed-off-by: Christopher Heiny <cheiny@synaptics.com>
You can add:
Acked-by: Jean Delvare <khali@linux-fr.org>
for the i2c parts. I still have a few comments you might be interested
in, maybe for a future incremental patch:
> (...)
> --- /dev/null
> +++ b/drivers/input/touchscreen/rmi_i2c_gta01.c
> @@ -0,0 +1,117 @@
> (...)
> +static void
> +rmi_i2c_release(struct device *dev)
> +{
> + struct platform_device *pd = container_of(dev,
> + struct platform_device, dev);
You could use to_platform_device(dev) instead, it's more readable.
> (...)
> --- /dev/null
> +++ b/drivers/input/touchscreen/rmi_phys_i2c.c
> (...)
> +/* TODO: for multiple device support will need a per-device mutex */
This comment would be better placed below, where page_mutex is declared.
> +#define DRIVER_NAME "rmi4-i2c"
> +
> +/* TODO: for multiple device support will need a per-device device name */
This comment is confusing... you would need different names if you were
supporting different device _types_ in the same driver. But you
definitely do _not_ need different names to support several devices of
the same type in a given system.
> +#define DEVICE_NAME "rmi4-i2c"
The use of dashes in i2c device names is strongly discouraged.
Including "i2c" in these names is discouraged as well, as it is
redundant. "rmi4_ts" would be a better name IMHO.
> (...)
> +static int
> +rmi_i2c_probe(struct i2c_client *client, const struct i2c_device_id *dev_id)
> +{
> + struct instance_data *id;
> + int retval = 0;
> + int i;
> + bool found = false;
> +
> + struct rmi_i2c_data *rmii2cdata;
> + struct rmi_i2c_platformdata *platformdata;
> +
> + pr_debug("Probing i2c RMI device\n");
> +
> + /* Allocate and initialize the instance data for this client */
> + id = kzalloc(sizeof(*id) * 2, GFP_KERNEL);
I still don't get the * 2.
> (...)
> + /* cast to our struct rmi_i2c_data so we know
> + the fields (see rmi_ic2.h) */
> + rmii2cdata = ((struct rmi_i2c_data *)(client->dev.platform_data));
Explicit cast still not needed, you can just write:
rmii2cdata = client->dev.platform_data;
--
Jean Delvare
next prev parent reply other threads:[~2010-05-29 12:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 0:29 [RFC PATCH 0/1] input/touchscreen: Synaptics Touchscreen Driver Christopher Heiny
2010-05-29 0:29 ` [RFC PATCH 1/1] " Christopher Heiny
2010-05-29 12:32 ` Jean Delvare [this message]
2010-05-29 20:34 ` Henrik Rydberg
2010-05-29 7:54 ` [RFC PATCH 0/1] " Henrik Rydberg
2010-05-29 10:01 ` Jean Delvare
2010-05-29 14:48 ` Henrik Rydberg
-- strict thread matches above, loose matches on Subject: below --
2010-03-23 2:07 Christopher Heiny
2010-03-23 2:07 ` [RFC PATCH 1/1] " Christopher Heiny
2010-04-02 12:50 ` Jean Delvare
2010-04-05 23:04 ` Christopher Heiny
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=20100529143206.1b3343d7@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=axiong@synaptics.com \
--cc=cheiny@synaptics.com \
--cc=dmitry.torokhov@gmail.com \
--cc=j.de.gram@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wmanson@synaptics.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;
as well as URLs for NNTP newsgroup(s).