From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Oded Gabbay <ogabbay@kernel.org>,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 4/6] accel/ivpu: Add param ioctl to identify capabilities
Date: Tue, 8 Aug 2023 10:52:19 +0200 [thread overview]
Message-ID: <20230808085219.GA3049188@linux.intel.com> (raw)
In-Reply-To: <20230803083737.GA3023441@linux.intel.com>
On Thu, Aug 03, 2023 at 10:37:37AM +0200, Stanislaw Gruszka wrote:
> > Seems like we might want to decide this now, because if we define a iVPU
> > specific ioctl as proposed here, but then switch to an Accel-wide mechanism
> > later, iVPU is going to be stuck supporting both.
>
> For the record, we do not add new ioctl in this patch, we just extend
> existing DRM_IOCTL_IVPU_GET_PARAM one.
To avoid confusion, I'll change the topic and commit massage
before applying:
accel/ivpu: Extend get_param ioctl to identify capabilities
Add DRM_IVPU_PARAM_CAPABILITIES parameters to get_param ioctl to query
driver capabilities. For now use it for identify metric streamer and
new dma memory range features. Currently upstream version of intel_vpu
does not have those, they will be added it the future.
Regards
Stanislaw
next prev parent reply other threads:[~2023-08-08 8:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 16:12 [PATCH 0/6] accel/ivpu: Refactor driver code and support new hardware Stanislaw Gruszka
2023-07-31 16:12 ` [PATCH 1/6] accel/ivpu: Rename sources to use generation based names Stanislaw Gruszka
2023-08-02 16:40 ` Jeffrey Hugo
2023-07-31 16:12 ` [PATCH 2/6] accel/ivpu: Use generation based function and registers names Stanislaw Gruszka
2023-08-02 16:43 ` Jeffrey Hugo
2023-07-31 16:12 ` [PATCH 3/6] accel/ivpu: Switch to generation based FW names Stanislaw Gruszka
2023-08-02 16:47 ` Jeffrey Hugo
2023-07-31 16:12 ` [PATCH 4/6] accel/ivpu: Add param ioctl to identify capabilities Stanislaw Gruszka
2023-08-02 17:07 ` Jeffrey Hugo
2023-08-03 8:37 ` Stanislaw Gruszka
2023-08-08 8:52 ` Stanislaw Gruszka [this message]
2023-08-09 0:45 ` Jeffrey Hugo
2023-08-09 11:24 ` Stanislaw Gruszka
2023-08-09 14:02 ` Jeffrey Hugo
2023-07-31 16:12 ` [PATCH 5/6] accel/ivpu: Refactor memory ranges logic Stanislaw Gruszka
2023-07-31 16:12 ` [PATCH 6/6] accel/ivpu: Add initial support for VPU 4 Stanislaw Gruszka
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=20230808085219.GA3049188@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.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.