From: Heiko Stuebner <heiko@sntech.de>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Hans Verkuil <hans.verkuil@cisco.com>,
kernel@collabora.com,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Tomasz Figa <tfiga@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Miouyouyou <myy@miouyouyou.fr>
Subject: Re: [PATCH v11 2/4] ARM: dts: rockchip: add VPU device node for RK3288
Date: Thu, 06 Dec 2018 13:41:58 +0100 [thread overview]
Message-ID: <3396503.flnDFgv558@phil> (raw)
In-Reply-To: <20181130173433.24185-3-ezequiel@collabora.com>
Am Freitag, 30. November 2018, 18:34:31 CET schrieb Ezequiel Garcia:
> Add the Video Processing Unit node for RK3288 SoC.
>
> Fix the VPU IOMMU node, which was disabled and lacking
> its power domain property.
>
> Reviewed-by: Tomasz Figa <tfiga@chromium.org>
> Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
applied for 4.21 after a tiny bit of reordering
Thanks for seeing this through
Heiko
next prev parent reply other threads:[~2018-12-06 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 17:34 [PATCH v11 0/4] Add Rockchip VPU JPEG encoder Ezequiel Garcia
2018-11-30 17:34 ` [PATCH v11 1/4] media: dt-bindings: Document the Rockchip VPU bindings Ezequiel Garcia
2018-11-30 17:34 ` [PATCH v11 2/4] ARM: dts: rockchip: add VPU device node for RK3288 Ezequiel Garcia
2018-12-06 12:41 ` Heiko Stuebner [this message]
2018-11-30 17:34 ` [PATCH v11 3/4] arm64: dts: rockchip: add VPU device node for RK3399 Ezequiel Garcia
2018-12-06 12:42 ` Heiko Stuebner
2018-11-30 17:34 ` [PATCH v11 4/4] media: add Rockchip VPU JPEG encoder driver Ezequiel Garcia
2018-12-05 15:01 ` Hans Verkuil
2018-12-05 15:09 ` Ezequiel Garcia
2018-12-05 16:04 ` Ezequiel Garcia
2018-12-05 16:09 ` [PATCH v12] " Ezequiel Garcia
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=3396503.flnDFgv558@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@collabora.com \
--cc=hans.verkuil@cisco.com \
--cc=kernel@collabora.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=myy@miouyouyou.fr \
--cc=nicolas.dufresne@collabora.com \
--cc=robh+dt@kernel.org \
--cc=tfiga@chromium.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 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).