public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laura Nao <laura.nao@collabora.com>
To: aliceryhl@google.com
Cc: a.hindborg@kernel.org, airlied@gmail.com,
	bjorn3_gh@protonmail.com, boqun@kernel.org,
	boris.brezillon@collabora.com, dakr@kernel.org,
	daniel.almeida@collabora.com, dri-devel@lists.freedesktop.org,
	gary@garyguo.net, kernel@collabora.com, laura.nao@collabora.com,
	linux-kernel@vger.kernel.org, lossin@kernel.org,
	nouveau@lists.freedesktop.org, ojeda@kernel.org,
	rust-for-linux@vger.kernel.org, simona@ffwll.ch,
	tmgross@umich.edu
Subject: Re: [PATCH v2 1/1] rust: drm: add RENDER_CAPABILITY flag for render node support
Date: Wed,  6 May 2026 10:41:47 +0200	[thread overview]
Message-ID: <20260506084147.19907-1-laura.nao@collabora.com> (raw)
In-Reply-To: <afnMTfVfGq_iLXov@google.com>

Hi Alice,

On 5/5/26 12:54, Alice Ryhl wrote:
>
> I think it would be nice for this documentation to elaborate more on
> what this feature actually does. After all, it clearly took us a while
> to understand it, so probably others are confused too.
>
> Something along these lines:
>
> /// Sets the `DRIVER_RENDER` feature for this driver.
> /// 
> /// When enabled, the driver exposes `/dev/dri/renderDXX` render nodes to
> /// userspace. The render node is an alternate low-priviledge way to access
> /// the driver, which is enforced on a per-ioctl level. Userspace processes
> /// that open the render node can only invoke ioctls explicitly listed as
> /// usable from the render node, whereas userspace processes using the
> /// master node can invoke any ioctl.
> const RENDER_CAPABILITY: bool = false;
>

Agreed, the extra documentation will definitely help clarify the flag 
purpose. Thanks for the feedback!

> Also, I'd probably call this const `FEAT_RENDER` for consistency / to
> make it show up in grep.
>

Right, using FEAT_RENDER in the Driver trait as well sounds good to me.
I'll submit a new revision with these changes.

Best,

Laura

      reply	other threads:[~2026-05-06  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  9:23 [PATCH v2 0/1] DRM 'feature' support for DRM drivers Laura Nao
2026-05-05  9:23 ` [PATCH v2 1/1] rust: drm: add RENDER_CAPABILITY flag for render node support Laura Nao
2026-05-05 10:54   ` Alice Ryhl
2026-05-06  8:41     ` Laura Nao [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=20260506084147.19907-1-laura.nao@collabora.com \
    --to=laura.nao@collabora.com \
    --cc=a.hindborg@kernel.org \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=boris.brezillon@collabora.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tmgross@umich.edu \
    /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