From: Sivakumar Thulasimani <sivakumar.thulasimani@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Sonika Jindal <sonika.jindal@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Dont enable hpd for eDP
Date: Mon, 10 Aug 2015 17:08:17 +0530 [thread overview]
Message-ID: <55C88D29.7000302@intel.com> (raw)
In-Reply-To: <87d1yv8jcg.fsf@intel.com>
On 8/10/2015 5:07 PM, Jani Nikula wrote:
> On Mon, 10 Aug 2015, Sivakumar Thulasimani <sivakumar.thulasimani@intel.com> wrote:
>> Reviewed-by: Sivakumar Thulasimani <sivakumar.thulasimani@intel.com>
>>
>> On 8/10/2015 10:35 AM, Sonika Jindal wrote:
>>> With HPD support added for all ports including PORT_A, setting hpd_pin will
>>> result in enabling of hpd to edp as well. There is no need to enable HPD on
>>> PORT_A hence this patch removes hpd_pin update for PORT_A, where edp will
>>> be connected. it can be added back when required
> What? You can't just go ahead and remove HPD from eDP sinks.
>
> BR,
> Jani.
Nope, we are not removing HPD for edp sinks, it was never there in the
first place. It was
enabled for CHV (even there by mistake since PORT B/C was both DP and
eDP) but it was
never there for any other plaforms nor is it used for any purpose (PSR
must use it, but i
dont see code for it as well).
>
>>> Signed-off-by: Sonika Jindal <sonika.jindal@intel.com>
>>> ---
>>> drivers/gpu/drm/i915/intel_dp.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>>> index fcc64e5..5a614c9 100644
>>> --- a/drivers/gpu/drm/i915/intel_dp.c
>>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>>> @@ -5784,7 +5784,7 @@ intel_dp_init_connector(struct intel_digital_port *intel_dig_port,
>>> /* Set up the hotplug pin. */
>>> switch (port) {
>>> case PORT_A:
>>> - intel_encoder->hpd_pin = HPD_PORT_A;
>>> + /* Not enabling edp interrupts */
>>> break;
>>> case PORT_B:
>>> intel_encoder->hpd_pin = HPD_PORT_B;
>> --
>> regards,
>> Sivakumar
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
regards,
Sivakumar
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-10 11:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 5:05 [PATCH 0/3] Add BXT A0/A1 WA for HPD swap in generic way Sonika Jindal
2015-08-10 5:05 ` [PATCH 1/3] drm/i915: Dont enable hpd for eDP Sonika Jindal
2015-08-10 5:24 ` Sivakumar Thulasimani
2015-08-10 11:37 ` Jani Nikula
2015-08-10 11:38 ` Sivakumar Thulasimani [this message]
2015-08-10 12:14 ` Jani Nikula
2015-08-10 12:16 ` Ville Syrjälä
2015-08-10 12:21 ` Sivakumar Thulasimani
2015-08-12 12:56 ` Daniel Vetter
2015-08-13 4:05 ` Sivakumar Thulasimani
2015-08-13 15:07 ` Ville Syrjälä
2015-08-10 5:05 ` [PATCH 2/3] drm/i915/bxt: Add HPD support for DDIA Sonika Jindal
2015-08-10 5:27 ` Sivakumar Thulasimani
2015-08-10 5:05 ` [PATCH 3/3] drm/i915/bxt: WA for swapped HPD pins in A stepping Sonika Jindal
2015-08-10 5:28 ` Sivakumar Thulasimani
2015-08-12 12:58 ` Daniel Vetter
2015-08-13 12:48 ` shuang.he
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=55C88D29.7000302@intel.com \
--to=sivakumar.thulasimani@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=sonika.jindal@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