The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Mel Henning" <mhenning@darkrefraction.com>
Cc: "Lyude Paul" <lyude@redhat.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Mary Guillemard" <mary@mary.zone>,
	<dri-devel@lists.freedesktop.org>,
	<nouveau@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] drm/nouveau: Add DRM_IOCTL_NOUVEAU_GET_ZCULL_INFO
Date: Fri, 13 Feb 2026 18:13:56 +0100	[thread overview]
Message-ID: <DGE03Z9YNGAW.3RUQ7P7L93HEE@kernel.org> (raw)
In-Reply-To: <20260205-zcull3-v2-2-ac572f38cc7b@darkrefraction.com>

On Thu Feb 5, 2026 at 7:56 PM CET, Mel Henning wrote:
> +int
> +nouveau_abi16_ioctl_get_zcull_info(ABI16_IOCTL_ARGS)
> +{
> +	struct nouveau_drm *drm = nouveau_drm(dev);
> +	struct nvkm_gr *gr = nvxx_gr(drm);
> +	struct drm_nouveau_get_zcull_info *out = data;
> +
> +	if (gr->has_zcull_info) {
> +		const struct nvkm_gr_zcull_info *i = &gr->zcull_info;
> +
> +		out->width_align_pixels = i->width_align_pixels;
> +		out->height_align_pixels = i->height_align_pixels;
> +		out->pixel_squares_by_aliquots = i->pixel_squares_by_aliquots;
> +		out->aliquot_total = i->aliquot_total;
> +		out->zcull_region_byte_multiplier = i->zcull_region_byte_multiplier;
> +		out->zcull_region_header_size = i->zcull_region_header_size;
> +		out->zcull_subregion_header_size = i->zcull_subregion_header_size;
> +		out->subregion_count = i->subregion_count;
> +		out->subregion_width_align_pixels = i->subregion_width_align_pixels;
> +		out->subregion_height_align_pixels = i->subregion_height_align_pixels;
> +		out->ctxsw_size = i->ctxsw_size;
> +		out->ctxsw_align = i->ctxsw_align;
> +
> +		return 0;
> +	} else {
> +		return -ENODEV;

ENODEV usually means that that device fell off the bus, I think ENOTTY would be
a better fit.

> +	}
> +}

  reply	other threads:[~2026-02-13 17:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 18:56 [PATCH v2 0/2] drm/nouveau: zcull support Mel Henning
2026-02-05 18:56 ` [PATCH v2 1/2] drm/nouveau: Fetch zcull info from device Mel Henning
2026-02-13 17:12   ` Danilo Krummrich
2026-02-13 21:48     ` M Henning
2026-02-13 22:22       ` Danilo Krummrich
2026-02-13 23:11         ` M Henning
2026-02-05 18:56 ` [PATCH v2 2/2] drm/nouveau: Add DRM_IOCTL_NOUVEAU_GET_ZCULL_INFO Mel Henning
2026-02-13 17:13   ` Danilo Krummrich [this message]
2026-02-13 22:06     ` M Henning

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=DGE03Z9YNGAW.3RUQ7P7L93HEE@kernel.org \
    --to=dakr@kernel.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lyude@redhat.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mary@mary.zone \
    --cc=mhenning@darkrefraction.com \
    --cc=mripard@kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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