From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Use 18 fast wake fast wake AUX sync len
Date: Tue, 30 May 2023 09:58:17 +0000 [thread overview]
Message-ID: <889bf98abd0b86f8aebcebaad58ff19d54d73da8.camel@intel.com> (raw)
In-Reply-To: <87ilcagoza.fsf@intel.com>
On Tue, 2023-05-30 at 12:14 +0300, Jani Nikula wrote:
> On Mon, 29 May 2023, Jouni Högander <jouni.hogander@intel.com> wrote:
> > HW default for wake sync pulses is 18. 10 precarge and 8 preamble.
> > There is
> > no reason to change this especially as it is causing problems with
> > certain
> > eDP panels.
> >
> > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> > Fixes: 605f7c731333 ("drm/i915: Fix fast wake AUX sync len")
>
> Due to the cherry-picks I think it's better to reference e1c71f8f9180
> ("drm/i915: Fix fast wake AUX sync len") which has been backported to
> stable. We need this fix to go wherever that's been backported.
Ok, I will change this.
>
> What happens if we use cc: stable and this gets backported to a
> kernel
> that does *not* have "drm/i915: Fix fast wake AUX sync len"? Any harm
> in
> that?
Our current understanding is that we should use 10 sync pulses for
precharge. Which is actually the HW default. Original value our driver
was writing before "drm/i915: Fix fast wake AUX sync len" was clearly
wrong -> It should be right thing to do to backport this even if
previous adjustment ("drm/i915: Fix fast wake AUX sync len") doesn't
exist.
BR,
Jouni Högander
>
> BR,
> Jani.
>
>
>
> > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/8475
> > ---
> > drivers/gpu/drm/i915/display/intel_dp_aux.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux.c
> > b/drivers/gpu/drm/i915/display/intel_dp_aux.c
> > index 0c27db8ae4f1..197c6e81db14 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp_aux.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp_aux.c
> > @@ -129,7 +129,7 @@ static int intel_dp_aux_sync_len(void)
> >
> > static int intel_dp_aux_fw_sync_len(void)
> > {
> > - int precharge = 16; /* 10-16 */
> > + int precharge = 10; /* 10-16 */
> > int preamble = 8;
> >
> > return precharge + preamble;
>
next prev parent reply other threads:[~2023-05-30 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 13:00 [Intel-gfx] [PATCH] drm/i915: Use 18 fast wake fast wake AUX sync len Jouni Högander
2023-05-30 9:06 ` Murthy, Arun R
2023-05-30 9:51 ` Hogander, Jouni
2023-05-30 9:14 ` Jani Nikula
2023-05-30 9:58 ` Hogander, Jouni [this message]
2023-05-31 1:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-06-01 7:07 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=889bf98abd0b86f8aebcebaad58ff19d54d73da8.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@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.