All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>,
	Gustavo Sousa <gustavo.sousa@intel.com>
Subject: Re: [PATCH] drm/i915/display: move dmc_firmware_path to display params
Date: Fri, 22 Mar 2024 11:06:20 -0500	[thread overview]
Message-ID: <b7o4x73ht2wv6t52h44dofzu36oic3bfazfilt2o4oxuj3zxzg@rzwm4a7cro7p> (raw)
In-Reply-To: <87v85elkic.fsf@intel.com>

On Fri, Mar 22, 2024 at 10:48:43AM +0200, Jani Nikula wrote:
>On Thu, 21 Mar 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
>> On Thu, Mar 21, 2024 at 06:20:57PM +0200, Jani Nikula wrote:
>>>On Thu, 21 Mar 2024, Jani Nikula <jani.nikula@intel.com> wrote:
>>>> The dmc_firmware_path parameter is clearly a display parameter. Move it
>>>> there. This also cleans up the ugly member in struct xe_device.
>>>
>>>Hmm, does this actually fix the parameter on xe?!
>>
>> not sure what you meant here. Patches makes sense to me.
>
>Unless I'm mistaken, the parameter currently does not work on xe at
>all. I only realized after posting the patch that this probably fixes
>that issue too.

+Gustavo

I never really tried the dmc_firmware_path param, but current code
contains:

drivers/gpu/drm/i915/display/intel_dmc.c:       if (err == -ENOENT && !i915->params.dmc_firmware_path) {
drivers/gpu/drm/i915/display/intel_dmc.c:       if (i915->params.dmc_firmware_path) {
drivers/gpu/drm/i915/display/intel_dmc.c:               if (strlen(i915->params.dmc_firmware_path) == 0) {
drivers/gpu/drm/i915/display/intel_dmc.c:               dmc->fw_path = i915->params.dmc_firmware_path;
drivers/gpu/drm/i915/i915_params.c:i915_param_named_unsafe(dmc_firmware_path, charp, 0400,
drivers/gpu/drm/i915/i915_params.h:     param(char *, dmc_firmware_path, NULL, 0400) \
drivers/gpu/drm/xe/xe_device_types.h:           const char *dmc_firmware_path;

So dmc_firmware_path is only dealt with inside display... it would be
odd if it was not working. I'll double check.

Lucas De Marchi

  reply	other threads:[~2024-03-22 16:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 16:18 [PATCH] drm/i915/display: move dmc_firmware_path to display params Jani Nikula
2024-03-21 16:20 ` Jani Nikula
2024-03-22  4:34   ` Lucas De Marchi
2024-03-22  8:48     ` Jani Nikula
2024-03-22 16:06       ` Lucas De Marchi [this message]
2024-03-22 18:32         ` Lucas De Marchi
2024-04-02  8:47           ` Jani Nikula
2024-03-21 19:35 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-21 19:35 ` ✗ CI.checkpatch: warning " Patchwork
2024-03-21 19:36 ` ✓ CI.KUnit: success " Patchwork
2024-03-21 19:47 ` ✓ CI.Build: " Patchwork
2024-03-21 19:49 ` ✓ CI.Hooks: " Patchwork
2024-03-21 19:51 ` ✗ CI.checksparse: warning " Patchwork
2024-03-21 20:14 ` ✓ CI.BAT: success " Patchwork
2024-03-21 23:52 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-03-21 23:52 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-03-22  0:02 ` ✗ Fi.CI.BAT: failure " 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=b7o4x73ht2wv6t52h44dofzu36oic3bfazfilt2o4oxuj3zxzg@rzwm4a7cro7p \
    --to=lucas.demarchi@intel.com \
    --cc=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@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.