From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: Christopher Obbard <chris.obbard@collabora.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Heiko Stuebner <heiko@sntech.de>,
Johan Jonker <jbx6244@gmail.com>, Alex Bee <knaerzche@gmail.com>,
Elaine Zhang <zhangqing@rock-chips.com>,
linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: Add vdec support for RK3328
Date: Fri, 22 Apr 2022 14:43:01 -0300 [thread overview]
Message-ID: <YmLpJQwdcSPHgZag@eze-laptop> (raw)
In-Reply-To: <20220422133803.989256-4-chris.obbard@collabora.com>
On Fri, Apr 22, 2022 at 02:38:03PM +0100, Christopher Obbard wrote:
> The RK3328 has an vdec device with dedicated iommu.
> Describe the device and required power-domains in the
> devicetree.
>
> Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>
Reviewed-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> ---
> arch/arm64/boot/dts/rockchip/rk3328.dtsi | 25 +++++++++++++++++++++++-
> 1 file changed, 24 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> index f8ef149fedad..390e1e4a8fc9 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> @@ -306,6 +306,10 @@ power-domain@RK3328_PD_HEVC {
> };
> power-domain@RK3328_PD_VIDEO {
> reg = <RK3328_PD_VIDEO>;
> + clocks = <&cru ACLK_RKVDEC>,
> + <&cru HCLK_RKVDEC>,
> + <&cru SCLK_VDEC_CABAC>,
> + <&cru SCLK_VDEC_CORE>;
> #power-domain-cells = <0>;
> };
> power-domain@RK3328_PD_VPU {
> @@ -660,6 +664,25 @@ vpu_mmu: iommu@ff350800 {
> power-domains = <&power RK3328_PD_VPU>;
> };
>
> + vdec: video-codec@ff360000 {
> + compatible = "rockchip,rk3328-vdec", "rockchip,rk3399-vdec";
> + reg = <0x0 0xff360000 0x0 0x400>;
> + interrupts = <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cru ACLK_RKVDEC>, <&cru HCLK_RKVDEC>,
> + <&cru SCLK_VDEC_CABAC>, <&cru SCLK_VDEC_CORE>;
> + clock-names = "axi", "ahb", "cabac", "core";
> + assigned-clocks = <&cru ACLK_RKVDEC>, <&cru SCLK_VDEC_CABAC>,
> + <&cru SCLK_VDEC_CORE>;
> + assigned-clock-rates = <400000000>, <400000000>, <300000000>;
> + resets = <&cru SRST_VDEC_A>, <&cru SRST_VDEC_H>,
> + <&cru SRST_VDEC_CABAC>, <&cru SRST_VDEC_CORE>,
> + <&cru SRST_VDEC_NIU_A>, <&cru SRST_VDEC_NIU_H>;
> + reset-names = "video_a", "video_h", "video_cabac", "video_core",
> + "niu_a", "niu_h";
> + iommus = <&vdec_mmu>;
> + power-domains = <&power RK3328_PD_VIDEO>;
> + };
> +
> vdec_mmu: iommu@ff360480 {
> compatible = "rockchip,iommu";
> reg = <0x0 0xff360480 0x0 0x40>, <0x0 0xff3604c0 0x0 0x40>;
> @@ -667,7 +690,7 @@ vdec_mmu: iommu@ff360480 {
> clocks = <&cru ACLK_RKVDEC>, <&cru HCLK_RKVDEC>;
> clock-names = "aclk", "iface";
> #iommu-cells = <0>;
> - status = "disabled";
> + power-domains = <&power RK3328_PD_VIDEO>;
> };
>
> vop: vop@ff370000 {
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-04-22 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 13:38 [PATCH 0/3] Rockchip RK3328 VDEC support Christopher Obbard
2022-04-22 13:38 ` [PATCH 1/3] media: dt-bindings: media: rockchip-vdec: Add RK3328 compatible Christopher Obbard
2022-04-22 16:48 ` Ezequiel Garcia
2022-04-23 11:10 ` Krzysztof Kozlowski
2022-04-23 17:31 ` Krzysztof Kozlowski
2022-04-25 9:53 ` Christopher Obbard
2022-04-25 9:54 ` Krzysztof Kozlowski
2022-04-22 13:38 ` [PATCH 2/3] arm64: dts: rockchip: Rename vdec_mmu node for RK3328 Christopher Obbard
2022-04-22 17:42 ` Ezequiel Garcia
2022-04-22 13:38 ` [PATCH 3/3] arm64: dts: rockchip: Add vdec support " Christopher Obbard
2022-04-22 17:43 ` Ezequiel Garcia [this message]
2022-04-23 17:33 ` Krzysztof Kozlowski
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=YmLpJQwdcSPHgZag@eze-laptop \
--to=ezequiel@vanguardiasur.com.ar \
--cc=chris.obbard@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=kernel@collabora.com \
--cc=knaerzche@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=zhangqing@rock-chips.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).