Netdev List
 help / color / mirror / Atom feed
From: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
To: Zack McKevitt <zachary.mckevitt@oss.qualcomm.com>,
	dri-devel@lists.freedesktop.org, netdev@vger.kernel.org,
	riana.tauro@intel.com, aravind.iddamsetty@linux.intel.com,
	rodrigo.vivi@intel.com, raag.jadav@intel.com,
	simona.vetter@ffwll.ch, airlied@gmail.com, kuba@kernel.org,
	ogabbay@kernel.org, lizhi.hou@amd.com,
	karol.wachowski@linux.intel.com
Cc: carl.vanderlip@oss.qualcomm.com, troy.hanson@oss.qualcomm.com,
	youssef.abdulrahman@oss.qualcomm.com
Subject: Re: [PATCH v2 2/3] drm/drm_ras: Extend DRM RAS interface to include telemetry nodes
Date: Fri, 30 Oct 2026 10:45:18 -0600	[thread overview]
Message-ID: <6c2b6fdf-90b0-43f3-b5fe-97235aeb4219@oss.qualcomm.com> (raw)
In-Reply-To: <20261029203000.1763447-3-zachary.mckevitt@oss.qualcomm.com>

On 10/29/2026 2:29 PM, Zack McKevitt wrote:
> Add a new node type, attribute set, and doit/dump functions for
> performing telemetry read and write operations using the DRM RAS
> interface.
> 
> ynl-regen.sh was used to regenerate drm_ras_nl.c, drm_ras_nl.h, and
> include/uapi/drm/drm_ras.h from the drm_ras.yaml spec.
> 
> Signed-off-by: Zack McKevitt <zachary.mckevitt@oss.qualcomm.com>

One minor nit below.

Reviewed-by: Jeff Hugo <jeff.hugo@oss.qualcomm.com>

> diff --git a/Documentation/netlink/specs/drm_ras.yaml b/Documentation/netlink/specs/drm_ras.yaml
> index a88fdab7a1c7..a02aaed8772f 100644
> --- a/Documentation/netlink/specs/drm_ras.yaml
> +++ b/Documentation/netlink/specs/drm_ras.yaml
> @@ -16,11 +16,11 @@ definitions:
>       type: enum
>       name: node-type
>       value-start: 1
> -    entries: [error-counter]
> +    entries: [error-counter, telemetry]
>       doc: >-
> -         Type of the node. Currently, only error-counter nodes are
> -         supported, which expose reliability counters for a hardware/software
> -         component.
> +         Type of the node. The error-counter nodes expose reliability counters
> +         for a hardware/software component, and telemetry nodes expose an
> +         interface for reading and writing telemetry values to a device.
>   
>   attribute-sets:
>     -
> @@ -100,6 +100,34 @@ attribute-sets:
>           name: error-value
>           type: u32
>           doc: Current value of the error counter.
> +  -
> +    name: telemetry-attrs
> +    attributes:
> +      -
> +        name: node-id
> +        type: u32
> +        doc: >-
> +             Unique identifier for the node.
> +             Assigned dynamically by the DRM RAS core upon registration.
> +      -
> +        name: field
> +        type: u32
> +        doc:  Telemetry field to be read/written, e.g., SoC temp.
> +      -
> +        name: field-name
> +        type: string
> +        doc:  Name of the telemetry field defined by the device's uapi.

uapi -> uAPI
Might as well be consistent with the documentation elsewhere in this patch.



  reply	other threads:[~2026-10-30 16:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 20:29 [PATCH v2 0/3] Extend drm_ras for qaic telemetry Zack McKevitt
2026-10-29 20:29 ` [PATCH v2 1/3] drm/drm_ras: Remove admin-perm flag from list-nodes operation Zack McKevitt
2026-10-30 16:37   ` Jeff Hugo
2026-10-29 20:29 ` [PATCH v2 2/3] drm/drm_ras: Extend DRM RAS interface to include telemetry nodes Zack McKevitt
2026-10-30 16:45   ` Jeff Hugo [this message]
2026-10-29 20:30 ` [PATCH v2 3/3] accel/qaic: Add callbacks for DRM RAS netlink telemetry Zack McKevitt
2026-10-30 17:06   ` Jeff Hugo
2026-10-30 16:36 ` [PATCH v2 0/3] Extend drm_ras for qaic telemetry Jeff Hugo

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=6c2b6fdf-90b0-43f3-b5fe-97235aeb4219@oss.qualcomm.com \
    --to=jeff.hugo@oss.qualcomm.com \
    --cc=airlied@gmail.com \
    --cc=aravind.iddamsetty@linux.intel.com \
    --cc=carl.vanderlip@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=karol.wachowski@linux.intel.com \
    --cc=kuba@kernel.org \
    --cc=lizhi.hou@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogabbay@kernel.org \
    --cc=raag.jadav@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona.vetter@ffwll.ch \
    --cc=troy.hanson@oss.qualcomm.com \
    --cc=youssef.abdulrahman@oss.qualcomm.com \
    --cc=zachary.mckevitt@oss.qualcomm.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