From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Oded Gabbay <ogabbay@kernel.org>
Cc: "Jeffrey Hugo" <quic_jhugo@quicinc.com>,
"Jacek Lawrynowicz" <jacek.lawrynowicz@linux.intel.com>,
dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 0/5] accel/ivpu: Add debugfs support
Date: Wed, 24 May 2023 10:29:52 +0200 [thread overview]
Message-ID: <20230524082952.GA867611@linux.intel.com> (raw)
In-Reply-To: <CAFCwf11x5xJmCsX_hXeHC3Vhjd2-JMRJJWNbdO4_p_3CsUbSmQ@mail.gmail.com>
Hi
On Wed, May 24, 2023 at 10:55:08AM +0300, Oded Gabbay wrote:
> On Wed, May 24, 2023 at 10:49 AM Stanislaw Gruszka
> <stanislaw.gruszka@linux.intel.com> wrote:
> >
> > Add debugfs support for ivpu driver, most importantly firmware loging
> > and tracing.
> Hi,
> Without looking at the code I have 2 comments/questions:
>
> 1. Please add an ABI documentation in Documentation/ABI/testing/ or
> Documentation/ABI/stable (if you are feeling courageous). You can see
> for example habana's file at
> Documentation/ABI/testing/debugfs-driver-habanalabs
We do not promise any ABI compatibility for debugfs for ivpu,
we can add, remove or modify at any time. Hence make no sense to add
documentation files to Documentation/ABI/ for us.
> 2. Is this synced with Christian's upcoming changes to the debugfs
> infra in drm ? If not, I might suggest to sync with that and wait
> until those patches are merged because they change the layout of
> debugfs nodes.
Is not synced. We can wait before Christian changes get in, what
hopefully will happen soon. But if not, ivpu debugfs can be modified
along with the changes. I can assist with that.
Regards
Stanislaw
next prev parent reply other threads:[~2023-05-24 8:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 7:48 [PATCH 0/5] accel/ivpu: Add debugfs support Stanislaw Gruszka
2023-05-24 7:48 ` [PATCH 1/5] accel/ivpu: Initial " Stanislaw Gruszka
2023-07-07 7:11 ` Jacek Lawrynowicz
2023-05-24 7:48 ` [PATCH 2/5] accel/ivpu: Add firmware tracing support Stanislaw Gruszka
2023-07-07 7:11 ` Jacek Lawrynowicz
2023-05-24 7:48 ` [PATCH 3/5] accel/ivpu: Add debugfs files for testing device reset Stanislaw Gruszka
2023-07-07 7:10 ` Jacek Lawrynowicz
2023-05-24 7:48 ` [PATCH 4/5] accel/ivpu: Print firmware name and version Stanislaw Gruszka
2023-05-24 7:48 ` [PATCH 5/5] accel/ivpu: Add fw_name file to debugfs Stanislaw Gruszka
2023-05-24 7:55 ` [PATCH 0/5] accel/ivpu: Add debugfs support Oded Gabbay
2023-05-24 8:29 ` Stanislaw Gruszka [this message]
2023-05-24 9:52 ` Oded Gabbay
2023-07-07 8:04 ` 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=20230524082952.GA867611@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=christian.koenig@amd.com \
--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.