From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] arm64: meson-gxm: Add support for the Mali T820 GPU
Date: Mon, 01 Apr 2019 21:42:40 -0700 [thread overview]
Message-ID: <7hbm1puif3.fsf@baylibre.com> (raw)
In-Reply-To: <ed3ca736-0d2d-0a69-2e14-a9ed29f0cd13@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> On 15/03/2019 14:56, Neil Armstrong wrote:
>> This patchset adds :
>> - Optional reset properties in the midgard bindings
>> - Mali T820 Node in Amlogic Meson GXM DTSI
>>
>> Changes since v1:
>> - Updated midgard DT wording following the recently submitted
>> bifrost bindings
>>
>> Christian Hewitt (1):
>> arm64: dts: meson-gxm: Add Mali-T820 node
>>
>> Neil Armstrong (1):
>> dt-bindings: gpu: mali-midgard: Add resets property
>>
>> .../bindings/gpu/arm,mali-midgard.txt | 14 ++++++++++
>> arch/arm64/boot/dts/amlogic/meson-gxm.dtsi | 27 +++++++++++++++++++
>> 2 files changed, 41 insertions(+)
>>
>
> Kevin, can you take both in your tree now the bindings are reviewed ?
Yes.
Queud for v5.2 (branch: v5.2/dt64)
Thanks,
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-04-02 4:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 13:56 [PATCH v2 0/2] arm64: meson-gxm: Add support for the Mali T820 GPU Neil Armstrong
2019-03-15 13:56 ` [PATCH v2 1/2] dt-bindings: gpu: mali-midgard: Add resets property Neil Armstrong
2019-03-31 6:40 ` Rob Herring
2019-03-15 13:56 ` [PATCH v2 2/2] arm64: dts: meson-gxm: Add Mali-T820 node Neil Armstrong
2019-04-01 8:48 ` [PATCH v2 0/2] arm64: meson-gxm: Add support for the Mali T820 GPU Neil Armstrong
2019-04-02 4:42 ` Kevin Hilman [this message]
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=7hbm1puif3.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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;
as well as URLs for NNTP newsgroup(s).