From: Jani Nikula <jani.nikula@intel.com>
To: "Lee\, Shawn C" <shawn.c.lee@intel.com>,
"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: Wed, 14 Oct 2020 17:14:04 +0300 [thread overview]
Message-ID: <87eem0c2tv.fsf@intel.com> (raw)
In-Reply-To: <BY5PR11MB4307FF0DBCF91278A17EC19AA3050@BY5PR11MB4307.namprd11.prod.outlook.com>
On Wed, 14 Oct 2020, "Lee, Shawn C" <shawn.c.lee@intel.com> wrote:
> I think I got the problem now. The patch you attached is correct.
> http://lore.kernel.org/r/20200831083657.15600-1-jani.nikula@intel.com
>
> But customer refer to below patch without "override_edid = true".
> https://patchwork.freedesktop.org/patch/388309/?series=81121&rev=1
>
> This is why they can't get EDID from mailbox #5 properly.
Yeah, there was that bug in v1 of the patch.
BR,
Jani.
--
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-14 14:14 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
2020-10-14 14:11 ` Lee, Shawn C
2020-10-14 14:14 ` Jani Nikula [this message]
-- 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=87eem0c2tv.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=20200828061941.17051-2-jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shawn.c.lee@intel.com \
--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.