From: Neil Armstrong <narmstrong@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org, khilman@baylibre.com
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] ARM: dts: wire up the power domains on Meson8/8b/8m2
Date: Mon, 22 Jun 2020 09:56:00 +0200 [thread overview]
Message-ID: <ba6e6dc7-623c-aa52-5750-b44737b2c372@baylibre.com> (raw)
In-Reply-To: <20200620161010.23171-1-martin.blumenstingl@googlemail.com>
On 20/06/2020 18:10, Martin Blumenstingl wrote:
> Now that the meson-ee-pwrc driver has gained support for the power
> domains on Meson8/Meson8b/Meson8m2 we can add it to the corresponding
> .dtsi files.
>
> So far this doesn't fix (or break) anything for me (probably because all
> vendor u-boots are enabling the Ethernet power domains unconditionally).
> But at least it's one preparation step which is needed for video output
> in the future.
>
>
> Martin Blumenstingl (3):
> ARM: dts: meson8: add power domain controller
> ARM: dts: meson8m2: add resets for the power domain controller
> ARM: dts: meson8b: add power domain controller
>
> arch/arm/boot/dts/meson8.dtsi | 13 +++++++++++++
> arch/arm/boot/dts/meson8b.dtsi | 27 +++++++++++++++++++++++++++
> arch/arm/boot/dts/meson8m2.dtsi | 19 +++++++++++++++++++
> 3 files changed, 59 insertions(+)
>
For the serie:
Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
next prev parent reply other threads:[~2020-06-22 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 16:10 Martin Blumenstingl
2020-06-20 16:10 ` [PATCH 1/3] ARM: dts: meson8: add power domain controller Martin Blumenstingl
2020-06-20 16:10 ` [PATCH 2/3] ARM: dts: meson8m2: add resets for the " Martin Blumenstingl
2020-06-20 16:10 ` [PATCH 3/3] ARM: dts: meson8b: add " Martin Blumenstingl
2020-06-22 7:56 ` Neil Armstrong [this message]
2020-07-13 19:03 ` [PATCH 0/3] ARM: dts: wire up the power domains on Meson8/8b/8m2 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=ba6e6dc7-623c-aa52-5750-b44737b2c372@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
/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
all inboxes | Powered by JetHome®