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 15:35:41 +0530 [thread overview]
Message-ID: <BANLkTim9Wbxo5U77Vo=FFxYU4vsUps7GMA@mail.gmail.com> (raw)
In-Reply-To: <20110627083507.GG2508@legolas.emea.dhcp.ti.com>
Hi Felipe,
On 27 June 2011 14:05, 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.
>
> same comment I gave before to another patch:
>
> it makes the diff a lot easier to understand should anyone modify this
> later. It's also a matter of consistency.
>
A quick grep showed otherwise though ...
In arch/arm/mach-omap2/
Total regulators defined = 71
Regulators with exactly 1 supply = 58
Single element non-array definitions = 46/58
Single element array definitions = 12/58
Even if we consider 20% to be norm for consistency, I am not sure it's
a good one.
Still many samsung guys piously enclose magic value defines in parenthesis,
just to maintain 'consistency' !
And, I don't understand how does diff become any easier beyond 2
elements in the array.
Sorry for being bitchy, but I am unable to buy any reason other than
having more than
one element to use array.
-Jassi
--
Linaro.org ? Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 ?-
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
next prev parent reply other threads:[~2011-06-27 10:05 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
2011-06-27 8:35 ` Felipe Balbi
2011-06-27 10:05 ` Jaswinder Singh [this message]
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='BANLkTim9Wbxo5U77Vo=FFxYU4vsUps7GMA@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).