From: Paul Burton <paul.burton@mips.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <pburton@wavecomp.com>,
James Hogan <jhogan@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Paul Cercueil <paul@crapouillou.net>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH 3/3] MIPS: qi_lb60: Move MMC configuration to devicetree
Date: Mon, 22 Jul 2019 22:30:13 +0000 [thread overview]
Message-ID: <MWHPR2201MB1277E59D5FC1D9BE944902D7C1C40@MWHPR2201MB1277.namprd22.prod.outlook.com> (raw)
In-Reply-To: <20190125200927.21045-3-paul@crapouillou.net>
Hello,
Paul Cercueil wrote:
> Move the MMC configuration from the board C file to devicetree.
>
> The 'power' GPIO was removed and instead the vmmc regulator is used,
> to follow the changes introduced in the jz4740-mmc driver.
>
> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
Applied to mips-next.
Thanks,
Paul
[ This message was auto-generated; if you believe anything is incorrect
then please email paul.burton@mips.com to report it. ]
next prev parent reply other threads:[~2019-07-22 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 20:09 [PATCH 1/3] mmc: jz4740: Remove platform data and use standard APIs Paul Cercueil
2019-01-25 20:09 ` [PATCH 2/3] MIPS: DTS: jz4740: Add node for the MMC driver Paul Cercueil
2019-07-22 21:22 ` Paul Burton
2019-01-25 20:09 ` [PATCH 3/3] MIPS: qi_lb60: Move MMC configuration to devicetree Paul Cercueil
2019-07-22 22:30 ` Paul Burton [this message]
2019-01-26 12:10 ` [PATCH 1/3] mmc: jz4740: Remove platform data and use standard APIs Linus Walleij
2019-01-28 12:02 ` Ulf Hansson
2019-01-28 12:58 ` Paul Cercueil
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=MWHPR2201MB1277E59D5FC1D9BE944902D7C1C40@MWHPR2201MB1277.namprd22.prod.outlook.com \
--to=paul.burton@mips.com \
--cc=devicetree@vger.kernel.org \
--cc=jhogan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paul@crapouillou.net \
--cc=pburton@wavecomp.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).