From: Heiko Stuebner <heiko@sntech.de>
To: djw@t-chip.com.cn
Cc: linux-rockchip@lists.infradead.org,
Wayne Chou <zxf@t-chip.com.cn>,
devicetree@vger.kernel.org, David Wu <david.wu@rock-chips.com>,
Liang Chen <cl@rock-chips.com>,
linux-kernel@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: Re: [PATCH v4 3/4] arm64: dts: rockchip: add io-domain to roc-rk3328-cc
Date: Thu, 02 Aug 2018 14:54:06 +0200 [thread overview]
Message-ID: <3471113.4LqEKgWTCV@phil> (raw)
In-Reply-To: <1533016762-5268-4-git-send-email-djw@t-chip.com.cn>
Am Dienstag, 31. Juli 2018, 07:59:21 CEST schrieb djw@t-chip.com.cn:
> From: Levin Du <djw@t-chip.com.cn>
>
> It is necessary for the io domain setting of the SoC to match the voltage
> supplied by the regulators.
>
> Signed-off-by: Levin Du <djw@t-chip.com.cn>
applied to my dts64 branch, possibly still for 4.19.
Other dts patches need to wait for the syscon-gpio change to land.
Thanks
Heiko
next prev parent reply other threads:[~2018-08-02 12:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 5:59 [PATCH v4 0/4] Add sdmmc UHS support to ROC-RK3328-CC board djw
2018-07-31 5:59 ` [PATCH v4 1/4] gpio: syscon: rockchip: add GRF GPIO support for rk3328 djw
2018-07-31 19:36 ` Rob Herring
2018-08-01 11:46 ` Heiko Stuebner
2018-08-03 17:13 ` Linus Walleij
2018-07-31 5:59 ` [PATCH v4 2/4] arm64: dts: rockchip: add GRF GPIO controller to rk3328 djw
2018-08-04 13:16 ` Heiko Stuebner
2018-07-31 5:59 ` [PATCH v4 3/4] arm64: dts: rockchip: add io-domain to roc-rk3328-cc djw
2018-08-02 12:54 ` Heiko Stuebner [this message]
2018-07-31 5:59 ` [PATCH v4 4/4] arm64: dts: rockchip: add sdmmc UHS support for roc-rk3328-cc djw
2018-08-04 13:18 ` 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=3471113.4LqEKgWTCV@phil \
--to=heiko@sntech.de \
--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=djw@t-chip.com.cn \
--cc=linux-arm-kernel@lists.infradead.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=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).