From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/10] Input: bu21013_ts - Request a regulator that actually exists
Date: Tue, 2 Oct 2012 09:13:16 +0100 [thread overview]
Message-ID: <1349165603-24401-4-git-send-email-lee.jones@linaro.org> (raw)
In-Reply-To: <1349165603-24401-1-git-send-email-lee.jones@linaro.org>
Currently the BU21013 Touch Screen driver requests a regulator by the
name of 'V-TOUCH', which doesn't exist anywhere in the kernel. The
correct name, as referenced in platform regulator code is 'avdd'. Here,
when we request a regulator, we use the correct name instead.
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input at vger.kernel.org
Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
drivers/input/touchscreen/bu21013_ts.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/bu21013_ts.c b/drivers/input/touchscreen/bu21013_ts.c
index 5c487d2..2fae682 100644
--- a/drivers/input/touchscreen/bu21013_ts.c
+++ b/drivers/input/touchscreen/bu21013_ts.c
@@ -461,7 +461,7 @@ static int __devinit bu21013_probe(struct i2c_client *client,
bu21013_data->chip = pdata;
bu21013_data->client = client;
- bu21013_data->regulator = regulator_get(&client->dev, "V-TOUCH");
+ bu21013_data->regulator = regulator_get(&client->dev, "avdd");
if (IS_ERR(bu21013_data->regulator)) {
dev_err(&client->dev, "regulator_get failed\n");
error = PTR_ERR(bu21013_data->regulator);
--
1.7.9.5
next prev parent reply other threads:[~2012-10-02 8:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 8:13 [PATCH 00/10] Platform data clean-up and UIB device enablement Lee Jones
2012-10-02 8:13 ` [PATCH 01/10] ARM: ux500: Move all Device Tree booting into cpu-db8500 Lee Jones
2012-10-02 8:55 ` Linus Walleij
2012-10-02 8:13 ` [PATCH 02/10] ARM: ux500: Strip out duplicate touch screen platform information Lee Jones
2012-10-02 9:07 ` Linus Walleij
2012-10-02 8:13 ` Lee Jones [this message]
2012-10-02 9:16 ` [PATCH 03/10] Input: bu21013_ts - Request a regulator that actually exists Linus Walleij
2012-10-02 8:13 ` [PATCH 04/10] Input: bu21013_ts - Move GPIO init and exit functions into the driver Lee Jones
2012-10-02 9:18 ` Linus Walleij
2012-10-02 8:13 ` [PATCH 05/10] Input: bu21013_ts - Add support for Device Tree booting Lee Jones
2012-10-02 9:20 ` Linus Walleij
2012-10-02 8:13 ` [PATCH 06/10] Documentation: Detail permitted DT properties for the BU21013 Touch Screen Lee Jones
2012-10-02 9:21 ` Linus Walleij
2012-10-02 8:13 ` [PATCH 07/10] ARM: ux500: Create a new Device Tree include file for boards supporting STUIBs Lee Jones
2012-10-02 10:57 ` Linus Walleij
2012-10-02 8:13 ` [PATCH 08/10] ARM: ux500: Stop calling the UIB init function when using Device Tree Lee Jones
2012-10-02 10:57 ` Linus Walleij
2012-10-02 12:15 ` Lee Jones
2012-10-02 12:58 ` Linus Walleij
2012-10-02 8:13 ` [PATCH 09/10] ARM: ux500: Add all bu21013 touch screen components to supported Device Trees Lee Jones
2012-10-02 10:58 ` Linus Walleij
2012-10-02 8:13 ` [PATCH 10/10] ARM: ux500: Stop informing the regulator subsystem that we have full constraints Lee Jones
2012-10-02 11:00 ` Linus Walleij
2012-10-02 11:44 ` [PATCH 00/10] Platform data clean-up and UIB device enablement Arnd Bergmann
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=1349165603-24401-4-git-send-email-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).