From: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Roger Quadros <rogerq-l0cyMroinI0@public.gmane.org>
Cc: "tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org"
<tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
"b-cousson-l0cyMroinI0@public.gmane.org"
<b-cousson-l0cyMroinI0@public.gmane.org>,
"balbi-l0cyMroinI0@public.gmane.org"
<balbi-l0cyMroinI0@public.gmane.org>,
"keshava_mgowda-l0cyMroinI0@public.gmane.org"
<keshava_mgowda-l0cyMroinI0@public.gmane.org>,
"linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Mark Brown
<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
Subject: Re: [PATCH 4/4] regulator: fixed: Properly use input_supply parameter from device tree
Date: Thu, 15 Nov 2012 14:11:59 -0500 [thread overview]
Message-ID: <50A53E7F.6070705@nvidia.com> (raw)
In-Reply-To: <1352991396-19589-5-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
On 11/15/2012 09:56 AM, Roger Quadros wrote:
> The device tree node will provide the input supply name as
> a string. Use that to populate the supply_name parameter of
> the regulator descriptor.
>
> Also correct the documentation to reflect the same.
>
> Signed-off-by: Roger Quadros <rogerq-l0cyMroinI0@public.gmane.org>
> CC: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> CC: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
> ---
> regulator-boot-on;
> gpio-open-drain;
> - vin-supply = <&parent_reg>;
> + vin-supply = "input-supply-name";
This is not correct as per the regulator binding. It says
- <name>-supply: phandle to the parent supply/regulator node
So we need to pass the phandle rather than string.
Just for curiosity, why do you want this change? What is the issue are
you facing.
This change will creates regression on many platform.
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-11-15 19:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 14:56 [PATCH 0/4] Device tree support for OMAP USB Host Roger Quadros
2012-11-15 14:56 ` [PATCH 2/4] ARM: OMAP4: USB: Add pin mux configuration for panda board Roger Quadros
[not found] ` <1352991396-19589-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2012-11-15 14:56 ` [PATCH 1/4] ARM: OMAP: usb-host: Device tree support for USB Host Roger Quadros
2012-11-16 10:30 ` Benoit Cousson
2012-11-16 10:55 ` Roger Quadros
2012-11-16 11:06 ` Benoit Cousson
2012-11-16 12:05 ` Roger Quadros
2012-11-15 14:56 ` [PATCH 3/4] ARM/dts: omap4-panda: Add USB Host support Roger Quadros
2012-11-15 14:56 ` [PATCH 4/4] regulator: fixed: Properly use input_supply parameter from device tree Roger Quadros
[not found] ` <1352991396-19589-5-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2012-11-15 19:11 ` Laxman Dewangan [this message]
[not found] ` <50A53E7F.6070705-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-11-16 10:23 ` Roger Quadros
2012-12-15 14:55 ` Mark Brown
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=50A53E7F.6070705@nvidia.com \
--to=ldewangan-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=b-cousson-l0cyMroinI0@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
--cc=keshava_mgowda-l0cyMroinI0@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rogerq-l0cyMroinI0@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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.