From: Alex Bee <knaerzche@gmail.com>
To: Jianfeng Liu <liujianfeng1994@gmail.com>,
ezequiel@vanguardiasur.com.ar, p.zabel@pengutronix.de,
mchehab@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
heiko@sntech.de, sfr@canb.auug.org.au
Cc: linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/3] Add hantro g1 video decoder support for RK3588
Date: Sat, 30 Dec 2023 10:46:42 +0100 [thread overview]
Message-ID: <35df6456-2bc2-415d-bc61-09e4b440e2ac@gmail.com> (raw)
In-Reply-To: <20231228131617.3411561-1-liujianfeng1994@gmail.com>
Hi, Jianfeng
Am 28.12.23 um 14:16 schrieb Jianfeng Liu:
> This is the v2 version of this series adding hantro g1 video decoder
> support for rk3588.
>
> Changes in v2:
> - Fix alphabetical order in patch1 and patch3
> - Sort device tree node by bus-address
> - Drop rk3588_vpu_variant fron v1 because that is exactly the same as rk3568_vpu_variant
if the RK3568 and RK3588 variants match, patch [1/3] is not necessary. Just
document a additional compatible in a similar way it's being done for
rk3188/rk3066 or rk3228/rk3399.
If there are ever differences we don't know about yet, a additional variant
can still be added in the driver.
Alex
> - Link to v1: https://lore.kernel.org/all/20231227173911.3295410-1-liujianfeng1994@gmail.com
>
> Jianfeng Liu (3):
> media: verisilicon: Add support for Hantro G1 on RK3588
> arm64: dts: rockchip: Add Hantro G1 VPU support for RK3588
> dt-bindings: media: rockchip-vpu: Add RK3588 compatible
>
> .../bindings/media/rockchip-vpu.yaml | 1 +
> arch/arm64/boot/dts/rockchip/rk3588s.dtsi | 20 +++++++++++++++++++
> .../media/platform/verisilicon/hantro_drv.c | 1 +
> 3 files changed, 22 insertions(+)
>
next prev parent reply other threads:[~2023-12-30 9:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 13:16 [PATCH v2 0/3] Add hantro g1 video decoder support for RK3588 Jianfeng Liu
2023-12-28 13:16 ` [PATCH v2 1/3] media: verisilicon: Add support for Hantro G1 on RK3588 Jianfeng Liu
2023-12-28 13:16 ` [PATCH v2 2/3] arm64: dts: rockchip: Add Hantro G1 VPU support for RK3588 Jianfeng Liu
2023-12-29 11:02 ` Hugh Cole-Baker
2023-12-30 10:20 ` amazingfate
2023-12-28 13:16 ` [PATCH v2 3/3] dt-bindings: media: rockchip-vpu: Add RK3588 compatible Jianfeng Liu
2023-12-30 16:06 ` Krzysztof Kozlowski
2023-12-30 17:17 ` amazingfate
2023-12-29 11:01 ` [PATCH v2 0/3] Add hantro g1 video decoder support for RK3588 Hugh Cole-Baker
2023-12-30 9:52 ` amazingfate
2023-12-30 11:49 ` Jonas Karlman
2023-12-30 15:31 ` amazingfate
2023-12-30 20:12 ` Jonas Karlman
2023-12-30 9:46 ` Alex Bee [this message]
2023-12-30 10:03 ` amazingfate
2023-12-30 10:09 ` amazingfate
2023-12-30 17:23 ` amazingfate
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=35df6456-2bc2-415d-bc61-09e4b440e2ac@gmail.com \
--to=knaerzche@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--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=liujianfeng1994@gmail.com \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).