From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [Intel-xe] [PATCH v2 rebased 3/6] drm/i915: Only initialize dlk phy lock in display 12 and newer
Date: Mon, 10 Apr 2023 13:19:02 -0400 [thread overview]
Message-ID: <ZDRFBgKIeg9BgzII@intel.com> (raw)
In-Reply-To: <f75f06a5fda030b3e77a8c6a8ef81436b0a34606.camel@intel.com>
On Mon, Apr 10, 2023 at 05:10:01PM +0000, Souza, Jose wrote:
> On Mon, 2023-04-10 at 11:37 -0400, Rodrigo Vivi wrote:
> > On Thu, Apr 06, 2023 at 07:31:30AM -0700, José Roberto de Souza wrote:
> > > This spin lock will not be used in older display versions, so no need
> > > to initialize it.
> >
> > Should we add some warn_on(disp_ver < 12) on the dkl phy functions?
>
> If called in platforms with display version older than 12 we will get warnings about spink lock functions being called in a non initialized spinlock_t
> anyways.
indeed! we are good then...
>
> >
> > Anyway:
> >
> > Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> >
> >
> > >
> > > Cc: intel-gfx@lists.freedesktop.org
> > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > > ---
> > > drivers/gpu/drm/i915/display/intel_dkl_phy.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/display/intel_dkl_phy.c b/drivers/gpu/drm/i915/display/intel_dkl_phy.c
> > > index 5bce7b5b27bc7..1c5d410b74e5d 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_dkl_phy.c
> > > +++ b/drivers/gpu/drm/i915/display/intel_dkl_phy.c
> > > @@ -108,5 +108,6 @@ intel_dkl_phy_posting_read(struct drm_i915_private *i915, struct intel_dkl_phy_r
> > > void
> > > intel_dkl_phy_init(struct drm_i915_private *i915)
> > > {
> > > - spin_lock_init(&i915->display.dkl.phy_lock);
> > > + if (DISPLAY_VER(i915) >= 12)
> > > + spin_lock_init(&i915->display.dkl.phy_lock);
> > > }
> > > --
> > > 2.40.0
> > >
>
next prev parent reply other threads:[~2023-04-10 17:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 14:31 [Intel-gfx] [PATCH v2 rebased 1/6] drm/i915: Nuke unused dsparb_lock José Roberto de Souza
2023-04-06 14:31 ` [Intel-gfx] [PATCH v2 rebased 2/6] drm/i915: Initialize dkl_phy spin lock from display code path José Roberto de Souza
2023-04-10 15:33 ` Rodrigo Vivi
2023-04-10 17:07 ` Souza, Jose
2023-04-10 17:20 ` [Intel-gfx] [Intel-xe] " Rodrigo Vivi
2023-04-06 14:31 ` [Intel-gfx] [PATCH v2 rebased 3/6] drm/i915: Only initialize dlk phy lock in display 12 and newer José Roberto de Souza
2023-04-10 15:37 ` [Intel-gfx] [Intel-xe] " Rodrigo Vivi
2023-04-10 17:10 ` Souza, Jose
2023-04-10 17:19 ` Rodrigo Vivi [this message]
2023-04-06 20:38 ` [Intel-gfx] [Intel-xe] [PATCH v2 rebased 1/6] drm/i915: Nuke unused dsparb_lock Rodrigo Vivi
2023-04-10 14:43 ` Souza, Jose
2023-04-10 15:26 ` Rodrigo Vivi
2023-04-10 15:45 ` Rodrigo Vivi
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=ZDRFBgKIeg9BgzII@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox