public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "20221024140607.25271-1-shawn.c.lee@intel.com"
	<20221024140607.25271-1-shawn.c.lee@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [v2] drm/i915/pps: improve eDP power on flow
Date: Tue, 01 Nov 2022 15:43:42 +0200	[thread overview]
Message-ID: <877d0e94dt.fsf@intel.com> (raw)
In-Reply-To: <DM6PR11MB27155735D30508F850923FF4A3369@DM6PR11MB2715.namprd11.prod.outlook.com>

On Tue, 01 Nov 2022, "Lee, Shawn C" <shawn.c.lee@intel.com> wrote:
> On Tuesday, November 1, 2022 5:53 PM, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>>On Mon, 24 Oct 2022, Lee Shawn C <shawn.c.lee@intel.com> wrote:
>>> A panel power off cycle delay always append before turn eDP on.
>>> Driver should check last_power_on and last_backlight_off before insert 
>>> this delay. If these values are the same, it means eDP was off until 
>>> now and driver can bypass power off cycle delay to save some times to 
>>> speed up eDP power on sequence.
>>>
>>> v2: fix commit messages
>>
>>There are more changes here than what the changelog says, but the previous review comments were not answered [1].
>>
>
> I'm sorry that lose the question in [1]. 
>
> "But someone else may have turned it off just before we were handed control, we have no idea."
> This is the situation from Ville's comment. Agree that we don't know when panel will be powered off.
> In my opinion, eDP panel should not be turned off before i915 take it over. If it was turned on or off by standard contorl (ex: modeset).
> last_power_on and last_backlight_off would not be the same. So this change should be safe.

I think it's pretty much a hard requirement we respect the panel delays
at i915 probe. If we don't know, we don't know, and we can't make
assumptions.

If the goal is to speed up boot, you should ensure 1) the pre-os enables
the display, and 2) i915 can take over the display without a modeset and
a panel power cycle.


BR,
Jani.


>
> Best regards,
> Shawn
>
>>
>>BR,
>>Jani.
>>
>>
>>[1] https://lore.kernel.org/r/Y1afUdAwfVTACJoK@intel.com
>>
>>>
>>> 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 | 9 ++++++++-
>>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/display/intel_pps.c 
>>> b/drivers/gpu/drm/i915/display/intel_pps.c
>>> index 21944f5bf3a8..290473ec70d5 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_pps.c
>>> +++ b/drivers/gpu/drm/i915/display/intel_pps.c
>>> @@ -509,6 +509,13 @@ static void wait_panel_power_cycle(struct intel_dp *intel_dp)
>>>  	ktime_t panel_power_on_time;
>>>  	s64 panel_power_off_duration;
>>>  
>>> +	/* When last_power_on equal to last_backlight_off, it means driver did not
>>> +	 * turn on or off eDP panel so far. So we can bypass power cycle delay to
>>> +	 * save some times here.
>>> +	 */
>>> +	if (intel_dp->pps.last_power_on == intel_dp->pps.last_backlight_off)
>>> +		return;
>>> +
>>>  	drm_dbg_kms(&i915->drm, "Wait for panel power cycle\n");
>>>  
>>>  	/* take the difference of current time and panel power off time @@ 
>>> -1100,7 +1107,7 @@ static void pps_init_timestamps(struct intel_dp 
>>> *intel_dp)  {
>>>  	intel_dp->pps.panel_power_off_time = ktime_get_boottime();
>>>  	intel_dp->pps.last_power_on = jiffies;
>>> -	intel_dp->pps.last_backlight_off = jiffies;
>>> +	intel_dp->pps.last_backlight_off = intel_dp->pps.last_power_on;
>>>  }
>>>  
>>>  static void
>>
>>--
>>Jani Nikula, Intel Open Source Graphics Center

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-11-01 13:43 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 [this message]
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
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=877d0e94dt.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=20221024140607.25271-1-shawn.c.lee@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