Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	dri-devel@lists.freedesktop.org,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Chris Wilson <chris.p.wilson@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/pcode: Wait 10 seconds for pcode to settle
Date: Wed, 11 Jan 2023 18:40:13 +0200	[thread overview]
Message-ID: <87pmblgh3m.fsf@intel.com> (raw)
In-Reply-To: <Y77XmlzOCuOg8YVZ@ashyti-mobl2.lan>

On Wed, 11 Jan 2023, Andi Shyti <andi.shyti@linux.intel.com> wrote:
> On Wed, Jan 11, 2023 at 03:18:38PM +0200, Jani Nikula wrote:
>> On Wed, 11 Jan 2023, Andi Shyti <andi.shyti@linux.intel.com> wrote:
>> > From: Aravind Iddamsetty <aravind.iddamsetty@intel.com>
>> >
>> > During module load not all the punit transaction have completed
>> > and we might end up timing out, as shown by the following
>> > warning:
>> 
>> Root cause?
>> 
>> >
>> >    i915 0000:4d:00.0: drm_WARN_ON_ONCE(timeout_base_ms > 3)
>> >
>> > Wait 10 seconds for the punit to settle and complete any
>> > outstanding transactions upon module load.
>> >
>> > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/7814
>> >
>> 
>> No blank lines between the tag lines please.
>
> I don't consider "Closes:" to be a tag even if someone is using
> it as such. AFAIK is not mentioned it in any of the kernel docs
> (e.g. Documentation/process/maintainer-tip.rst).

Basically all of the Something: lines should be bundled together.

BR,
Jani.

>
> Not to confuse it with a normal tag, I wanted to put it in
> parenthesis or rephrase it.
>
>> > Signed-off-by: Aravind Iddamsetty <aravind.iddamsetty@intel.com>
>> > Co-developed-by: Chris Wilson <chris@chris-wilson.co.uk>
>> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> > Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
>> > ---
>> >  drivers/gpu/drm/i915/intel_pcode.c | 35 ++++++++++++++++++++++++++----
>> >  1 file changed, 31 insertions(+), 4 deletions(-)
>> >
>> > diff --git a/drivers/gpu/drm/i915/intel_pcode.c b/drivers/gpu/drm/i915/intel_pcode.c
>> > index a234d9b4ed14..3db2ba439bb5 100644
>> > --- a/drivers/gpu/drm/i915/intel_pcode.c
>> > +++ b/drivers/gpu/drm/i915/intel_pcode.c
>> > @@ -204,15 +204,42 @@ int skl_pcode_request(struct intel_uncore *uncore, u32 mbox, u32 request,
>> >  #undef COND
>> >  }
>> >  
>> > +static int pcode_init_wait(struct intel_uncore *uncore, int timeout_ms)
>> > +{
>> > +	if (__intel_wait_for_register_fw(uncore,
>> > +					 GEN6_PCODE_MAILBOX,
>> > +					 GEN6_PCODE_READY, 0,
>> > +					 500, timeout_ms,
>> > +					 NULL))
>> > +		return -EPROBE_DEFER;
>> 
>> This is already done within skl_pcode_request -> skl_pcode_try_request
>> -> __snb_pcode_rw path, with waits in skl_pcode_request.
>
> the idea is to check for PCODE_READY even before checking if
> data are sent/received by pcode. And this is only during boot
> time. While skl_pcode_request is called in other contexts as
> well.
>
> In other words here I want to start the communication when I
> already know that the punit is ready. Otherwise I would hit an
> -EAGAIN and fail.
>
>> Is there anyone who still understands what's being waited for, where,
>> for how long, and why in the different code paths? I know I don't, and
>> this isn't helping.
>
> I think it depends on hardware. There are some documents roaming
> around with some boot time and reset time calculation.
>
>> There's also no explanation on the -EPROBE_DEFER return in the commit
>> message or comments or anywhere.
>
> we haven't really failed, right? We just need some time for the
> punit to be ready and try to probe again (remember we are here in
> module probe).
>
> Thanks for the review,
> Andi
>
>> Again, root cause?
>> 
>> BR,
>> Jani.
>> 
>> 
>> > +
>> > +	return skl_pcode_request(uncore,
>> > +				 DG1_PCODE_STATUS,
>> > +				 DG1_UNCORE_GET_INIT_STATUS,
>> > +				 DG1_UNCORE_INIT_STATUS_COMPLETE,
>> > +				 DG1_UNCORE_INIT_STATUS_COMPLETE, timeout_ms);
>> > +}
>> > +
>> >  int intel_pcode_init(struct intel_uncore *uncore)
>> >  {
>> > +	int err;
>> > +
>> >  	if (!IS_DGFX(uncore->i915))
>> >  		return 0;
>> >  
>> > -	return skl_pcode_request(uncore, DG1_PCODE_STATUS,
>> > -				 DG1_UNCORE_GET_INIT_STATUS,
>> > -				 DG1_UNCORE_INIT_STATUS_COMPLETE,
>> > -				 DG1_UNCORE_INIT_STATUS_COMPLETE, 180000);
>> > +	/*
>> > +	 * Wait 10 seconds so that the punit to settle and complete
>> > +	 * any outstanding transactions upon module load
>> > +	 */
>> > +	err = pcode_init_wait(uncore, 10000);
>> > +
>> > +	if (err) {
>> > +		drm_notice(&uncore->i915->drm,
>> > +			   "Waiting for HW initialisation...\n");
>> > +		err = pcode_init_wait(uncore, 180000);
>> > +	}
>> > +
>> > +	return err;
>> >  }
>> >  
>> >  int snb_pcode_read_p(struct intel_uncore *uncore, u32 mbcmd, u32 p1, u32 p2, u32 *val)
>> 
>> -- 
>> Jani Nikula, Intel Open Source Graphics Center

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-01-11 16:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 10:44 [Intel-gfx] [PATCH] drm/i915/pcode: Wait 10 seconds for pcode to settle Andi Shyti
2023-01-11 11:21 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-01-11 12:41 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-01-11 13:18 ` [Intel-gfx] [PATCH] " Jani Nikula
2023-01-11 15:36   ` Andi Shyti
2023-01-11 16:40     ` Jani Nikula [this message]
2023-01-27  6:50     ` Gwan-gyeong Mun
2023-01-27  9:00       ` Andi Shyti
2023-01-28  5:41         ` Gwan-gyeong Mun
2023-01-30  8:48           ` Andi Shyti
2023-01-30 14:41             ` Rodrigo Vivi
2023-01-30 16:12               ` Andi Shyti
2023-01-30 16:37                 ` Rodrigo Vivi
2023-01-30 17:30                   ` Rodrigo Vivi
2023-01-30 20:41                     ` Andi Shyti
2023-02-02  8:22                       ` Gwan-gyeong Mun
2023-02-02  9:28                         ` Andi Shyti
2023-02-02 11:01                           ` Gwan-gyeong Mun
2023-01-11 15:25 ` Rodrigo Vivi
2023-01-11 15:39   ` Andi Shyti
2023-01-11 17:06     ` Rodrigo Vivi
2023-01-16 19:27       ` Andi Shyti

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=87pmblgh3m.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=chris.p.wilson@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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