From: Matt Ranostay <matt@ranostay.consulting>
To: linux-mmc@vger.kernel.org
Cc: tony@atomide.com, ulf.hansson@linaro.org,
Matt Ranostay <matt@ranostay.consulting>
Subject: [PATCH v4 0/2] mmc: pwrseq: add support for Marvell SD8787 chip
Date: Mon, 23 Jan 2017 19:08:28 -0800 [thread overview]
Message-ID: <20170124030830.21766-1-matt@ranostay.consulting> (raw)
Changes from v1:
* split devictree docs from pwrseq changes
* rebase devicetree documents due to filename change
* rebase pwrseq patchset
Changes from v2:
* update device tree bindings to powerdown-gpios and document
active state
Changes from v3:
* actually update patchset series
* correct overlooked gpio to gpios renaming of properties
Matt Ranostay (2):
devicetree: document new marvell-8xxx and pwrseq-sd8787 options
mmc: pwrseq: add support for Marvell SD8787 chip
.../devicetree/bindings/mmc/mmc-pwrseq-sd8787.txt | 16 +++
.../bindings/net/wireless/marvell-8xxx.txt | 7 +-
drivers/mmc/core/Kconfig | 10 ++
drivers/mmc/core/Makefile | 1 +
drivers/mmc/core/pwrseq_sd8787.c | 117 +++++++++++++++++++++
5 files changed, 150 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/mmc/mmc-pwrseq-sd8787.txt
create mode 100644 drivers/mmc/core/pwrseq_sd8787.c
--
2.10.2
next reply other threads:[~2017-01-24 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 3:08 Matt Ranostay [this message]
[not found] ` <20170124030830.21766-1-matt-sk+viVC6FLCDq+mSdOJa79kegs52MxvZ@public.gmane.org>
2017-01-24 3:08 ` [PATCH v4 1/2] devicetree: document new marvell-8xxx and pwrseq-sd8787 options Matt Ranostay
2017-01-27 21:22 ` Rob Herring
2017-01-24 3:08 ` [PATCH v4 2/2] mmc: pwrseq: add support for Marvell SD8787 chip Matt Ranostay
2017-01-24 9:56 ` [PATCH v4 0/2] " Ulf Hansson
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=20170124030830.21766-1-matt@ranostay.consulting \
--to=matt@ranostay.consulting \
--cc=linux-mmc@vger.kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.