From: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-samsung-soc@vger.kernel.org, Kukjin Kim <kgene@kernel.org>,
Tobias Jakobi <Liquid.Acid@gmx.net>,
Daniel Drake <drake@endlessm.com>,
Sebastian Reichel <sre@kernel.org>,
Seungwon Jeon <tgih.jun@samsung.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Joonyoung Shim <jy0922.shim@samsung.com>
Subject: Re: [PATCH 0/2] Fix reboot issue on Odroid boards with eMMC card
Date: Tue, 27 Jan 2015 09:56:07 +0100 [thread overview]
Message-ID: <1422348967.10070.26.camel@collabora.co.uk> (raw)
In-Reply-To: <1422346289-9348-1-git-send-email-m.szyprowski@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
On Tue, 2015-01-27 at 09:11 +0100, Marek Szyprowski wrote:
> Hello,
>
> This patchset fixes reboot hang issue on Hardkernel's Odroid boards with
> eMMC card. Those boards are designed in such a way, that the eMMC nreset
> signal is routed to SoC GPIO line instead of the board reset logic. To
> properly restard system, one need to set this line to zero before
> performing reboot.
>
> The initial patches consisted of a complete reset/power off driver, but
> after further analysis, it turned out that only eMMC nreset line control
> logic is specific for those boards. Everything else can be done by
> generic Exynos code, so the code has been moved to Exynos DW MMC driver.
This seems a general board design quirk, rather then an exynos specific
one. Potentially better to have this in the mmc core so it can be
re-used by non-exynos boards?
A very quick peek at the schematic for the hardkernel C1 (amlogic
based), shows that for that board the eMMC reset line is hooked up to an
SoC gpio line as well. (Although ofcourse, it may not need to be reset
before a warm restart depending on what the amlogic rom code does).
Random side-note, at least the samsung peach chromebooks are also hooked
up this way. But don't run into this issue as they load their initial
stages from flash rather then the eMMC.
> Best regards
> Marek Szyprowski
> Samsung R&D Institute Poland
>
>
> Changelog:
>
> initial version:
> http://thread.gmane.org/gmane.linux.power-management.general/51855/
>
>
> Path summary:
>
> Marek Szyprowski (2):
> mmc: dw_mmc-exynos: add support for controlling emmc reset pin
> ARM: dts: exynos*-odroid*: add eMMC reset line
>
> .../devicetree/bindings/mmc/exynos-dw-mshc.txt | 6 +++
> arch/arm/boot/dts/exynos4412-odroid-common.dtsi | 1 +
> arch/arm/boot/dts/exynos5422-odroidxu3.dts | 1 +
> drivers/mmc/host/dw_mmc-exynos.c | 43 +++++++++++++++++++++-
> 4 files changed, 50 insertions(+), 1 deletion(-)
>
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6170 bytes --]
next prev parent reply other threads:[~2015-01-27 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 8:11 [PATCH 0/2] Fix reboot issue on Odroid boards with eMMC card Marek Szyprowski
2015-01-27 8:11 ` [PATCH 1/2] mmc: dw_mmc-exynos: add support for controlling emmc reset pin Marek Szyprowski
2015-01-27 8:28 ` Jaehoon Chung
[not found] ` <54C74C33.5050305-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-01-28 12:41 ` Tobias Jakobi
[not found] ` <54C8D8E3.9060609-hi6Y0CQ0nG0@public.gmane.org>
2015-01-28 14:54 ` Ulf Hansson
[not found] ` <CAPDyKFr9fQ5ny=Foi4x_-wEQA9K0wRqqEfLxmxtBn5tmPwS-Nw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-28 15:23 ` Tobias Jakobi
2015-01-28 15:40 ` Ulf Hansson
[not found] ` <1422346289-9348-1-git-send-email-m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-01-27 8:11 ` [PATCH 2/2] ARM: dts: exynos*-odroid*: add eMMC reset line Marek Szyprowski
2015-01-27 8:56 ` Sjoerd Simons [this message]
[not found] ` <1422348967.10070.26.camel-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2015-01-27 13:29 ` [PATCH 0/2] Fix reboot issue on Odroid boards with eMMC card Marek Szyprowski
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=1422348967.10070.26.camel@collabora.co.uk \
--to=sjoerd.simons@collabora.co.uk \
--cc=Liquid.Acid@gmx.net \
--cc=devicetree@vger.kernel.org \
--cc=drake@endlessm.com \
--cc=jh80.chung@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sre@kernel.org \
--cc=tgih.jun@samsung.com \
--cc=ulf.hansson@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