From: Pankaj Dubey <pankaj.dubey@samsung.com>
To: Kukjin Kim <kgene@kernel.org>,
'Yadwinder Singh Brar' <yadi.brar@samsung.com>,
devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: robh+dt@kernel.org, yadi.brar01@gmail.com
Subject: Re: [1/2] ARM: dts: Fix bootup issue on smdk5250
Date: Tue, 28 Apr 2015 16:35:45 +0530 [thread overview]
Message-ID: <553F6989.3080406@samsung.com> (raw)
In-Reply-To: <038501d00604$034a9640$09dfc2c0$@kernel.org>
Hi Kukjin,
On Saturday 22 November 2014 08:55 AM, Kukjin Kim wrote:
> Pankaj Dubey wrote:
>>
>> Hi,
>>
> Hi,
>
> Yadwinder, please don't miss [PATCH 1/2] in subject, so that my e-mail client
> can't filter wrong ;)
>
>> On Tuesday 18 November 2014 05:38 PM, Yadwinder Singh Brar wrote:
>>> With default config on smdk5250 latest tree throws below message :
>>>
>>> [ 2.226049] thermal thermal_zone0: critical temperature reached(224 C),shutting down
>>> [ 2.227840] reboot: Failed to start orderly shutdown: forcing the issue
>>>
>>> and hangs randomly because it reads wrong temperature value.
>>>
>>> I can't figure out any direct relation between LDO10 and TMU from board
>>> schematics which I have. So making LDO10 always-on to fix issue for now.
>>>
> Hmm...strange, I also can't see any relations now...but I need to contact to
> hardware guy before applying this, this fixes the problem though.
>
By any chance you got time to check with HW engineer, as issue is there
without this patch, SMDK5250 fails to boot and hangs.
Thanks,
Pankaj Dubey
> Thanks,
> Kukjin
>
>>> Signed-off-by: Yadwinder Singh Brar <yadi.brar@samsung.com>
>>>
>>
>> Tested this on SMDK5250 board, system boot is fine now, hence
>>
>> Tested-by: Pankaj Dubey <pankaj.dubey@samsung.com>
>>
>>> ---
>>> arch/arm/boot/dts/exynos5250-smdk5250.dts | 1 +
>>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/arch/arm/boot/dts/exynos5250-smdk5250.dts b/arch/arm/boot/dts/exynos5250-smdk5250.dts
>>> index bc27cc2..95b5b51 100644
>>> --- a/arch/arm/boot/dts/exynos5250-smdk5250.dts
>>> +++ b/arch/arm/boot/dts/exynos5250-smdk5250.dts
>>> @@ -190,6 +190,7 @@
>>> regulator-name = "P1.8V_LDO_OUT10";
>>> regulator-min-microvolt = <1800000>;
>>> regulator-max-microvolt = <1800000>;
>>> + regulator-always-on;
>>> };
>>>
>>> ldo11_reg: LDO11 {
>>>
>
>
prev parent reply other threads:[~2015-04-28 11:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 12:08 [PATCH 1/2] ARM: dts: Fix bootup issue on smdk5250 Yadwinder Singh Brar
2014-11-18 12:08 ` [PATCH 2/2] ARM: dts: Add missing irq pinctrl for max77686 " Yadwinder Singh Brar
2014-11-18 14:02 ` Javier Martinez Canillas
2014-11-20 4:06 ` [2/2] " Pankaj Dubey
2015-04-28 11:02 ` Pankaj Dubey
2015-05-02 5:49 ` Krzysztof Kozlowski
2015-08-17 5:50 ` Krzysztof Kozlowski
2015-08-18 6:13 ` Pankaj Dubey
2015-08-18 6:27 ` Pankaj Dubey
2015-08-18 7:00 ` Krzysztof Kozlowski
2014-11-20 4:01 ` [1/2] ARM: dts: Fix bootup issue " Pankaj Dubey
2014-11-22 3:25 ` Kukjin Kim
2014-11-25 13:16 ` Yadwinder Singh Brar
2015-04-28 11:05 ` Pankaj Dubey [this message]
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=553F6989.3080406@samsung.com \
--to=pankaj.dubey@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=yadi.brar01@gmail.com \
--cc=yadi.brar@samsung.com \
/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