public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Alex Bee <knaerzche@gmail.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-media@vger.kernel.org,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Rob Herring <robh@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Subject: Re: (subset) [PATCH 0/3] Add VPU support for RK3128
Date: Wed, 28 Aug 2024 12:24:38 +0200	[thread overview]
Message-ID: <14376251.lVVuGzaMjS@diego> (raw)
In-Reply-To: <8a5f1856-823b-4cf7-a9fa-1dc6b9b54cd2@gmail.com>

Am Sonntag, 4. August 2024, 18:42:13 CEST schrieb Alex Bee:
> Hi Heiko
> 
> Am 28.05.24 um 17:09 schrieb Heiko Stuebner:
> > On Thu, 23 May 2024 20:56:30 +0200, Alex Bee wrote:
> >> Similar to most Rockchip SoCs RK312x have hantro G1 based decoder and a
> >> hantro H1 based encoder with attached iommu.
> >>
> >> The existing drivers can be used as-is.
> >>
> >> Fluster scores:
> >>    - FFmpeg:
> >>      - H.264: 127/135
> >>      - VP8:    59/61
> >>    - GStreamer:
> >>      - H.264: 129/135
> >>      - VP8:    59/61
> >>
> >> [...]
> > Applied, thanks!
> >
> > [2/3] soc: rockchip: grf: Set RK3128's vpu main clock
> >        commit: b465223129f951d110e633a305085bd8430d7df0
> I just noticed this patch didn't make it in 6.11-rc1. While it's not really
> important for this patch as the media mainainters didn't manage to apply
> the vpu bindings patch for 6.11 anyways, it looks like all commits of your
> v6.11-armsoc/drivers aren't merged. I still haven't fully understand how
> the SoC tree *really* works, but I couldn't find a PR for this branch [0].

That was me actually forgetting that branch :-( .

With the rk3128 vpu-binding getting merged today, I just moved that
onwards to 6.12 too. I guess this time I shouln't forget ;-)


Heiko




  reply	other threads:[~2024-08-28 10:24 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
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 [this message]
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=14376251.lVVuGzaMjS@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 \
    /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