From: Thomas Zimmermann <tzimmermann@suse.de>
To: Icenowy Zheng <zhengxingda@iscas.ac.cn>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH drm-misc-next v4 0/4] drm: verisilicon: convert drm_format to vs_format in atomic_check
Date: Mon, 4 May 2026 13:45:36 +0200 [thread overview]
Message-ID: <fcbb98f2-96d4-4bfc-8701-85d802856972@suse.de> (raw)
In-Reply-To: <c6a4439d757a812994c4a0314a52f236ea7a9b38.camel@iscas.ac.cn>
Hi
Am 02.05.26 um 15:47 schrieb Icenowy Zheng:
> 在 2026-03-31二的 08:27 +0200,Thomas Zimmermann写道:
>> Hi,
>>
>> I only looked briefly over the update, but it seems good now.
> Could you have a more thorough look on this patchset (and if possible,
> apply it)?
Merged now. I thought this got in already.
Best regards
Thomas
>
> Thanks
> Icenowy
>
>> Best regards
>> Thomas
>>
>>
>> Am 31.03.26 um 08:01 schrieb Icenowy Zheng:
>>> This patchset tries to move the process of converting drm_format to
>>> vs_format into plane's atomic_check callback (instead of the
>>> atomic_commit one, which the process currently sits) for more
>>> proper
>>> error handling (because atomic_commit cannot fail).
>>>
>>> In addition, because of the original flow of primary plane's
>>> atomic_check seems to be flawed, it's also updated before filling
>>> vs_format is added there.
>>>
>>> Icenowy Zheng (4):
>>> drm: verisilicon: make vs_format conversion function return int
>>> drm: verisilicon: subclass drm_plane_state
>>> drm: verisilicon: call atomic helper's plane state check even if
>>> no
>>> CRTC
>>> drm: verisilicon: fill plane's vs_format in atomic_check
>>>
>>> drivers/gpu/drm/verisilicon/vs_plane.c | 54
>>> ++++++++++++++++++-
>>> drivers/gpu/drm/verisilicon/vs_plane.h | 18 ++++++-
>>> .../gpu/drm/verisilicon/vs_primary_plane.c | 48 ++++++++++----
>>> ---
>>> 3 files changed, 98 insertions(+), 22 deletions(-)
>>>
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)
prev parent reply other threads:[~2026-05-04 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 6:01 [PATCH drm-misc-next v4 0/4] drm: verisilicon: convert drm_format to vs_format in atomic_check Icenowy Zheng
2026-03-31 6:01 ` [PATCH drm-misc-next v4 1/4] drm: verisilicon: make vs_format conversion function return int Icenowy Zheng
2026-03-31 6:01 ` [PATCH drm-misc-next v4 2/4] drm: verisilicon: subclass drm_plane_state Icenowy Zheng
2026-03-31 6:01 ` [PATCH drm-misc-next v4 3/4] drm: verisilicon: call atomic helper's plane state check even if no CRTC Icenowy Zheng
2026-03-31 6:01 ` [PATCH drm-misc-next v4 4/4] drm: verisilicon: fill plane's vs_format in atomic_check Icenowy Zheng
2026-03-31 6:27 ` [PATCH drm-misc-next v4 0/4] drm: verisilicon: convert drm_format to " Thomas Zimmermann
2026-05-02 13:47 ` Icenowy Zheng
2026-05-04 11:45 ` Thomas Zimmermann [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=fcbb98f2-96d4-4bfc-8701-85d802856972@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=zhengxingda@iscas.ac.cn \
/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