Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Golle <daniel@makrotopia.org>
To: Christian Hewitt <christianshewitt@gmail.com>
Cc: Detlev Casanova <detlev.casanova@collabora.com>,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Shawn Lin <shawn.lin@rock-chips.com>,
	Michael Riesch <michael.riesch@collabora.com>,
	David Heidelberg <david@ixit.cz>, Marc Zyngier <maz@kernel.org>,
	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,
	Nicolas Dufresne <nicolas.dufresne@collabora.com>,
	Hans Verkuil <hverkuil+cisco@kernel.org>,
	Jonas Karlman <jonas@kwiboo.se>,
	Diederik de Haas <diederik@cknow-tech.com>,
	Dang Huynh <dang.huynh@mainlining.org>,
	Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
Subject: Re: [PATCH v5 0/5] media: rockchip: rkvdec: add support for the VDPU346 variant
Date: Sun, 22 Nov 2026 10:57:15 +0000	[thread overview]
Message-ID: <awLKiyI-z6wdTD4C@makrotopia.org> (raw)
In-Reply-To: <E8475BAC-F137-493E-B7AC-9C81FB158610@gmail.com>

On Sun, Nov 22, 2026 at 11:44:32AM +0400, Christian Hewitt wrote:
> > On 20 Nov 2026, at 9:36 pm, Daniel Golle <daniel@makrotopia.org> wrote:
> > 
> > This series adds the VDPU346 decoder of the RK3566 and RK3568 to the
> > rkvdec driver, for H.264 and HEVC. It continues Christian Hewitt's v3
> > [1]; in the v2 cover letter he offered to pass the series on. The
> > previous posting [2] carried no version in its subject and counts as
> > v4.
> 
> The original offer was directed at Detlev based on conversations with
> other Collabora folks who were hinting that he would be able to (and
> it would even be desirable to) fold VDPU346 patches into his work on
> VDPU381/383 which was in-flight at the time.

VDPU381/383 has landed shortly after your initial post, 10 months ago.

Your wording, on a public mailing list, reads

> [...] would be happy to pass the series over to a more experienced
> developer.

I may not have been active in media/drm that much, but am generally very
familiar with kernel development and consider myself reasonably skilled
with C (also "pre-Claude").

As all missing was running the validation suite (and the minimal changes
such as the clock change I've appended to the series) I thought
re-submitting it with the results of the validation suite run would be
the right thing to do.

> However he didn’t take
> the bait and it didn’t happen. The comment is also pre-Claude when my
> coding abilities were more rudimentary. The main reason for the long
> delay in following up has been the length of time it took for Detlev’s
> and related DRM series that permit wider testing to land; a vacation
> over the summer, and then Claude distracting me with a deep dive into
> the Amlogic and Rockchip media stacks that’s resulted in 300+ patches
> that need a proper plan for upstreaming else I’m going to annoy the
> already-overworked media/drm maintainers.

That particular bit, making VDPU436 work, doesn't depend on any of that
future work you may still want to submit. It's immediately useful and
can be tested independently.

> I don’t object to someone upstreaming my patches. I do object to the
> lack of outreach to check on my plans and patch status before blindly
> (and wrongly) assuming there were none.

I didn't mean to overstep you here -- but 10 months of silence and an
offer to hand over the series didn't seem to require any coordination.

> You will find later versions
> of my patches with fixes for changes in surrounding code (as I work
> on something broadly equivalent to drm-tip not Linux 6.18) and from
> further testing in my not-very-abandoned development tree:
> 
> https://github.com/chewitt/linux/commits/rockchip-7.4.y

I wasn't aware of yout Github tree which wasn't mentioned anywhere in
your previous submissions. It also seems that this tree has only been
published hours ago, and doesn't contain any changes related to rkvdec
beyond what is also published via the mailing lists.


      reply	other threads:[~2026-11-22 10:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 17:36 [PATCH v5 0/5] media: rockchip: rkvdec: add support for the VDPU346 variant Daniel Golle
2026-11-20 17:40 ` [PATCH v5 1/5] media: dt-bindings: rockchip: Add RK3568 Video Decoder bindings Daniel Golle
2026-11-20 20:19   ` Diederik de Haas
2026-11-20 20:24     ` Daniel Golle
2026-11-21 13:12   ` Krzysztof Kozlowski
2026-11-20 17:40 ` [PATCH v5 2/5] media: rkvdec: Add support for the VDPU346 variant Daniel Golle
2026-11-20 17:41 ` [PATCH v5 3/5] media: rkvdec: vdpu381: Program the read caches Daniel Golle
2026-11-20 21:20   ` Nicolas Dufresne
2026-11-20 17:41 ` [PATCH v5 4/5] arm64: dts: rockchip: Add the vdpu346 Video Decoders on RK356X Daniel Golle
2026-11-20 17:42 ` [PATCH v5 5/5] arm64: dts: rockchip: rk356x: Clock the vdec at 400 MHz Daniel Golle
2026-11-20 20:16 ` [PATCH v5 0/5] media: rockchip: rkvdec: add support for the VDPU346 variant Diederik de Haas
2026-11-22  7:44 ` Christian Hewitt
2026-11-22 10:57   ` Daniel Golle [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=awLKiyI-z6wdTD4C@makrotopia.org \
    --to=daniel@makrotopia.org \
    --cc=christianshewitt@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=dang.huynh@mainlining.org \
    --cc=david@ixit.cz \
    --cc=detlev.casanova@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=diederik@cknow-tech.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=heiko@sntech.de \
    --cc=hverkuil+cisco@kernel.org \
    --cc=jonas@kwiboo.se \
    --cc=krzk+dt@kernel.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=maz@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=michael.riesch@collabora.com \
    --cc=nicolas.dufresne@collabora.com \
    --cc=piotr.oniszczuk@gmail.com \
    --cc=robh@kernel.org \
    --cc=shawn.lin@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