From: "Heiko Stübner" <heiko@sntech.de>
To: Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alex Bee <knaerzche@gmail.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
Subject: Re: [PATCH 1/3] dt-bindings: media: rockchip,vpu: Document RK3128 compatible
Date: Thu, 01 Aug 2024 12:36:28 +0200 [thread overview]
Message-ID: <23279441.ssLaC8jLEa@diego> (raw)
In-Reply-To: <20240528083747.z55laxnmioorzaru@basti-XPS-13-9310>
Hey,
Am Dienstag, 28. Mai 2024, 10:37:47 CEST schrieb Sebastian Fricke:
> On 28.05.2024 10:19, Heiko Stübner wrote:
> >Am Donnerstag, 23. Mai 2024, 20:56:31 CEST schrieb Alex Bee:
> >> The integration for this SoC is similar to RK3066/RK3188.
> >>
> >> Document it's compatible.
> >>
> >> Signed-off-by: Alex Bee <knaerzche@gmail.com>
> >
> >Reviewed-by: Heiko Stuebner <heiko@sntech.de>
> >
> >Media people, can you apply this patch alone from the series?
>
> Yes, will do got this on my list already :).
as I'm going through my list of "waiting for ..." patches,
is this still on the radar?
As far as I can tell, it didn't make it into 6.11-rc1, but 6.12 would be
nice :-)
Thanks a lot
Heiko
> >> ---
> >> Documentation/devicetree/bindings/media/rockchip-vpu.yaml | 4 +++-
> >> 1 file changed, 3 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/Documentation/devicetree/bindings/media/rockchip-vpu.yaml b/Documentation/devicetree/bindings/media/rockchip-vpu.yaml
> >> index c57e1f488895..d1b47b14ca57 100644
> >> --- a/Documentation/devicetree/bindings/media/rockchip-vpu.yaml
> >> +++ b/Documentation/devicetree/bindings/media/rockchip-vpu.yaml
> >> @@ -26,7 +26,9 @@ properties:
> >> - rockchip,rk3568-vpu
> >> - rockchip,rk3588-av1-vpu
> >> - items:
> >> - - const: rockchip,rk3188-vpu
> >> + - enum:
> >> + - rockchip,rk3128-vpu
> >> + - rockchip,rk3188-vpu
> >> - const: rockchip,rk3066-vpu
> >> - items:
> >> - const: rockchip,rk3228-vpu
> >>
> >
> >
> >
> >
> >
>
next prev parent reply other threads:[~2024-08-01 10:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 18:56 [PATCH 0/3] Add VPU support for RK3128 Alex Bee
2024-05-23 18:56 ` [PATCH 1/3] dt-bindings: media: rockchip,vpu: Document RK3128 compatible Alex Bee
2024-05-23 20:34 ` Krzysztof Kozlowski
2024-05-28 8:19 ` Heiko Stübner
2024-05-28 8:37 ` Sebastian Fricke
2024-06-10 13:56 ` Alex Bee
2024-08-01 10:36 ` Heiko Stübner [this message]
2024-05-23 18:56 ` [PATCH 2/3] soc: rockchip: grf: Set RK3128's vpu main clock Alex Bee
2024-05-23 18:56 ` [PATCH 3/3] ARM: dts: rockchip: Add vpu nodes for RK3128 Alex Bee
2024-05-28 15:09 ` (subset) [PATCH 0/3] Add VPU support " Heiko Stuebner
2024-08-04 16:42 ` Alex Bee
2024-08-28 10:24 ` Heiko Stübner
2024-08-28 10:24 ` 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=23279441.ssLaC8jLEa@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--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=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sebastian.fricke@collabora.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).