public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
	Heiner Kallweit <hkallweit1@gmail.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 0/4] mmc: add pwrseq-based hw_reset
Date: Wed, 01 Mar 2017 10:01:55 -0800	[thread overview]
Message-ID: <m2lgsozxik.fsf@baylibre.com> (raw)
In-Reply-To: <db739bb8-2ad1-75bb-0b65-8246f84da7e8@gmail.com> (Heiner Kallweit's message of "Wed, 8 Feb 2017 22:45:52 +0100")

Ulf,

Heiner Kallweit <hkallweit1@gmail.com> writes:

> For implementing ops hw_reset in struct meson_host_ops often we can
> use what is available in pwrseq already, just with a small extension.
> For example all existing pwrseq drivers parse DT for a reset GPIO.

Do you have any thoughts on this series?

Kevin

> Meson GX is the first user of this extension.
>
> Heiner Kallweit (4):
>   mmc: pwrseq: add op reset to struct mmc_pwrseq_ops
>   mmc: pwrseq: implement reset operation in pwrseq_emmc
>   mmc: meson-gx: add pwrseq-based hw_reset
>   ARM64: dts: meson-gxbb-odroidc2: add hw-reset capability flag for emmc port
>
>  arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 1 +
>  drivers/mmc/core/core.c                             | 6 ++++++
>  drivers/mmc/core/pwrseq.c                           | 8 ++++++++
>  drivers/mmc/core/pwrseq.h                           | 3 +++
>  drivers/mmc/core/pwrseq_emmc.c                      | 1 +
>  drivers/mmc/host/meson-gx-mmc.c                     | 1 +
>  include/linux/mmc/core.h                            | 1 +
>  7 files changed, 21 insertions(+)

      reply	other threads:[~2017-03-01 19:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 21:45 [PATCH 0/4] mmc: add pwrseq-based hw_reset Heiner Kallweit
2017-03-01 18:01 ` Kevin Hilman [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=m2lgsozxik.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --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