From: Chris Leech <christopher.leech@linux.intel.com>
To: linux-input@vger.kernel.org
Cc: Joonyoung Shim <jy0922.shim@samsung.com>
Subject: [PATCH 4/5] qt602240_ts: add optional hooks for board specific reset logic
Date: Tue, 16 Nov 2010 12:42:06 -0800 [thread overview]
Message-ID: <20101116204206.28796.34520.stgit@localhost6.localdomain6> (raw)
In-Reply-To: <20101116203914.28796.23141.stgit@localhost6.localdomain6>
Hooks for board specific setup and tear-down, to be used if the controllers
reset is wired to a GPIO pin.
Signed-off-by: Chris Leech <christopher.leech@linux.intel.com>
---
drivers/input/touchscreen/qt602240_ts.c | 7 +++++++
include/linux/i2c/qt602240_ts.h | 4 ++++
2 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/drivers/input/touchscreen/qt602240_ts.c b/drivers/input/touchscreen/qt602240_ts.c
index 11055ec..efe975e 100644
--- a/drivers/input/touchscreen/qt602240_ts.c
+++ b/drivers/input/touchscreen/qt602240_ts.c
@@ -1307,6 +1307,11 @@ static int __devinit qt602240_probe(struct i2c_client *client,
i2c_set_clientdata(client, data);
+ if (data->pdata->hw_setup) {
+ error = data->pdata->hw_setup(client);
+ if (error)
+ goto err_free_object;
+ }
error = qt602240_initialize(data);
if (error)
goto err_free_object;
@@ -1376,6 +1381,8 @@ static int __devexit qt602240_remove(struct i2c_client *client)
sysfs_remove_group(&client->dev.kobj, &qt602240_attr_group);
free_irq(data->irq, data);
input_unregister_device(data->input_dev);
+ if (data->pdata->hw_teardown)
+ data->pdata->hw_teardown(client);
kfree(data->object_table);
kfree(data);
diff --git a/include/linux/i2c/qt602240_ts.h b/include/linux/i2c/qt602240_ts.h
index d2aa1b6..764dd45 100644
--- a/include/linux/i2c/qt602240_ts.h
+++ b/include/linux/i2c/qt602240_ts.h
@@ -41,6 +41,10 @@ struct qt602240_platform_data {
* platform_data).
*/
unsigned char trust_nvm;
+
+ /* Board-specific HW hooks; NULL if not needed */
+ int (*hw_setup) (struct i2c_client *client);
+ void (*hw_teardown) (struct i2c_client *client);
};
#endif /* __LINUX_QT602240_TS_H */
next prev parent reply other threads:[~2010-11-16 20:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 20:41 [PATCH 0/4] qt602240_ts changes for Intel mid platform Chris Leech
2010-11-16 20:41 ` [PATCH 1/5] qt602240_ts: fix wrong sizeof in object table allocation Chris Leech
2010-11-18 11:16 ` Joonyoung Shim
2010-11-18 11:30 ` Joonyoung Shim
2010-11-16 20:41 ` [PATCH 2/5] qt602240_ts: move clearing of pending interrupt closer to request_threaded_irq Chris Leech
2010-11-18 12:53 ` Joonyoung Shim
2010-11-18 19:29 ` Chris Leech
2010-11-18 22:54 ` Dmitry Torokhov
2010-11-16 20:42 ` [PATCH 3/5] qt602240_ts: Trust factory configuration of touchscreen Chris Leech
2010-11-18 13:09 ` Joonyoung Shim
2010-11-18 19:41 ` Chris Leech
2010-11-16 20:42 ` Chris Leech [this message]
2010-11-18 11:32 ` [PATCH 4/5] qt602240_ts: add optional hooks for board specific reset logic Joonyoung Shim
2010-11-18 19:46 ` Chris Leech
2010-11-16 20:42 ` [PATCH 5/5] qt602240_ts: add mXT224 identifier to id_table, to match Intel mid firmware identifier Chris Leech
2010-11-18 11:34 ` Joonyoung Shim
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=20101116204206.28796.34520.stgit@localhost6.localdomain6 \
--to=christopher.leech@linux.intel.com \
--cc=jy0922.shim@samsung.com \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).