From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
Koby Elbaz <kelbaz@habana.ai>
Cc: rodrigo.vivi@intel.com, intel-xe@lists.freedesktop.org,
"Daniel Vetter" <daniel@ffwll.ch>,
"Ofir Bitton" <obitton@habana.ai>,
"José Roberto de Souza" <jose.souza@intel.com>
Subject: Re: [PATCH v9] drm/xe: add mmio debugfs file & restore xe_mmio_ioctl as its ioctl handler
Date: Thu, 16 May 2024 11:13:57 +0300 [thread overview]
Message-ID: <87seyib2d6.fsf@intel.com> (raw)
In-Reply-To: <75pog7eg7y5igqenv7gjgearkwyn66ba2cnxpwhfh5wgjtj27o@nqgpq2vew2vt>
On Wed, 15 May 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> Currently intel_reg has a few backends like mapping the BAR, or
> submitting a batch and reading/writing from the GPU side. Adding another
> one to be "via driver's debugfs" would probably be ok. +Jani as
> intel_reg's original author.
Yeah, why not. It should be possible to cleanly add new "backends", and
there's already plenty.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-05-16 8:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 16:52 [PATCH v9] drm/xe: add mmio debugfs file & restore xe_mmio_ioctl as its ioctl handler Koby Elbaz
2024-05-15 17:12 ` ✓ CI.Patch_applied: success for drm/xe: add mmio debugfs file & restore xe_mmio_ioctl as its ioctl handler (rev2) Patchwork
2024-05-15 17:12 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-15 17:13 ` ✓ CI.KUnit: success " Patchwork
2024-05-15 17:25 ` ✓ CI.Build: " Patchwork
2024-05-15 17:29 ` ✓ CI.Hooks: " Patchwork
2024-05-15 17:31 ` ✓ CI.checksparse: " Patchwork
2024-05-15 17:53 ` ✓ CI.BAT: " Patchwork
2024-05-15 18:00 ` [PATCH v9] drm/xe: add mmio debugfs file & restore xe_mmio_ioctl as its ioctl handler Ofir Bitton
2024-05-15 18:57 ` ✗ CI.FULL: failure for drm/xe: add mmio debugfs file & restore xe_mmio_ioctl as its ioctl handler (rev2) Patchwork
2024-05-15 20:04 ` [PATCH v9] drm/xe: add mmio debugfs file & restore xe_mmio_ioctl as its ioctl handler Lucas De Marchi
2024-05-16 8:13 ` Jani Nikula [this message]
2025-02-18 8:04 ` Dafna Hirschfeld
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=87seyib2d6.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=kelbaz@habana.ai \
--cc=lucas.demarchi@intel.com \
--cc=obitton@habana.ai \
--cc=rodrigo.vivi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.