From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: dts: configure regulators for Gumstix Pepper
Date: Sun, 28 Jun 2015 23:47:17 -0700 [thread overview]
Message-ID: <20150629064717.GR4156@atomide.com> (raw)
In-Reply-To: <1433441299-18887-3-git-send-email-arun@gumstix.com>
* Arun Bharadwaj <arun@gumstix.com> [150604 11:10]:
> From: Adam YH Lee <adam.yh.lee@gmail.com>
>
> Boot process is halting in midway because some of the necessary voltage
> regulators are deemed unused and subsequently powered off, leading to
> a completely unresponsive system.
OK that needs to be fixed for v4.2-rc series.
> Most of the device nodes had correct voltage regulator attachments.
> Yet these nodes had to set stricter enforcement on them through
> 'regulator-boot-on' and 'regulator-always-on' to function correctly.
That's a lot of regulators marked as regulator-always-on. Could
you please update the description what consumers are using them
so we know why they are all needed always-on?
> Signed-off-by: Ash Charles <ashcharles@gmail.com>
>From Adam, sent by Arun, signed by Ash? Can you please check
that too.
Regards,
Tony
next prev parent reply other threads:[~2015-06-29 6:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 18:08 [PATCH 0/3] ARM: dts: Changes for Gumstix Pepper dts Arun Bharadwaj
2015-06-04 18:08 ` [PATCH 1/3] ARM: dts: Correct audio input route & set mic bias Arun Bharadwaj
2015-07-14 6:57 ` Tony Lindgren
2015-06-04 18:08 ` [PATCH 2/3] ARM: dts: configure regulators for Gumstix Pepper Arun Bharadwaj
2015-06-29 6:47 ` Tony Lindgren [this message]
2015-07-02 18:34 ` Ash Charles
2015-07-03 5:53 ` Tony Lindgren
2015-06-04 18:08 ` [PATCH 3/3] ARM: dts: Fix frequency scaling on " Arun Bharadwaj
2015-06-09 15:45 ` Ash Charles
2015-07-14 6:54 ` Tony Lindgren
2015-07-14 12:25 ` [PATCH 0/3] ARM: dts: Changes for Gumstix Pepper dts Kevin Hilman
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=20150629064717.GR4156@atomide.com \
--to=tony@atomide.com \
--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).