From: Jani Nikula <jani.nikula@linux.intel.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>,
Daniel Vetter <daniel@ffwll.ch>
Cc: "David Airlie" <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Luís Mendes" <luis.p.mendes@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm/bridge: dw-hdmi: fix EDID parsing
Date: Thu, 09 Nov 2017 11:49:56 +0200 [thread overview]
Message-ID: <87inejaiij.fsf@intel.com> (raw)
In-Reply-To: <20171109093122.GA12318@n2100.armlinux.org.uk>
On Thu, 09 Nov 2017, Russell King - ARM Linux <linux@armlinux.org.uk> wrote:
> On Thu, Nov 09, 2017 at 09:23:18AM +0100, Daniel Vetter wrote:
>> On Tue, Nov 07, 2017 at 11:27:21AM +0000, Russell King wrote:
>> > Parsing the EDID for HDMI and audio information in the get_modes()
>> > callback is incorrect - this only parses the EDID read from the
>> > connector, not any override or firmware provided EDID.
>> >
>> > The correct place to parse the EDID for these parameters is the
>> > fill_modes() callback, after we've called the helper. Move the parsing
>> > there. This caused problems for Luís Mendes.
>> >
>> > Cc: <stable@vger.kernel.org>
>> > Reported-by: Luís Mendes <luis.p.mendes@gmail.com>
>> > Tested-by: Luís Mendes <luis.p.mendes@gmail.com>
>> > Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
>> > ---
>> > drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 28 ++++++++++++++++++++++++----
>> > 1 file changed, 24 insertions(+), 4 deletions(-)
>> >
>> > diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
>> > index 9fe407f49986..2516a1c18a10 100644
>> > --- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
>> > +++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
>> > @@ -1905,10 +1905,7 @@ static int dw_hdmi_connector_get_modes(struct drm_connector *connector)
>> > dev_dbg(hdmi->dev, "got edid: width[%d] x height[%d]\n",
>> > edid->width_cm, edid->height_cm);
>> >
>> > - hdmi->sink_is_hdmi = drm_detect_hdmi_monitor(edid);
>> > - hdmi->sink_has_audio = drm_detect_monitor_audio(edid);
>> > drm_mode_connector_update_edid_property(connector, edid);
>> > - cec_notifier_set_phys_addr_from_edid(hdmi->cec_notifier, edid);
>> > ret = drm_add_edid_modes(connector, edid);
>> > /* Store the ELD */
>> > drm_edid_to_eld(connector, edid);
>> > @@ -1920,6 +1917,29 @@ static int dw_hdmi_connector_get_modes(struct drm_connector *connector)
>> > return ret;
>> > }
>> >
>> > +static int dw_hdmi_connector_fill_modes(struct drm_connector *connector,
>> > + uint32_t maxX, uint32_t maxY)
>> > +{
>> > + struct dw_hdmi *hdmi = container_of(connector, struct dw_hdmi,
>> > + connector);
>> > + int ret;
>> > +
>> > + ret = drm_helper_probe_single_connector_modes(connector, maxX, maxY);
>> > +
>> > + if (connector->edid_blob_ptr) {
>> > + struct edid *edid = (void *)connector->edid_blob_ptr->data;
>> > +
>> > + hdmi->sink_is_hdmi = drm_detect_hdmi_monitor(edid);
>> > + hdmi->sink_has_audio = drm_detect_monitor_audio(edid);
>> > + cec_notifier_set_phys_addr_from_edid(hdmi->cec_notifier, edid);
>> > + } else {
>> > + hdmi->sink_is_hdmi = false;
>> > + hdmi->sink_has_audio = false;
>> > + }
>> > +
>> > + return ret;
>> > +}
>> > +
>> > static void dw_hdmi_connector_force(struct drm_connector *connector)
>> > {
>> > struct dw_hdmi *hdmi = container_of(connector, struct dw_hdmi,
>> > @@ -1933,7 +1953,7 @@ static void dw_hdmi_connector_force(struct drm_connector *connector)
>> > }
>> >
>> > static const struct drm_connector_funcs dw_hdmi_connector_funcs = {
>> > - .fill_modes = drm_helper_probe_single_connector_modes,
>> > + .fill_modes = dw_hdmi_connector_fill_modes,
>>
>> Papering over helper functions shouldn't be necessary, except the helper
>> functions not handling the override edid is a known issue. Jani Nikula is
>> working on a proper fix, please coordinate with him.
>
> So, what you're basically saying is that fixing real bugs that affect
> users is not something that DRM people want. That's fine, I'll ignore
> people who come to me for help with DRM bugs in future then because
> it's obviously a dead loss.
We may already have fixed the bug in drm-next at the proper
layer. Please see my other mail.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-11-09 9:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 11:27 [PATCH] drm/bridge: dw-hdmi: fix EDID parsing Russell King
2017-11-09 6:49 ` Archit Taneja
2017-11-09 8:23 ` Daniel Vetter
2017-11-09 9:31 ` Russell King - ARM Linux
2017-11-09 9:49 ` Jani Nikula [this message]
2017-11-09 9:51 ` Luís Mendes
2017-11-09 10:52 ` Luís Mendes
2017-11-09 11:07 ` Luís Mendes
2017-11-09 12:12 ` Jani Nikula
2017-11-09 14:34 ` Luís Mendes
2017-11-09 15:01 ` Jani Nikula
2017-11-09 15:08 ` Luís Mendes
2017-11-09 15:22 ` Jani Nikula
2017-11-09 16:17 ` Daniel Vetter
2017-11-09 22:44 ` Luís Mendes
2017-11-10 9:37 ` Daniel Vetter
2017-11-09 16:28 ` Russell King - ARM Linux
2017-11-09 18:45 ` Luís Mendes
2017-11-09 16:26 ` Russell King - ARM Linux
2017-11-10 9:45 ` Jani Nikula
2017-11-09 8:27 ` Jani Nikula
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=87inejaiij.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=luis.p.mendes@gmail.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