From: Peter Barada <peter.barada@logicpd.com>
To: linux-omap@vger.kernel.org, Peter Barada <peter.barada@logicpd.com>
Subject: Regulator question regarding I2C devices
Date: Fri, 28 Jan 2011 17:24:01 -0500 [thread overview]
Message-ID: <4D434201.6060108@logicpd.com> (raw)
I have a tsc2004 touch controller on I2C3 that is powered by vaux1, and since its probed I have to turn the power on before it can be probed. I've created:
static struct regulator_consumer_supply dm3730logic_vaux1_supply = {
.supply = "vaux1",
};
/* VAUX1 for touch chip */
static struct regulator_init_data dm3730logic_vaux1 = {
.constraints = {
.min_uV = 3000000,
.max_uV = 3000000,
.apply_uV = true,
.valid_modes_mask = REGULATOR_MODE_NORMAL
| REGULATOR_MODE_STANDBY,
.valid_ops_mask = REGULATOR_CHANGE_MODE
| REGULATOR_CHANGE_STATUS,
},
.num_consumer_supplies = 1,
.consumer_supplies = &dm3730logic_vaux1_supply,
};
and listed it in the twldata initializer
.vaux1 = &dm3730logic_vaux1,
But it never gets enabled... How can I tell the kernel to turn the regulator on?
If I try to call regulator_get() right before the call to omap_register_i2c_bus for I2C3, regulator_get returns a NULL due to regulator_map_list being empty. If I look in sys/class/regulator I see VAUX1 listed (as regulator.4), but there are no users.
Any suggestions on how I can turn on vaux1 so the tsc2004 touch controller is visible to by the I2C system?
Thanks in advance!
--
Peter Barada
peter.barada@logicpd.com
next reply other threads:[~2011-01-28 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 22:24 Peter Barada [this message]
2011-01-29 17:34 ` Regulator question regarding I2C devices Matthias Kaehlcke
2011-01-29 19:58 ` Peter Barada
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=4D434201.6060108@logicpd.com \
--to=peter.barada@logicpd.com \
--cc=linux-omap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.