Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Deak, Imre" <imre.deak@intel.com>
Subject: Re: [PATCH 1/2] drm/i915: Prevent HW access during init from SDVO TV get_modes hook
Date: Wed, 7 Feb 2024 13:45:15 +0000	[thread overview]
Message-ID: <236599ca2b3982045a2515d4eaef16a2f23cefd5.camel@intel.com> (raw)
In-Reply-To: <47fac05618fb85725f9c0cfa694fb601c82b2a7f.camel@intel.com>

On Wed, 2024-02-07 at 15:26 +0200, Hogander, Jouni wrote:
> On Tue, 2024-02-06 at 17:39 +0200, Imre Deak wrote:
> > Prevent accessing the HW from the SDVO/TV get_modes connector hook.
> > Returning 0 from the hook will make the caller -
> > drm_helper_probe_single_connector_modes() - keep the previously
> > detected
> > mode list of the connector.
> 
> I don't see where this is done? Not sure if looking at wrong place,
> but
> I see it tries using some override edid and in case that fails as
> well
> uses drm_add_modes_noedid?
> 
> > 
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_sdvo.c | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_sdvo.c
> > b/drivers/gpu/drm/i915/display/intel_sdvo.c
> > index 2571ef5a1b211..ccea0efbd136f 100644
> > --- a/drivers/gpu/drm/i915/display/intel_sdvo.c
> > +++ b/drivers/gpu/drm/i915/display/intel_sdvo.c
> > @@ -2287,6 +2287,7 @@ static const struct drm_display_mode
> > sdvo_tv_modes[] = {
> >  static int intel_sdvo_get_tv_modes(struct drm_connector
> > *connector)
> 
> I see intel_sdvo_get_tv_modes is called from intel_sdvo_get_modes.
> Why
> there is no need to do the same in intel_sdvo_get_lvds_modes and
> intel_sdvo_get_ddc_modes as well?

It seems you are taking care of intel_svdo_get_ddc_modes in next patch.
Intel_svdo_get_lvds_modes doesn't touch the hw -> nothing to do there.

> 
> BR,
> 
> Jouni Högander
> 
> >  {
> >         struct intel_sdvo *intel_sdvo =
> > intel_attached_sdvo(to_intel_connector(connector));
> > +       struct drm_i915_private *i915 = to_i915(intel_sdvo-
> > > base.base.dev);
> >         struct intel_sdvo_connector *intel_sdvo_connector =
> >                 to_intel_sdvo_connector(connector);
> >         const struct drm_connector_state *conn_state = connector-
> > > state;
> > @@ -2298,6 +2299,9 @@ static int intel_sdvo_get_tv_modes(struct
> > drm_connector *connector)
> >         DRM_DEBUG_KMS("[CONNECTOR:%d:%s]\n",
> >                       connector->base.id, connector->name);
> >  
> > +       if (!intel_display_driver_check_access(i915))
> > +               return 0;
> > +
> >         /*
> >          * Read the list of supported input resolutions for the
> > selected TV
> >          * format.
> 


  reply	other threads:[~2024-02-07 13:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 15:39 [PATCH 0/2] drm/i915: Prevent HW access during init from connector hooks Imre Deak
2024-02-06 15:39 ` [PATCH 1/2] drm/i915: Prevent HW access during init from SDVO TV get_modes hook Imre Deak
2024-02-07 13:26   ` Hogander, Jouni
2024-02-07 13:45     ` Hogander, Jouni [this message]
2024-02-07 14:10       ` Imre Deak
2024-02-07 15:49         ` Imre Deak
2024-02-07 14:16       ` Imre Deak
2024-02-07 15:35         ` Hogander, Jouni
2024-02-08 11:18   ` [PATCH v2 " Imre Deak
2024-02-06 15:39 ` [PATCH 2/2] drm/i915: Prevent HW access during init from connector get_modes hooks Imre Deak
2024-02-07 15:36   ` Hogander, Jouni
2024-02-06 17:01 ` ✓ Fi.CI.BAT: success for drm/i915: Prevent HW access during init from connector hooks Patchwork
2024-02-06 20:18 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-02-08 19:26 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Prevent HW access during init from connector hooks (rev2) Patchwork
2024-02-08 19:40 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-08 23:36 ` ✓ Fi.CI.IGT: " 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=236599ca2b3982045a2515d4eaef16a2f23cefd5.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@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