From: Jani Nikula <jani.nikula@linux.intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
"Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/gmbus: Add Wa_16025573575 for PTL for bit-bashing
Date: Fri, 13 Jun 2025 13:38:01 +0300 [thread overview]
Message-ID: <b42497874eb7fb36b2b29a8de3ffae6da74809aa@intel.com> (raw)
In-Reply-To: <174981021705.14553.10495600609368679486@intel.com>
On Fri, 13 Jun 2025, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
> Quoting Jani Nikula (2025-06-13 06:13:55-03:00)
>>For now, you'd manually check for each enum in __intel_display_wa()
>>implementation, but in the future that code could be generated similar
>>to what xe currently has. I'm just not very enthusiastic about adding C
>>language hostprogs with custom .rules files and parsing.
>
> Hehe. Yeah. I'm wondering if something nice could be achieved with
> header files and cpp magic...
Ugh! :)
If it was universally okay to add Python as a build dependency, I'd have
done this already. The rules format could be yaml, json, toml, or
something supported by Python out of the box (not xml though!). The
whole thing could be 100-200 lines of Python without a hostprogs build
step.
drm/msm has quietly added a Python build dependency a few releases ago,
and I'm kind of still waiting to see how it plays out...
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-06-13 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 7:53 [PATCH] drm/i915/gmbus: Add Wa_16025573575 for PTL for bit-bashing Ankit Nautiyal
2025-06-12 9:05 ` ✓ CI.checkpatch: success for " Patchwork
2025-06-12 9:06 ` ✓ CI.KUnit: " Patchwork
2025-06-12 9:17 ` ✓ CI.Build: " Patchwork
2025-06-12 9:58 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-12 12:00 ` [PATCH] " Gustavo Sousa
2025-06-13 6:15 ` Nautiyal, Ankit K
2025-06-13 9:13 ` Jani Nikula
2025-06-13 10:23 ` Gustavo Sousa
2025-06-13 10:38 ` Jani Nikula [this message]
2025-06-15 15:17 ` Nautiyal, Ankit K
2025-06-12 21:08 ` ✗ Xe.CI.Full: failure for " Patchwork
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=b42497874eb7fb36b2b29a8de3ffae6da74809aa@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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