From: jaswinder.singh@linaro.org (Jaswinder Singh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP4: PANDA, SDP: Fix EHCI regulator supply
Date: Mon, 27 Jun 2011 13:38:54 +0530 [thread overview]
Message-ID: <BANLkTinVdWjoS-qdGnSxGnmrPKHSDNV7hw@mail.gmail.com> (raw)
In-Reply-To: <20110627080036.GB2508@legolas.emea.dhcp.ti.com>
Hi Felipe,
On 27 June 2011 13:30, Felipe Balbi <balbi@ti.com> wrote:
>> >
>> > +static struct regulator_consumer_supply sdp4430_vusb_supply =
>> > + ? ? ? REGULATOR_SUPPLY("hsusb0", "ehci-omap.0");
>
> this should be an array.
Ok, I can make it an array of _one_ element.
Though I am not sure why is that a good thing, or are we to use another
possible VUSB supply on Panda/SDP boards ? Please suggest so that
I can add that too.
>> > ?static struct regulator_init_data sdp4430_vusb = {
>> > ? ? ? ?.constraints = {
>> > ? ? ? ? ? ? ? ?.min_uV ? ? ? ? ? ? ? ? = 3300000,
>> > ? ? ? ? ? ? ? ?.max_uV ? ? ? ? ? ? ? ? = 3300000,
>> > - ? ? ? ? ? ? ? .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,
>
> ARRAY_SIZE()
Yes, of course if we are to switch to single-element array.
Thanks,
Jassi
next prev parent reply other threads:[~2011-06-27 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 14:37 [PATCH] OMAP4: PANDA, SDP: Fix EHCI regulator supply Jassi Brar
2011-06-24 17:07 ` Jaswinder Singh
2011-06-27 8:00 ` Felipe Balbi
2011-06-27 8:08 ` Jaswinder Singh [this message]
2011-06-27 8:35 ` Felipe Balbi
2011-06-27 10:05 ` Jaswinder Singh
2011-06-27 10:11 ` Felipe Balbi
2011-06-27 11:10 ` Jaswinder Singh
2011-06-27 15:02 ` [PATCHv2] " Jassi Brar
2011-06-27 15:05 ` Felipe Balbi
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=BANLkTinVdWjoS-qdGnSxGnmrPKHSDNV7hw@mail.gmail.com \
--to=jaswinder.singh@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).