From: Adam Jackson Subject: Re: [PATCH] drm/i915/pch: Save/restore PCH_PORT_HOTPLUG across suspend Date: Wed, 27 Jul 2011 09:43:11 -0400 Message-ID: <1311774192.1723.33.camel@atropine> References: <1311713586-23557-1-git-send-email-ajax@redhat.com> <20110726140032.7fb350a0@jbarnes-desktop> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1484853917==" Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by gabe.freedesktop.org (Postfix) with ESMTP id 5CB809E793 for ; Wed, 27 Jul 2011 06:43:13 -0700 (PDT) In-Reply-To: <20110726140032.7fb350a0@jbarnes-desktop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Jesse Barnes Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org --===============1484853917== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-YIbWkXRjuOpKUMY+wch4" --=-YIbWkXRjuOpKUMY+wch4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2011-07-26 at 14:00 -0700, Jesse Barnes wrote: > We should be writing this reg. The only question is whether we should > be trusting the BIOS values (which may have custom pulse duration > settings) or just unconditionally enabling hot plug for ports we care > about with the default 2ms pulse width (per the DP spec). >=20 > If we assume the BIOS programs this reg to a good value (a very big > assumption) saving and restoring it is safest. I just wonder if we'll > find machines where it's broken by default leading to weird DP behavior. Another option is reading the HPD input enable bits from the platform value, but setting the pulse width ourselves. I have a vague fear of enabling HPD for all ports blindly, I suspect there's some platform out there that miswires things such that if we did we'd get an infinite irq storm. IWBNI the documentation for the pulse width bits in that reg was worded a bit more clearly. It's not completely clear whether the "short pulse duration" part sets a minimum or maximum. My reading interprets it as minimum, but then one wonders what the long pulse duration is. I'll play around with it a bit more. If - as evidence seems to suggest - we're really getting two HPD IRQs for each plug, then there's probably a good reason for it which the code should reflect. - ajax --=-YIbWkXRjuOpKUMY+wch4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEABECAAYFAk4wFe8ACgkQW4otUKDs0NMTagCeN4RT2E0WbZqG3rdzA9w/FRE1 hncAnArXysqjKPAHVlmqfboKsq9z9ljl =ZzlO -----END PGP SIGNATURE----- --=-YIbWkXRjuOpKUMY+wch4-- --===============1484853917== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============1484853917==--