All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Vandana Kannan <vandana.kannan@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: BXT DDI PHY sequence BUN
Date: Mon, 21 Mar 2016 17:02:28 +0200	[thread overview]
Message-ID: <87io0fg9h7.fsf@intel.com> (raw)
In-Reply-To: <87oaa8t9nn.fsf@intel.com>

On Mon, 21 Mar 2016, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> [ text/plain ]
> On Mon, 21 Mar 2016, Vandana Kannan <vandana.kannan@intel.com> wrote:
>> According to the BSpec update, bit 7 of PORT_CL1CM_DW0 register needs to be
>> checked to ensure that the register is in accessible state.
>
> *sigh* the bspec is still not updated, and I didn't get the BUN.
>
>> Also, based on a BSpec update, changing the timeout value to
>> check iphypwrgood, from 10ms to wait for up to 100us.
>>
>> Signed-off-by: Vandana Kannan <vandana.kannan@intel.com>
>> Reported-by: Philippe Lecluse <Philippe.Lecluse@intel.com>
>> Cc: Deak, Imre <imre.deak@intel.com>
>> ---
>>  drivers/gpu/drm/i915/i915_reg.h  |  1 +
>>  drivers/gpu/drm/i915/intel_ddi.c | 11 +++++++++--
>>  2 files changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
>> index 7dfc400..9a02bfc 100644
>> --- a/drivers/gpu/drm/i915/i915_reg.h
>> +++ b/drivers/gpu/drm/i915/i915_reg.h
>> @@ -1318,6 +1318,7 @@ enum skl_disp_power_wells {
>>  #define _PORT_CL1CM_DW0_A		0x162000
>>  #define _PORT_CL1CM_DW0_BC		0x6C000
>>  #define   PHY_POWER_GOOD		(1 << 16)
>> +#define   PHY_RESERVED			(1 << 7)
>>  #define BXT_PORT_CL1CM_DW0(phy)		_BXT_PHY((phy), _PORT_CL1CM_DW0_BC, \
>>  							_PORT_CL1CM_DW0_A)
>>  
>> diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
>> index 62de9f4..354f949 100644
>> --- a/drivers/gpu/drm/i915/intel_ddi.c
>> +++ b/drivers/gpu/drm/i915/intel_ddi.c
>> @@ -2669,9 +2669,16 @@ static void broxton_phy_init(struct drm_i915_private *dev_priv,
>>  	val |= GT_DISPLAY_POWER_ON(phy);
>>  	I915_WRITE(BXT_P_CR_GT_DISP_PWRON, val);
>>  
>> -	/* Considering 10ms timeout until BSpec is updated */
>> -	if (wait_for(I915_READ(BXT_PORT_CL1CM_DW0(phy)) & PHY_POWER_GOOD, 10))
>> +	/*
>> +	 * HW team confirmed that the time to reach phypowergood status is
>> +	 * anywhere between 50 us and 100us.
>> +	 */

Interesting, the spec section (now that I found it, thanks again!) says,
"recommended poll time interval = 100 us". Interval, not timeout.

>> +	if (wait_for_atomic_us(((!(I915_READ(BXT_PORT_CL1CM_DW0(phy)) &
>> +				PHY_RESERVED)) &&
>> +				((I915_READ(BXT_PORT_CL1CM_DW0(phy)) &
>> +				  PHY_POWER_GOOD) == PHY_POWER_GOOD)), 100)) {
>
> Is there any reason why you'd need to do the read twice? Why not just
> write it as:
>
> (I915_READ(BXT_PORT_CL1CM_DW0(phy)) & (PHY_RESERVED | PHY_POWER_GOOD)) == PHY_POWER_GOOD

AFAICT this should be fine.

BR,
Jani.

>
> BR,
> Jani.
>
>>  		DRM_ERROR("timeout during PHY%d power on\n", phy);
>> +	}
>>  
>>  	for (port =  (phy == DPIO_PHY0 ? PORT_B : PORT_A);
>>  	     port <= (phy == DPIO_PHY0 ? PORT_C : PORT_A); port++) {

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-03-21 15:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21  6:42 [PATCH] drm/i915: BXT DDI PHY sequence BUN Vandana Kannan
2016-03-21 10:20 ` Jani Nikula
2016-03-21 15:02   ` Jani Nikula [this message]
2016-03-21 14:03 ` Ville Syrjälä
2016-03-23  4:43   ` Kannan, Vandana
2016-03-29 12:03     ` Imre Deak
2016-03-31 12:38       ` Imre Deak
2016-03-21 14:33 ` ✗ Fi.CI.BAT: warning for " 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=87io0fg9h7.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=vandana.kannan@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.