From: Luc Verhaegen <libv@skynet.be>
To: Priit Laes <plaes@plaes.org>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Russell King <linux@armlinux.org.uk>,
David Airlie <airlied@linux.ie>, Chen-Yu Tsai <wens@csie.org>,
Daniel Vetter <daniel@ffwll.ch>, Priit Laes <priit.laes@paf.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [linux-sunxi] [RESEND PATCH] drm/sun4i: hdmi: Improve compatibility with hpd-less HDMI displays
Date: Mon, 4 Mar 2019 14:31:39 +0100 [thread overview]
Message-ID: <20190304133139.GA26394@skynet.be> (raw)
In-Reply-To: <20190304130616.27525-1-plaes@plaes.org>
On Mon, Mar 04, 2019 at 03:06:16PM +0200, Priit Laes wrote:
> From: Priit Laes <priit.laes@paf.com>
>
> Even though HDMI connector features hotplug detect pin (HPD), there
> are older devices which do not support it. For these devices fall
> back to additional check on I2C bus to probe for EDID data.
>
> One known example is HDMI/DVI display with following edid:
>
> $ xxd -p display.edid
> 00ffffffffffff0005a1e00301000000150f0103800f05780a0f6ea05748
> 9a2610474f200000010101010101010101010101010101012a08804520e0
> 0b1020004000953600000018000000fd0034441a2403000a202020202020
> 0000001000310a20202020202020202020200000001000002a4030701300
> 782d1100001e006b
>
> $ edid-decode display.edid
> EDID version: 1.3
> Manufacturer: AMA Model 3e0 Serial Number 1
> Digital display
> Maximum image size: 15 cm x 5 cm
> Gamma: 2.20
> RGB color display
> First detailed timing is preferred timing
> Display x,y Chromaticity:
> Red: 0.6250, 0.3398
> Green: 0.2841, 0.6044
> Blue: 0.1494, 0.0644
> White: 0.2802, 0.3105
>
> Established timings supported:
> 640x480@60Hz 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz
> Standard timings supported:
> Detailed mode: Clock 20.900 MHz, 149 mm x 54 mm
> 640 672 672 709 hborder 0
> 480 484 484 491 vborder 0
> -hsync -vsync
> VertFreq: 60 Hz, HorFreq: 29478 Hz
> Monitor ranges (GTF): 52-68Hz V, 26-36kHz H, max dotclock 30MHz
> Dummy block
> Dummy block
> Checksum: 0x6b (valid)
>
> Now, current implementation is still flawed, as HDMI uses the
> HPD signal to indicate that the source should re-read the EDID
> due to change in device capabilities. With current HPD polling
> implementation we would most certainly miss those notifications
> as one can try just swapping two HDMI monitors really fast.
>
> Proper fix would be skipping the HPD pin detection and relying
> on just EDID fetching and acting on its changes.
HPD has been a hard requirement since DDWG came up with DVI somewhere in
the late 90s. This monitor is plainly broken, and should not get an
expensive i2c address polling based workaround at the driver level.
Luc Verhaegen.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-03-04 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 13:06 [RESEND PATCH] drm/sun4i: hdmi: Improve compatibility with hpd-less HDMI displays Priit Laes
2019-03-04 13:31 ` Luc Verhaegen [this message]
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=20190304133139.GA26394@skynet.be \
--to=libv@skynet.be \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux@armlinux.org.uk \
--cc=maxime.ripard@bootlin.com \
--cc=plaes@plaes.org \
--cc=priit.laes@paf.com \
--cc=wens@csie.org \
/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;
as well as URLs for NNTP newsgroup(s).