From: Detlev Casanova <detlev.casanova@collabora.com>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Jonas Karlman <jonas@kwiboo.se>
Cc: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Heiko Stuebner <heiko@sntech.de>, 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 v2 1/7] media: rkvdec: Add HEVC backend
Date: Mon, 18 Aug 2025 04:25:58 -0400 [thread overview]
Message-ID: <6183937.lOV4Wx5bFT@earth> (raw)
In-Reply-To: <d7446ed8-4af1-475f-88e0-07025c60d0b1@kwiboo.se>
Hi Jonas,
On Sunday, 17 August 2025 12:39:01 EDT Jonas Karlman wrote:
> Hi Detlev,
>
> On 8/12/2025 9:54 PM, Detlev Casanova wrote:
> > On Tuesday, 12 August 2025 09:07:33 EDT Nicolas Dufresne wrote:
> >> Le mardi 12 août 2025 à 02:58 +0200, Jonas Karlman a écrit :
> >>> Hi Nicolas,
> >>>
> >>> On 8/11/2025 11:07 PM, Nicolas Dufresne wrote:
> >>>> First pass of review,
> >>>>
> >>>> There is obvious conflict between Detlev RK3388/3576 series, please
> >>>> coordinate. By picking the same direction, the common code can be split
> >>>> from platform code, and then both sets can share that common code and
> >>>> avoid conflicts.>
> >>>
> >>> Yes, it is very unfortunate that Detlev did not base the work on v1 of
> >>> this series, this has been sitting idle on the list for almost 2 years
> >>> only waiting on its dependent H264 High10/4:2:2 series to be merged.
> >>>
> >>> Most feedback for v1 was related to unstaging and the series could be
> >>> applied clean until iommu detach/attach was introduced very recently.
> >>>
> >>> This series has also been referenced in multiple threads related to
> >>> rkvdec2 work, most recent at [1]. Unfortunately, I have missed both v1
> >>> and v2 of Detlev's new rkvdec2 series, and was not able to send a v2 of
> >>> this until now due to family tragedy.
> >>>
> >>> I will take a closer look at Detlev's new rkvdec2 series and see what I
> >>> can do in a v3 to ease any merge conflicts.
> >>
> >> All in all, I'd like to have both of these series ready for 6.18. To
> >> avoid
> >> the need for dependant series, I can pick top patches if the preparation
> >> is
> >> properly split from the platform specific code. Please make you
> >> recommendation.
> >>
> >> My main concern at the moment is the back and forth from register to
> >> structure, Detlev already ported everything else to structures, so
> >> porting
> >> a single codec for a single SoC seems like the least amount of work. I'd
> >> like to ear if any of you would be willing to convert it. This way I can
> >> land the conversion early, and we remove one massive clash between the
> >> two
> >> sets.
> >
> > The conversion won't be too difficult to manage, I can do it as I did for
> > h264 and add that to my serie over this one.
>
> Thanks, I very much appreciate that!, I won't have time to look into a
> conversion until at earliest next weekend.
I pushed a branch with my series rebased on yours[1]. It ports the hevc code
to using structs (for registers).
Also move the cabac table and common hevc functions.
Reports indicate that all works well :)
> > As my series is already doing a conversion, I'm not against keeping this
> > one without structs and simply do the conversion later, even if that
> > means merging code we know will change later.
> >
> > I'd also like to mention that currently, my serie changes the writel to
> > structs only for the registers, not for PPS and SPS.
> > So I don't mind keeping that part as is for rkvdec-hevc.
> >
> > For the variants support, I can also merge in my changes: my rkvdec_config
> > would just become an extention your rkvdec_variant.
> >
> > Finally, this series has been here for longer than mine, so it's only fair
> > to have me rebase mine, especially because it means doing a bit more of
> > what I already did.
>
> Great, I will try to get a v3 out in next few days after addressing some
> of the feedback.
I will rebase on your v3 and send my v3 when this one is accepted.
[1]: https://gitlab.collabora.com/detlev/linux/-/commits/add-vdpu381-and-383-to-rkvdec-v3
Regards,
Detlev.
next prev parent reply other threads:[~2025-08-18 8:26 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 21:24 [PATCH v2 0/7] media: rkvdec: Add HEVC backend Jonas Karlman
2025-08-10 21:24 ` [PATCH v2 1/7] " Jonas Karlman
2025-08-11 19:12 ` Nicolas Dufresne
2025-08-11 19:46 ` Jonas Karlman
2025-08-11 20:27 ` Nicolas Dufresne
2025-08-11 21:07 ` Nicolas Dufresne
2025-08-12 0:58 ` Jonas Karlman
2025-08-12 13:07 ` Nicolas Dufresne
2025-08-12 19:54 ` Detlev Casanova
2025-08-17 16:39 ` Jonas Karlman
2025-08-18 8:25 ` Detlev Casanova [this message]
2025-08-12 20:10 ` Detlev Casanova
2025-08-17 16:46 ` Jonas Karlman
2025-08-29 20:22 ` Nicolas Dufresne
2025-09-03 7:28 ` Jonas Karlman
2025-09-03 13:44 ` Nicolas Dufresne
2025-08-10 21:24 ` [PATCH v2 2/7] media: rkvdec: Add variants support Jonas Karlman
2025-08-11 21:11 ` Nicolas Dufresne
2025-08-10 21:24 ` [PATCH v2 3/7] media: rkvdec: Implement capability filtering Jonas Karlman
2025-08-11 21:17 ` Nicolas Dufresne
2025-08-10 21:24 ` [PATCH v2 4/7] media: rkvdec: Add RK3288 variant Jonas Karlman
2025-08-11 21:17 ` Nicolas Dufresne
2025-08-10 21:24 ` [PATCH v2 5/7] media: rkvdec: Disable QoS for HEVC and VP9 on RK3328 Jonas Karlman
2025-08-11 21:25 ` Nicolas Dufresne
2025-08-11 22:22 ` Jonas Karlman
2025-08-12 12:47 ` Nicolas Dufresne
2025-08-11 23:08 ` Jonas Karlman
2025-08-12 13:00 ` Nicolas Dufresne
2025-08-17 16:18 ` Jonas Karlman
2025-08-10 21:24 ` [PATCH v2 6/7] media: dt-bindings: rockchip,vdec: Add RK3288 compatible Jonas Karlman
2025-08-10 21:24 ` [PATCH v2 7/7] ARM: dts: rockchip: Add vdec node for RK3288 Jonas Karlman
2025-08-11 21:52 ` [PATCH v2 0/7] media: rkvdec: Add HEVC backend Nicolas Dufresne
2025-08-12 0:00 ` Jonas Karlman
2025-08-12 12:38 ` Nicolas Dufresne
2025-08-12 12:44 ` Nicolas Dufresne
2025-08-12 17:31 ` Jonas Karlman
2025-08-12 18:26 ` Nicolas Dufresne
2025-08-12 18:52 ` Nicolas Dufresne
2025-08-17 16:33 ` Jonas Karlman
2025-08-12 19:57 ` Detlev Casanova
2025-08-12 21:11 ` Nicolas Dufresne
2025-08-12 12:11 ` Diederik de Haas
2025-08-12 12:55 ` Diederik de Haas
2025-08-12 13:27 ` Nicolas Dufresne
2025-08-12 14:09 ` Diederik de Haas
2025-08-14 21:25 ` Alex Bee
2025-08-12 17:11 ` Jonas Karlman
2025-08-12 18:28 ` Diederik de Haas
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=6183937.lOV4Wx5bFT@earth \
--to=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=knaerzche@gmail.com \
--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=nicolas.dufresne@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).