From: Michael Tretter <m.tretter@pengutronix.de>
To: Shengyu Qu <wiagn233@outlook.com>
Cc: devicetree@vger.kernel.org, ezequiel@vanguardiasur.com.ar,
heiko@sntech.de, jacob-chen@iotwrt.com, kernel@pengutronix.de,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
michael.riesch@wolfvision.net, robh+dt@kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add RGA2 support to rk356x
Date: Mon, 21 Nov 2022 17:41:16 +0100 [thread overview]
Message-ID: <20221121164116.GE15565@pengutronix.de> (raw)
In-Reply-To: <TY3P286MB2611FB223B1CC437B01BD984980A9@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>
Hi,
On Tue, 22 Nov 2022 00:01:28 +0800, Shengyu Qu wrote:
> Someone from pine64 discord found that RGA2 doesn't work properly on over
>
> 4GB memory RK3568 devices. Are you sure current driver works now?
I am absolutely sure that the driver works on a 2GB ROCK3A board.
Unfortunately, I don't have a device with 4GB or more memory and I cannot test
the driver with such a device.
As the documentation for the RGA2 is the same in the TRM of the rk3288 and
rk3568, I would guess that the driver doesn't work on a rk3288 with more than
4GB (if there is such a thing) either and the driver needs to be fixed for
both SoCs.
Michael
next prev parent reply other threads:[~2022-11-21 16:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 15:17 [PATCH 0/2] media: rockchip: rga: Add rk3568 support Michael Tretter
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 [this message]
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=20221121164116.GE15565@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 \
--cc=wiagn233@outlook.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).