From: Michael Tretter <m.tretter@pengutronix.de>
To: devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
jacob-chen@iotwrt.com, ezequiel@vanguardiasur.com.ar,
robh+dt@kernel.org
Cc: krzysztof.kozlowski+dt@linaro.org, heiko@sntech.de,
michael.riesch@wolfvision.net,
linux-arm-kernel@lists.infradead.org, m.tretter@pengutronix.de,
kernel@pengutronix.de
Subject: [PATCH 0/2] media: rockchip: rga: Add rk3568 support
Date: Mon, 21 Nov 2022 16:17:53 +0100 [thread overview]
Message-ID: <20221121151755.2072816-1-m.tretter@pengutronix.de> (raw)
The RGA2 on the Rockchip rk3568 is the same core as the RGA2 on the Rockchip
rk3288.
This series adds the necessary device tree binding and node in the device tree
to enable the RGA2 on the Rockchip rk3568.
I tested the driver with the GStreamer v4l2convert element on a ROCK3A board.
Michael
Michael Tretter (2):
media: dt-bindings: media: rockchip-rga: add rockchip,rk3568-rga
arm64: dts: rockchip: Add RGA2 support to rk356x
.../devicetree/bindings/media/rockchip-rga.yaml | 4 +++-
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 11 +++++++++++
2 files changed, 14 insertions(+), 1 deletion(-)
--
2.30.2
next reply other threads:[~2022-11-21 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 15:17 Michael Tretter [this message]
2022-11-21 15:17 ` [PATCH 1/2] media: dt-bindings: media: rockchip-rga: add rockchip,rk3568-rga Michael Tretter
2022-11-21 16:26 ` Krzysztof Kozlowski
2022-11-21 15:17 ` [PATCH 2/2] arm64: dts: rockchip: Add RGA2 support to rk356x Michael Tretter
2022-11-21 16:01 ` Shengyu Qu
2022-11-21 16:41 ` Michael Tretter
2022-11-21 17:13 ` Shengyu Qu
2022-11-21 17:30 ` Ezequiel Garcia
2022-11-21 23:10 ` Peter Geis
2022-11-22 19:47 ` Nicolas Frattaroli
2022-11-23 9:28 ` Michael Tretter
2023-01-17 12:41 ` Michael Tretter
2023-01-18 0:01 ` Nicolas Frattaroli
2023-01-19 12:15 ` 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=20221121151755.2072816-1-m.tretter@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=jacob-chen@iotwrt.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
--cc=robh+dt@kernel.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).