From: Jerome Brunet <jbrunet@baylibre.com>
To: Kevin Hilman <khilman@baylibre.com>
Cc: devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-kernel@vger.kernel.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: [PATCH 0/3] arm64: dts: meson: g12a: add mmc B and C
Date: Tue, 14 May 2019 11:16:08 +0200 [thread overview]
Message-ID: <20190514091611.15278-1-jbrunet@baylibre.com> (raw)
This patchset adds the MMC controller B and C to the g12a SoC as well
as the u200 and sei510 boards.
MMC controller A has been left out on purpose. This controller is
special on this SoC family and will be added later on.
Notice the use of the pinconf DT property 'drive-strength-microamp'.
Support for this property is not yet merged in meson pinctrl driver but
the DT part as been acked by the DT maintainer [0] so it should be safe
to use.
[0]: https://lkml.kernel.org/r/20190513152451.GA25690@bogus
Jerome Brunet (3):
arm64: dts: meson: g12a: add mmc nodes
arm64: dts: meson: u200: add sd and emmc
arm64: dts: meson: sei510: add sd and emmc
.../boot/dts/amlogic/meson-g12a-sei510.dts | 42 ++++++
.../boot/dts/amlogic/meson-g12a-u200.dts | 42 ++++++
arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 124 ++++++++++++++++++
3 files changed, 208 insertions(+)
--
2.20.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2019-05-14 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 9:16 Jerome Brunet [this message]
2019-05-14 9:16 ` [PATCH 1/3] arm64: dts: meson: g12a: add mmc nodes Jerome Brunet
2019-05-14 18:29 ` Martin Blumenstingl
2019-05-14 9:16 ` [PATCH 2/3] arm64: dts: meson: u200: add sd and emmc Jerome Brunet
2019-05-14 18:24 ` Martin Blumenstingl
2019-05-14 9:16 ` [PATCH 3/3] arm64: dts: meson: sei510: " Jerome Brunet
2019-05-14 18:24 ` Martin Blumenstingl
2019-05-14 10:21 ` [PATCH 0/3] arm64: dts: meson: g12a: add mmc B and C Neil Armstrong
2019-05-15 0:23 ` Kevin Hilman
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=20190514091611.15278-1-jbrunet@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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).