From: peng.fan@nxp.com
To: ulf.hansson@linaro.org, robh+dt@kernel.org, shawnguo@kernel.org,
adrian.hunter@intel.com
Cc: devicetree@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
s.hauer@pengutronix.de, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
kernel@pengutronix.de, festevam@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/4] imx esdhc dt/driver update
Date: Thu, 21 Jan 2021 11:09:49 +0800 [thread overview]
Message-ID: <1611198593-16287-1-git-send-email-peng.fan@nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
Patch V2:
patch 1, 2, 3 is new
patch 4 is not changed
Peng Fan (4):
dt-bindings: mmc: fsl-imx-esdhc: add pinctrl bindings
dt-bindings: mmc: fsl-imx-esdhc: add clock bindings
arm64: dts: imx8qxp: correct usdhc clock-names sequence
mmc: sdhci-esdhc-imx: validate pinctrl before use it
.../bindings/mmc/fsl-imx-esdhc.yaml | 36 +++++++++++++++++++
arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 18 +++++-----
drivers/mmc/host/sdhci-esdhc-imx.c | 2 +-
3 files changed, 46 insertions(+), 10 deletions(-)
--
2.28.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-01-21 3:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 3:09 peng.fan [this message]
2021-01-21 3:09 ` [PATCH V2 1/4] dt-bindings: mmc: fsl-imx-esdhc: add pinctrl bindings peng.fan
2021-01-22 16:38 ` Rob Herring
2021-01-21 3:09 ` [PATCH V2 2/4] dt-bindings: mmc: fsl-imx-esdhc: add clock bindings peng.fan
2021-01-21 16:01 ` Rob Herring
2021-01-22 0:55 ` Peng Fan
2021-01-22 14:33 ` Rob Herring
2021-01-21 3:09 ` [PATCH V2 3/4] arm64: dts: imx8qxp: correct usdhc clock-names sequence peng.fan
2021-01-21 3:09 ` [PATCH V2 4/4] mmc: sdhci-esdhc-imx: validate pinctrl before use it peng.fan
2021-02-07 13:10 ` [PATCH V2 0/4] imx esdhc dt/driver update Peng Fan
2021-02-08 12:05 ` 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=1611198593-16287-1-git-send-email-peng.fan@nxp.com \
--to=peng.fan@nxp.com \
--cc=adrian.hunter@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).