From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org
Cc: kever.yang@rock-chips.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] arm64: dts: rockchip: bring rk3399-firefly power-tree in line
Date: Tue, 30 May 2017 12:07:23 +0200 [thread overview]
Message-ID: <2924720.omGovoX6XK@phil> (raw)
In-Reply-To: <20170523095427.7421-1-heiko@sntech.de>
Am Dienstag, 23. Mai 2017, 11:54:25 CEST schrieb Heiko Stuebner:
> The power-tree on the rk3399-firefly did not completely match the
> documentation and vendor devicetree. It was also missing some
> supply-hirarchy information and some regulator-gpio names did not
> match the schematics. Fix this for the existing regulators before
> introducing new things.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
applied all 3 for 4.13, with the ethernet alias changed to ethernet0
as suggested
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64: dts: rockchip: bring rk3399-firefly power-tree in line
Date: Tue, 30 May 2017 12:07:23 +0200 [thread overview]
Message-ID: <2924720.omGovoX6XK@phil> (raw)
In-Reply-To: <20170523095427.7421-1-heiko@sntech.de>
Am Dienstag, 23. Mai 2017, 11:54:25 CEST schrieb Heiko Stuebner:
> The power-tree on the rk3399-firefly did not completely match the
> documentation and vendor devicetree. It was also missing some
> supply-hirarchy information and some regulator-gpio names did not
> match the schematics. Fix this for the existing regulators before
> introducing new things.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
applied all 3 for 4.13, with the ethernet alias changed to ethernet0
as suggested
Heiko
next prev parent reply other threads:[~2017-05-30 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 9:54 [PATCH 1/3] arm64: dts: rockchip: bring rk3399-firefly power-tree in line Heiko Stuebner
2017-05-23 9:54 ` Heiko Stuebner
[not found] ` <20170523095427.7421-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2017-05-23 9:54 ` [PATCH 2/3] arm64: dts: rockchip: add ethernet alias on rk3399 Heiko Stuebner
2017-05-23 9:54 ` Heiko Stuebner
2017-05-23 10:15 ` Baruch Siach
2017-05-23 10:15 ` Baruch Siach
2017-05-23 11:12 ` Heiko Stuebner
2017-05-23 11:12 ` Heiko Stuebner
2017-05-23 9:54 ` [PATCH 3/3] arm64: dts: rockchip: enable usb3 controllers on rk3399-firefly Heiko Stuebner
2017-05-23 9:54 ` Heiko Stuebner
2017-05-30 10:07 ` Heiko Stuebner [this message]
2017-05-30 10:07 ` [PATCH 1/3] arm64: dts: rockchip: bring rk3399-firefly power-tree in line 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=2924720.omGovoX6XK@phil \
--to=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.