From: djw@t-chip.com.cn
To: linux-rockchip@lists.infradead.org
Cc: Wayne Chou <zxf@t-chip.com.cn>, Levin Du <djw@t-chip.com.cn>,
devicetree@vger.kernel.org, David Wu <david.wu@rock-chips.com>,
Heiko Stuebner <heiko@sntech.de>, Liang Chen <cl@rock-chips.com>,
William Wu <william.wu@rock-chips.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Rocky Hao <rocky.hao@rock-chips.com>,
Will Deacon <will.deacon@arm.com>,
Joseph Chen <chenjh@rock-chips.com>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
"David S. Miller" <davem@davemloft.net>
Subject: [PATCH v0 0/2] Add sdmmc UHS support to ROC-RK3328-CC board
Date: Tue, 8 May 2018 10:48:22 +0800 [thread overview]
Message-ID: <1525747704-8537-1-git-send-email-djw@t-chip.com.cn> (raw)
From: Levin Du <djw@t-chip.com.cn>
Hi all,
This is an attemp to add sdmmc UHS support to the ROC-RK3328-CC board.
It adds a new compatible `rockchip,rk3328-gpio-syscon10` to the gpio-syscon
driver, so that a new gpio controller named `gpio_syscon10` can be defined
and used in the regulator-gpio. This regulator controls the signal voltage of the
sdmmc. It is essential for UHS support which requires 1.8V signal voltage.
Levin Du (2):
gpio: syscon: Add gpio-syscon for rk3328
arm64: dts: rockchip: Add sdmmc UHS support for roc-rk3328-cc
arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts | 36 ++++++++++++++++++++++++++
drivers/gpio/gpio-syscon.c | 32 +++++++++++++++++++++++
2 files changed, 68 insertions(+)
--
2.7.4
next reply other threads:[~2018-05-08 2:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 2:48 djw [this message]
2018-05-08 2:48 ` [PATCH v0 2/2] arm64: dts: rockchip: Add sdmmc UHS support for roc-rk3328-cc djw
2018-05-08 11:57 ` Heiko Stuebner
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=1525747704-8537-1-git-send-email-djw@t-chip.com.cn \
--to=djw@t-chip.com.cn \
--cc=catalin.marinas@arm.com \
--cc=chenjh@rock-chips.com \
--cc=cl@rock-chips.com \
--cc=davem@davemloft.net \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=rocky.hao@rock-chips.com \
--cc=will.deacon@arm.com \
--cc=william.wu@rock-chips.com \
--cc=zxf@t-chip.com.cn \
/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).