From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/pc8: Add parent interface for PC8 forcewake tricks
Date: Tue, 9 Dec 2025 21:59:28 +0200 [thread overview]
Message-ID: <aTh_oCyruKjdP3rS@intel.com> (raw)
In-Reply-To: <1d8e29c0684013d60529c28247ee6b4ce4510901@intel.com>
On Tue, Dec 09, 2025 at 02:13:47PM +0200, Jani Nikula wrote:
> On Tue, 09 Dec 2025, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
<snip>
> > diff --git a/drivers/gpu/drm/i915/display/intel_parent.h b/drivers/gpu/drm/i915/display/intel_parent.h
> > index 8f91a6f75c53..974a016ab3be 100644
> > --- a/drivers/gpu/drm/i915/display/intel_parent.h
> > +++ b/drivers/gpu/drm/i915/display/intel_parent.h
> > @@ -22,6 +22,9 @@ void intel_parent_hdcp_gsc_context_free(struct intel_display *display,
> > bool intel_parent_irq_enabled(struct intel_display *display);
> > void intel_parent_irq_synchronize(struct intel_display *display);
> >
> > +void intel_parent_pc8_block(struct intel_display *display);
> > +void intel_parent_pc8_unblock(struct intel_display *display);
> > +
> > bool intel_parent_rps_available(struct intel_display *display);
> > void intel_parent_rps_boost_if_not_started(struct intel_display *display, struct dma_fence *fence);
> > void intel_parent_rps_mark_interactive(struct intel_display *display, bool interactive);
> > diff --git a/drivers/gpu/drm/i915/i915_display_pc8.c b/drivers/gpu/drm/i915/i915_display_pc8.c
> > new file mode 100644
> > index 000000000000..443935d282e3
> > --- /dev/null
> > +++ b/drivers/gpu/drm/i915/i915_display_pc8.c
> > @@ -0,0 +1,30 @@
> > +// SPDX-License-Identifier: MIT
> > +/*
> > + * Copyright 2025, Intel Corporation.
> > + */
> > +
> > +#include <drm/drm_print.h>
> > +#include <drm/intel/display_parent_interface.h>
> > +
> > +#include "i915_drv.h"
> > +#include "intel_uncore.h"
>
> For completeness, I think this should include i915_display_pc8.h. I'm a
> bit surprised the compilers only warn about non-static functions without
> declarations, not about non-static variables.
A bit of googling gave me, among other things, this:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110947
And indeed enabling -Wmissing-variable-declarations still
triggers on 'current_stack_pointer'. So I guess no progress
on that since 2023 :(
The other surprising thing here is that the extern decalaration
doesn't seem to need the type definition. Or at least HDRTEST
passses w/o including display_parent_interface.h in
i915_display_pc8.h.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-12-09 19:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 11:11 [PATCH] drm/i915/pc8: Add parent interface for PC8 forcewake tricks Ville Syrjala
2025-12-09 11:17 ` ✗ CI.checkpatch: warning for " Patchwork
2025-12-09 11:18 ` ✓ CI.KUnit: success " Patchwork
2025-12-09 11:33 ` ✗ CI.checksparse: warning " Patchwork
2025-12-09 12:13 ` [PATCH] " Jani Nikula
2025-12-09 12:23 ` Jani Nikula
2025-12-09 19:59 ` Ville Syrjälä [this message]
2025-12-09 12:24 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-12-09 14:17 ` ✗ i915.CI.BAT: failure " Patchwork
2025-12-09 17:39 ` ✗ Xe.CI.Full: " Patchwork
2025-12-10 17:26 ` [PATCH v2] " Ville Syrjala
2025-12-11 8:42 ` Jani Nikula
2025-12-10 19:34 ` ✓ i915.CI.BAT: success for drm/i915/pc8: Add parent interface for PC8 forcewake tricks (rev2) Patchwork
2025-12-11 4:06 ` ✓ i915.CI.Full: " Patchwork
2025-12-18 18:20 ` [PATCH v3] drm/i915/pc8: Add parent interface for PC8 forcewake tricks Ville Syrjala
2025-12-18 19:33 ` ✗ CI.checkpatch: warning for drm/i915/pc8: Add parent interface for PC8 forcewake tricks (rev3) Patchwork
2025-12-18 19:34 ` ✓ CI.KUnit: success " Patchwork
2025-12-18 20:15 ` ✗ i915.CI.BAT: failure " Patchwork
2025-12-18 20:24 ` ✓ Xe.CI.BAT: success " Patchwork
2025-12-19 18:33 ` ✓ Xe.CI.Full: " 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=aTh_oCyruKjdP3rS@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.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.