From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lee Shawn C <shawn.c.lee@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [v3] drm/i915/pps: improve eDP power on flow
Date: Thu, 03 Nov 2022 13:00:05 +0200 [thread overview]
Message-ID: <87sfj0b8wa.fsf@intel.com> (raw)
In-Reply-To: <20221103004006.24904-1-shawn.c.lee@intel.com>
On Thu, 03 Nov 2022, Lee Shawn C <shawn.c.lee@intel.com> wrote:
> After i915 dirver initialized, a panel power off cycle delay
> always append before turn eDP on. If eDP display did not
> power on before. With this change, power off duration might
> longer than power cycle delay. So driver can save power cycle
> delay to speed up driver initialization time.
>
> v2: fix commit messages
> v3: refine panel_power_off_time default value and modify
> commit messages
>
> Cc: Shankar Uma <uma.shankar@intel.com>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Lee Shawn C <shawn.c.lee@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_pps.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_pps.c b/drivers/gpu/drm/i915/display/intel_pps.c
> index 21944f5bf3a8..a394bb1c92d0 100644
> --- a/drivers/gpu/drm/i915/display/intel_pps.c
> +++ b/drivers/gpu/drm/i915/display/intel_pps.c
> @@ -1098,7 +1098,7 @@ bool intel_pps_have_panel_power_or_vdd(struct intel_dp *intel_dp)
>
> static void pps_init_timestamps(struct intel_dp *intel_dp)
> {
> - intel_dp->pps.panel_power_off_time = ktime_get_boottime();
> + intel_dp->pps.panel_power_off_time = 0;
So this is just copy-paste from [1] where we discuss the problems with
this approach, specifically module reload ignoring the power off
time. Why would you post this without even mentioning the problem?
BR,
Jani.
[1] https://gitlab.freedesktop.org/drm/intel/-/issues/7417#note_1619118
> intel_dp->pps.last_power_on = jiffies;
> intel_dp->pps.last_backlight_off = jiffies;
> }
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-11-03 11:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 6:40 [Intel-gfx] [PATCH] drm/i915/pps: improve eDP power on flow Lee Shawn C
2022-10-24 7:39 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-10-24 13:16 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2022-10-24 13:47 ` Lee, Shawn C
2022-10-24 14:21 ` Ville Syrjälä
2022-10-24 14:06 ` [Intel-gfx] [v2] " Lee Shawn C
2022-11-01 9:53 ` Jani Nikula
2022-11-01 10:50 ` Lee, Shawn C
2022-11-01 13:43 ` Jani Nikula
2022-11-01 14:40 ` Lee, Shawn C
2022-11-01 14:42 ` Lee, Shawn C
2022-11-02 10:19 ` Jani Nikula
2022-11-02 14:50 ` Lee, Shawn C
2022-10-24 17:33 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/pps: improve eDP power on flow. (rev2) Patchwork
2022-11-03 0:40 ` [Intel-gfx] [v3] drm/i915/pps: improve eDP power on flow Lee Shawn C
2022-11-03 11:00 ` Jani Nikula [this message]
2022-11-03 11:23 ` Lee, Shawn C
2022-11-03 1:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/pps: improve eDP power on flow. (rev3) Patchwork
2022-11-03 14:04 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-11-14 6:21 ` [Intel-gfx] [v4] drm/i915/pps: improve eDP power on flow Lee Shawn C
2022-11-16 15:44 ` Jani Nikula
2022-11-16 15:57 ` Lee, Shawn C
2022-11-14 11:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/pps: improve eDP power on flow. (rev4) Patchwork
2022-11-14 17:22 ` [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=87sfj0b8wa.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shawn.c.lee@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