From: Shawn Lin <shawn.lin@rock-chips.com>
To: Guodong Xu <guodong.xu@linaro.org>,
jh80.chung@samsung.com, --to=robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
ulf.hansson@linaro.org
Cc: shawn.lin@rock-chips.com, "Heiko Stübner" <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] mmc: dw_mmc: controller reset support
Date: Wed, 30 Mar 2016 19:45:05 +0800 [thread overview]
Message-ID: <56FBBC41.5080104@rock-chips.com> (raw)
In-Reply-To: <1459322696-29919-1-git-send-email-guodong.xu@linaro.org>
+ Heiko
On 2016/3/30 15:24, Guodong Xu wrote:
> mmc controller registers may in abnormal state if mmc is used in
> bootloader, eg. to load kernel from eMMC. Some controllers cann't
> clear their registers when clk is set. They use dedicated reset
> logics to do this.
>
> In this patch, a 'resets' property is added into dw_mmc dts
> node. When driver does parse_dt and probe, it calls reset API to
> deassert the 'reset' of dw_mmc host controller. When probe error or
> remove, it calls reset API to assert it.
>
> Chip vendor's actual reset logics is implemented in reset driver, not
> in dw_mmc code.
>
> Please also refer to Documentation/devicetree/bindings/reset/reset.txt
>
> Guodong Xu (2):
> Documentation: synopsys-dw-mshc: add binding for resets
> mmc: dw_mmc: add resets support to dw_mmc
>
> .../devicetree/bindings/mmc/synopsys-dw-mshc.txt | 4 ++++
> drivers/mmc/host/dw_mmc.c | 20 +++++++++++++++++++-
> include/linux/mmc/dw_mmc.h | 6 ++++--
> 3 files changed, 27 insertions(+), 3 deletions(-)
>
--
Best Regards
Shawn Lin
prev parent reply other threads:[~2016-03-30 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 7:24 [PATCH v3 0/2] mmc: dw_mmc: controller reset support Guodong Xu
2016-03-30 7:24 ` [PATCH v3 1/2] Documentation: synopsys-dw-mshc: add binding for resets Guodong Xu
2016-03-30 7:24 ` [PATCH v3 2/2] mmc: dw_mmc: add resets support to dw_mmc Guodong Xu
2016-03-30 11:40 ` Jaehoon Chung
2016-04-01 18:42 ` Heiko Stuebner
2016-04-04 3:54 ` Jaehoon Chung
2016-04-01 18:42 ` Heiko Stuebner
[not found] ` <CAFGCpxzUBUvMLWHUmd1WYDM7Do0J=QvaNbVQYMi_cQEhbV9-1Q@mail.gmail.com>
2016-04-02 14:03 ` Heiko Stuebner
2016-05-25 13:33 ` Guodong Xu
2016-03-30 11:45 ` Shawn Lin [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=56FBBC41.5080104@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=guodong.xu@linaro.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.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