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 v3 3/3] accel/qaic: Add callbacks for DRM RAS netlink telemetry
Date: Fri, 13 Nov 2026 10:56:56 -0700 [thread overview]
Message-ID: <df3a9511-a17b-45d6-b048-9cceaffe6a8b@oss.qualcomm.com> (raw)
In-Reply-To: <20261106181225.3333260-4-zachary.mckevitt@oss.qualcomm.com>
On 11/6/2026 11:12 AM, Zack McKevitt wrote:
> Use the DRM RAS netlink infrastructure to perform device telemetry.
> During PCI probe, create a DRM RAS node with DRM_RAS_NODE_TYPE_TELEMETRY
> type and add callbacks to telemetry_request for read and write operations.
>
> Co-developed-by: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
> Signed-off-by: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
> Signed-off-by: Zack McKevitt <zachary.mckevitt@oss.qualcomm.com>
Reviewed-by: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
prev parent reply other threads:[~2026-11-13 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 18:12 [PATCH v3 0/3] Extend drm_ras for qaic telemetry Zack McKevitt
2026-11-06 18:12 ` [PATCH v3 1/3] drm/drm_ras: Remove admin-perm flag from list-nodes operation Zack McKevitt
2026-11-06 18:12 ` [PATCH v3 2/3] drm/drm_ras: Extend DRM RAS interface to include telemetry nodes Zack McKevitt
2026-11-09 15:41 ` Rodrigo Vivi
2026-11-09 21:05 ` Zack McKevitt
2026-11-06 18:12 ` [PATCH v3 3/3] accel/qaic: Add callbacks for DRM RAS netlink telemetry Zack McKevitt
2026-11-13 17:56 ` Jeff Hugo [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=df3a9511-a17b-45d6-b048-9cceaffe6a8b@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