From: Johan Jonker <jbx6244@gmail.com>
To: Michael Riesch <michael.riesch@wolfvision.net>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: s.hauer@pengutronix.de, benjamin.gaignard@collabora.com,
hjc@rock-chips.com, heiko@sntech.de, pgwipeout@gmail.com
Subject: Re: [PATCH] arm64: dts: rockchip: enable vop2 and hdmi tx on quartz64a
Date: Thu, 25 Nov 2021 20:44:16 +0100 [thread overview]
Message-ID: <db4731a5-56b9-f1f8-2d3f-c62bb7e3b91a@gmail.com> (raw)
In-Reply-To: <20211117154429.2274443-1-michael.riesch@wolfvision.net>
On 11/17/21 4:44 PM, Michael Riesch wrote:
> Enable the RK356x Video Output Processor (VOP) 2 on the Pine64
> Quartz64 Model A.
>
> Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
> ---
> .../boot/dts/rockchip/rk3566-quartz64-a.dts | 24 +++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.dts b/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.dts
> index 4d4b2a301b1a..9fba790c6af4 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.dts
> @@ -205,6 +205,16 @@ &gmac1m0_clkinout
> status = "okay";
> };
>
> +&hdmi {
> + status = "okay";
> + avdd-0v9-supply = <&vdda_0v9>;
> + avdd-1v8-supply = <&vcc_1v8>;
Heiko's sort rules:
compatible
reg
interrupts
[alphabetical]
status [if needed]
> +};
> +
> +&hdmi_in_vp0 {
> + status = "okay";
> +};
> +
> &i2c0 {
> status = "okay";
>
> @@ -546,3 +556,17 @@ bluetooth {
> &uart2 {
> status = "okay";
> };
> +
> +&vop {
> + status = "okay";
status below
> + assigned-clocks = <&cru DCLK_VOP0>, <&cru DCLK_VOP1>;
> + assigned-clock-parents = <&pmucru PLL_HPLL>, <&cru PLL_VPLL>;
> +};
> +
> +&vop_mmu {
> + status = "okay";
> +};
> +
> +&vp0_out_hdmi {
> + status = "okay";
> +};
>
prev parent reply other threads:[~2021-11-25 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211117143347.314294-11-s.hauer@pengutronix.de>
2021-11-17 15:44 ` Michael Riesch
2021-11-25 19:44 ` Johan Jonker [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=db4731a5-56b9-f1f8-2d3f-c62bb7e3b91a@gmail.com \
--to=jbx6244@gmail.com \
--cc=benjamin.gaignard@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
--cc=pgwipeout@gmail.com \
--cc=s.hauer@pengutronix.de \
/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®