From: Christopher Heiny <cheiny@synaptics.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jean Delvare <khali@linux-fr.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Input <linux-input@vger.kernel.org>,
Allie Xiong <axiong@synaptics.com>,
William Manson <WManson@synaptics.com>,
Joerie de Gram <j.de.gram@gmail.com>,
Linus Walleij <linus.walleij@stericsson.com>,
Naveen Kumar Gaddipati <naveen.gaddipati@stericsson.com>
Subject: Re: [PATCH 1/3] input/touchscreen: Synaptics RMI4 Touchscreen Driver
Date: Wed, 30 Mar 2011 11:36:04 -0700 [thread overview]
Message-ID: <4D937814.5010604@synaptics.com> (raw)
In-Reply-To: <20110330080223.GB2232@pengutronix.de>
On 03/30/2011 01:02 AM, Wolfram Sang wrote:
> * PGP Signed by an unknown key: 03/30/2011 at 12:02:23 AM
> Hi,
>
>> + retval = rmi_register_sensor(&instancedata->rmiphysdrvr, platformdata->perfunctiondata);
>> + if (retval) {
>> + dev_err(&client->dev, "%s: Failed to Register %s sensor drivers\n",
>> + __func__, instancedata->rmiphysdrvr.name);
>> + i2c_set_clientdata(client, NULL);
>
> I originally just wanted to say that this line can be removed. Then I
> remembered that I already sent a patch for a similar driver in staging
> (dc7b202a4ee6cb686e2bbef80c84443f43ec91bd). The staging driver looks in
> a better shape to me. Do you know about it?
Hi Wolfram,
That call is required in order to register the sensor device on the rmi
bus, so that the rmi functions can be associated with it. Without that
call, the driver will not function.
I'm afraid I can't locate the commit you specified. I do find a driver
in staging/ste_rmi4/synaptics_i2c_rmi4.[ch] - is that the one? If not
which, tree/branch can I find it in?
Thanks,
Chris
next prev parent reply other threads:[~2011-03-30 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 0:50 [PATCH 0/3] input/touchscreen: Synaptics RMI4 Touchscreen Driver Christopher Heiny
2011-03-30 0:50 ` [PATCH 1/3] " Christopher Heiny
2011-03-30 8:02 ` Wolfram Sang
2011-03-30 18:36 ` Christopher Heiny [this message]
2011-03-30 19:44 ` Wolfram Sang
2011-03-30 21:08 ` Christopher Heiny
2011-03-30 11:46 ` Joerie de Gram
2011-03-30 14:00 ` Christopher Heiny
2011-03-30 0:50 ` [PATCH 2/3] " Christopher Heiny
2011-03-30 0:50 ` [PATCH 3/3] " 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=4D937814.5010604@synaptics.com \
--to=cheiny@synaptics.com \
--cc=WManson@synaptics.com \
--cc=axiong@synaptics.com \
--cc=dmitry.torokhov@gmail.com \
--cc=j.de.gram@gmail.com \
--cc=khali@linux-fr.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.gaddipati@stericsson.com \
--cc=w.sang@pengutronix.de \
/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