mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Icenowy Zheng <uwu@icenowy.me>, Han Gao <rabenda.cn@gmail.com>
Subject: Re: [PATCH -next 1/2] drm: verisilicon: add max cursor size to HWDB
Date: Tue, 10 Mar 2026 10:10:29 +0100	[thread overview]
Message-ID: <937580b6-7433-41e8-9d65-e84385b7b4dd@suse.de> (raw)
In-Reply-To: <20260309085302.3132732-2-zhengxingda@iscas.ac.cn>

Hi

Am 09.03.26 um 09:53 schrieb Icenowy Zheng:
> Different display controller variants support different maximum cursor
> size. All known DC8200 variants support both 32x32 and 64x64, but some
> DC8000 variants support either only 32x32 or up to 256x256.
>
> The minimum size is fixed at 32 and only PoT square sizes are supported.
>
> Add the max cursor size field to HWDB and fill all entries with 64.
>
> Signed-off-by: Icenowy Zheng <zhengxingda@iscas.ac.cn>
> ---
>   drivers/gpu/drm/verisilicon/vs_hwdb.c | 4 ++++
>   drivers/gpu/drm/verisilicon/vs_hwdb.h | 1 +
>   2 files changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/verisilicon/vs_hwdb.c b/drivers/gpu/drm/verisilicon/vs_hwdb.c
> index 09336af0900ae..2a0f7c59afa3a 100644
> --- a/drivers/gpu/drm/verisilicon/vs_hwdb.c
> +++ b/drivers/gpu/drm/verisilicon/vs_hwdb.c
> @@ -95,6 +95,7 @@ static struct vs_chip_identity vs_chip_identities[] = {
>   		.customer_id = ~0U,
>   
>   		.display_count = 2,
> +		.max_cursor_size = 64,
>   		.formats = &vs_formats_no_yuv444,
>   	},
>   	{
> @@ -103,6 +104,7 @@ static struct vs_chip_identity vs_chip_identities[] = {
>   		.customer_id = 0x30B,
>   
>   		.display_count = 2,
> +		.max_cursor_size = 64,
>   		.formats = &vs_formats_no_yuv444,
>   	},
>   	{
> @@ -111,6 +113,7 @@ static struct vs_chip_identity vs_chip_identities[] = {
>   		.customer_id = 0x310,
>   
>   		.display_count = 2,
> +		.max_cursor_size = 64,
>   		.formats = &vs_formats_with_yuv444,
>   	},
>   	{
> @@ -119,6 +122,7 @@ static struct vs_chip_identity vs_chip_identities[] = {
>   		.customer_id = 0x311,
>   
>   		.display_count = 2,
> +		.max_cursor_size = 64,
>   		.formats = &vs_formats_no_yuv444,
>   	},
>   };
> diff --git a/drivers/gpu/drm/verisilicon/vs_hwdb.h b/drivers/gpu/drm/verisilicon/vs_hwdb.h
> index 92192e4fa0862..c54c9326c1681 100644
> --- a/drivers/gpu/drm/verisilicon/vs_hwdb.h
> +++ b/drivers/gpu/drm/verisilicon/vs_hwdb.h
> @@ -20,6 +20,7 @@ struct vs_chip_identity {
>   	u32 customer_id;
>   
>   	u32 display_count;
> +	int32_t max_cursor_size;

Just 'unsigned int'.

BTW the other fields should have used regular C types unless they are 
required to have a certain size.

I would also store this as max_cursor_width and max_cursor_height. The 
term size somehow implies "raw size in bytes".

Best regards
Thomas

>   	const struct vs_formats *formats;
>   };
>   

-- 
--
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)



  reply	other threads:[~2026-03-10  9:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09  8:53 [PATCH -next 0/2] drm: verisilicon: add hardware cursor support Icenowy Zheng
2026-03-09  8:53 ` [PATCH -next 1/2] drm: verisilicon: add max cursor size to HWDB Icenowy Zheng
2026-03-10  9:10   ` Thomas Zimmermann [this message]
2026-03-10  9:56     ` Thomas Zimmermann
2026-03-09  8:53 ` [PATCH -next 2/2] drm: verisilicon: add support for cursor planes Icenowy Zheng
2026-03-10  9:54   ` Thomas Zimmermann
2026-03-24  5:34     ` Icenowy Zheng
2026-03-24  7:45       ` Thomas Zimmermann
2026-03-24  7:49         ` Icenowy Zheng

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=937580b6-7433-41e8-9d65-e84385b7b4dd@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=rabenda.cn@gmail.com \
    --cc=simona@ffwll.ch \
    --cc=uwu@icenowy.me \
    --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

all inboxes | Powered by JetHome®