From: Jani Nikula <jani.nikula@intel.com>
To: "20200828061941.17051-2-jani.nikula\@intel.com"
<20200828061941.17051-2-jani.nikula@intel.com>,
"intel-gfx\@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>, "Shankar\,
Uma" <uma.shankar@intel.com>
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/dp: use opregion mailbox #5 EDID for eDP, if available
Date: Tue, 13 Oct 2020 14:03:45 +0300 [thread overview]
Message-ID: <87sgaibd66.fsf@intel.com> (raw)
In-Reply-To: <BY5PR11MB43075789F4800E9D04E2DA6DA3040@BY5PR11MB4307.namprd11.prod.outlook.com>
On Tue, 13 Oct 2020, "Lee, Shawn C" <shawn.c.lee@intel.com> wrote:
> On Mon, Oct 12, 2020 at 5:09 PM, Jani Nikula wrote:
>>On Mon, 12 Oct 2020, "Lee, Shawn C" <shawn.c.lee@intel.com> wrote:
>>> On Fri, Aug 28, 2020 at 06:19AM, Shankar Uma wrote:
>>>>> -----Original Message-----
>>>>> From: Jani Nikula <jani.nikula@intel.com>
>>>>> Sent: Friday, August 28, 2020 11:50 AM
>>>>> To: intel-gfx@lists.freedesktop.org
>>>>> Cc: Nikula, Jani <jani.nikula@intel.com>; Shankar, Uma
>>>>> <uma.shankar@intel.com>
>>>>> Subject: [PATCH 2/2] drm/i915/dp: use opregion mailbox #5 EDID for
>>>>> eDP, if available
>>>>>
>>>>> If a panel's EDID is broken, there may be an override EDID set in
>>>>> the ACPI OpRegion mailbox #5. Use it if available.
>>>>
>>>>Looks Good to me.
>>>>Reviewed-by: Uma Shankar <uma.shankar@intel.com>
>>>>
>>>>> Cc: Uma Shankar <uma.shankar@intel.com>
>>>>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>>>>> ---
>>>>> drivers/gpu/drm/i915/display/intel_dp.c | 3 +++
>>>>> 1 file changed, 3 insertions(+)
>>>>>
>>>>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
>>>>> b/drivers/gpu/drm/i915/display/intel_dp.c
>>>>> index c57ac83bf563..d1307be196a2 100644
>>>>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>>>>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>>>>> @@ -8114,6 +8114,9 @@ static bool intel_edp_init_connector(struct
>>>>> intel_dp *intel_dp, goto out_vdd_off; }
>>>>>
>>>>> +/* Set up override EDID, if any, from ACPI OpRegion */
>>>>> +intel_opregion_edid_override(intel_connector);
>>>>> +
>>>
>>> Customer report DUT still get EDID from eDP panel instead of mailbox #5.
>>> After some investigations, this change can retrieve EDID from mailbox #5 properly.
>>> But driver still used panel's EDID to enable eDP display. This is
>>> because of drm_get_edid() was executed after
>>> intel_opregion_edid_override(). drm_get_edid() return panel's EDID and overwrite mailbox #5's.
>>
>>In recent kernels, drm_get_edid() respects EDID override, and calling
>>drm_get_edid() will return the override EDID from mailbox #5 instead of retrieving the actual EDID.
>>
>>Check the kernel version they're using and the drm_get_edid() implementation.
>>
>>BR,
>>Jani.
>>
>
> Just confirm customer is using kernel v5.8. Seems drm_edid.c already include
> the change for override_edid.
>
> BTW. override_edid should be "true" and used to over EDID in intel_opregion_edid_override() in patch 1. Right?
> But it is "false" in the patch 1.
>
> +connector->override_edid = false;
>
+
+ connector->override_edid = false;
+ ret = drm_connector_update_edid_property(connector, edid);
+ if (ret)
+ return;
+
+ connector->override_edid = true;
+ drm_dbg_kms(&i915->drm, "Using OpRegion EDID for [CONNECTOR:%d:%s]\n",
+ connector->base.id, connector->name);
http://lore.kernel.org/r/20200831083657.15600-1-jani.nikula@intel.com
BR,
Jani.
> Best regards,
> Shawn
>
>>
>>>
>>> We try to move drm_get_edid() before intel_opregion_edid_override().
>>> The test result is positive, mailbox #5 EDID will substitute for panel's.
>>> It seems we may need some additional change for this patch. Thanks!
>>>
>>> Best regards,
>>> Shawn
>>>
>>>>> mutex_lock(&dev->mode_config.mutex);
>>>>> edid = drm_get_edid(connector, &intel_dp->aux.ddc); if (edid) {
>>>>> --
>>>>> 2.20.1
>>
>>--
>>Jani Nikula, Intel Open Source Graphics Center
>>_______________________________________________
>>Intel-gfx mailing list
>>Intel-gfx@lists.freedesktop.org
>>https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-10-13 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 8:37 [Intel-gfx] [PATCH 2/2] drm/i915/dp: use opregion mailbox #5 EDID for eDP, if available Lee, Shawn C
2020-10-12 9:09 ` Jani Nikula
2020-10-13 9:56 ` Lee, Shawn C
2020-10-13 11:03 ` Jani Nikula [this message]
2020-10-14 14:11 ` Lee, Shawn C
2020-10-14 14:14 ` Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2020-08-28 6:19 [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add support for mailbox #5 EDID Jani Nikula
2020-08-28 6:19 ` [Intel-gfx] [PATCH 2/2] drm/i915/dp: use opregion mailbox #5 EDID for eDP, if available Jani Nikula
2020-08-31 7:59 ` Shankar, Uma
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=87sgaibd66.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=20200828061941.17051-2-jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=uma.shankar@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.