From: Lizhi Hou <lizhi.hou@amd.com>
To: Md Shofiqul Islam <shofiqtest@gmail.com>, <mamin506@gmail.com>
Cc: <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/accel/amdxdna: add debugfs support -- follow-up
Date: Thu, 21 May 2026 10:40:42 -0700 [thread overview]
Message-ID: <5ff41dd5-a583-da76-76be-2b70365a4cbc@amd.com> (raw)
In-Reply-To: <6a0cce2d.1abec865.8b8c7.cb2a@mx.google.com>
On 5/19/26 13:55, Md Shofiqul Islam wrote:
> Hi Min, Lizhi,
>
> I just sent a patch to dri-devel adding debugfs support to the amdxdna
> driver (subject: "drm/accel/amdxdna: add debugfs support"). It resolves
> the TODO item in drivers/accel/amdxdna/TODO and adds three read-only
> entries: fw_version, device_info, and clients.
>
> I'm a Linux kernel contributor with upstream patches in IIO, ASoC, SCSI,
> SCTP, XFS, and power supply subsystems, and I'm interested in spending
> more time in the accel/NPU space.
>
> A few questions if you have a moment:
>
> 1. Is the debugfs patch heading in the right direction, or are there
> conventions in amdxdna I should follow more closely?
Thanks for trying and reviewing this driver. I replied your patch.
>
> 2. Are there other known gaps or TODO items in the driver that would be
> good next contributions?
You are welcome to view the driver repo for the new features, issues and
discussions.
https://github.com/amd/xdna-driver
>
> 3. Is drm/misc/kernel the correct tree for amdxdna patches?
Usually, the latest upstream patches are in drm-misc-next.
Thanks,
Lizhi
>
> Happy to take on more work in this driver.
>
> Regards,
> Md Shofiqul Islam
> https://lore.kernel.org/all/?q=Md+Shofiqul+Islam
prev parent reply other threads:[~2026-05-21 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 20:55 [PATCH] drm/accel/amdxdna: add debugfs support -- follow-up Md Shofiqul Islam
2026-05-21 17:40 ` Lizhi Hou [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=5ff41dd5-a583-da76-76be-2b70365a4cbc@amd.com \
--to=lizhi.hou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=mamin506@gmail.com \
--cc=shofiqtest@gmail.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