From: Alex Elder <elder@ieee.org>
To: Matt Porter <mporter@linaro.org>, Alex Elder <elder@linaro.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Cc: Mark Brown <broonie@kernel.org>,
Christian Daudt <bcm@fixthebug.org>,
Devicetree List <devicetree@vger.kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: bcm28155-ap: leave camldo1 on to fix reboot
Date: Wed, 12 Mar 2014 08:16:19 -0500 [thread overview]
Message-ID: <53205E23.8030905@ieee.org> (raw)
In-Reply-To: <1394630079-12063-1-git-send-email-mporter@linaro.org>
On 03/12/2014 08:14 AM, Matt Porter wrote:
> The BCM28155-AP board has a bootloader that expects the camldo1
> regulator to be enabled on entry. Currently, the camldo1 regulator
> is disabled when no longer in use as is the case during a reboot /
> warm reset. This causes the early bootloader to hang upon entry. Add
> regulator-always-on to the camldo1 constraint to fix reboot.
>
> Reported-by: Alex Elder <elder@linaro.org>
> Signed-off-by: Matt Porter <mporter@linaro.org>
Tested-by: Alex Elder <elder@linaro.org>
> ---
> [Depends on BCM59056 regulator series dts support:
> http://www.gossamer-threads.com/lists/linux/kernel/1885489]
>
> arch/arm/boot/dts/bcm28155-ap.dts | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/bcm28155-ap.dts b/arch/arm/boot/dts/bcm28155-ap.dts
> index 99ff0c1..cc1303c 100644
> --- a/arch/arm/boot/dts/bcm28155-ap.dts
> +++ b/arch/arm/boot/dts/bcm28155-ap.dts
> @@ -94,6 +94,7 @@
> camldo1_reg: camldo1 {
> regulator-min-microvolt = <3300000>;
> regulator-max-microvolt = <3300000>;
> + regulator-always-on;
> };
>
> sdldo_reg: sdldo {
>
next prev parent reply other threads:[~2014-03-12 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 13:14 [PATCH] ARM: dts: bcm28155-ap: leave camldo1 on to fix reboot Matt Porter
2014-03-12 13:16 ` Alex Elder [this message]
2014-03-14 16:55 ` Matt Porter
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=53205E23.8030905@ieee.org \
--to=elder@ieee.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bcm@fixthebug.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@linaro.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).