From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756917AbcK2WAE (ORCPT ); Tue, 29 Nov 2016 17:00:04 -0500 Received: from mail.free-electrons.com ([62.4.15.54]:42475 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932818AbcK2V7o (ORCPT ); Tue, 29 Nov 2016 16:59:44 -0500 Date: Tue, 29 Nov 2016 22:59:32 +0100 From: Maxime Ripard To: Jean-Francois Moine Cc: Icenowy Zheng , Chen-Yu Tsai , Jernej Skrabec , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com Subject: Re: [RFC PATCH] ARM: dts: sun8i: add simplefb node for H3 Message-ID: <20161129215932.kmk6qodthicadpyb@lukather> References: <20161128095900.27615-1-icenowy@aosc.xyz> <20161128114218.14d2ed434802a20fa6b62023@free.fr> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gdrz6lrmamth7t2u" Content-Disposition: inline In-Reply-To: <20161128114218.14d2ed434802a20fa6b62023@free.fr> User-Agent: Mutt/1.6.2-neo (2016-08-21) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --gdrz6lrmamth7t2u Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 28, 2016 at 11:42:18AM +0100, Jean-Francois Moine wrote: > On Mon, 28 Nov 2016 17:59:00 +0800 > Icenowy Zheng wrote: >=20 > > As there's currently a fork of U-Boot which provides simplefb support > > for H3, a simplefb node can be added to the device tree. > >=20 > > Signed-off-by: Icenowy Zheng > > --- > >=20 > > I'm still not sure which pipeline should I use. > >=20 > > And, it seems that HDMI Slow Clock is not needed? > >=20 > > (seems that it's only for EDID, but simplefb won't use EDID) >=20 > So, I don't see how this may work. > How can the u-boot know the resolutions of the HDMI display device? >=20 > In other words: I have a new H3 board with the last u-boot and kernel. > I plug my (rather old or brand new) HDMI display device. > After powering on the system, I hope to get something on the screen. > How? If it works like the driver for the first display engine in U-Boot, it will use the preferred mode reported by the EDID, and will fallback to 1024x768 if it cannot access it. Maybe it would be worth exchanging on the EDID code that has been done for the u-boot driver too, so that it can be fixed in your driver. Maxime --=20 Maxime Ripard, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com --gdrz6lrmamth7t2u Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJYPfpEAAoJEBx+YmzsjxAgfoIQAIvqtOvlM8Ogt/eMNflfOXwf wMXPiZZDUTsDbFgJA2+5GMdbuDw+X4EfHFSBIVtDf6G8MVH01p60vrwQuyly0mV4 jkSpt0YN9TnllIFzliYS3lBcbnesQQq6qXZyPM3ruHJdeGiEkJ1UPRDXQJF6Sfb8 jybCj72vwATuwfUz+2BFTU7BZIWGYFDrN1d88voyQO2eJb4G3PxfgttBzEUGPReW enOgfj75FqOazCa0LeX23AyS1b70mGqr5LkAn01XJS/sFGGU0AP0OTtRyn6rGwi9 agtsEXmKzLoGZp4qf3ytzKmbvXju99uNAv6UNtg6CAoHAdlezaI0qIjKLvCF95mA 4mKLc5OXZufpO/hqoehEsAksBje3t/jJMBCwn7MlaMTALRoN7gGONoq4VbMesDKl C+uWXYE6cBynQHOqzPgfYh/DQmzcUhYUfpvxPeEQffG6F7HZM1T0HNkCKJqEwP5p taL0lwA+qr50ZYopUohmxqCM1O/d8GUOc0Xlr/Zz7KuYzlTziHOY3zR5kttxOVUF judR0VqfE5JnBy2as5us/oE7+rQcyCi+W58g5qBI6lL/tC9/73/IZ/Ri/K4Jrgbl yI1gM620ici9pj592nt/wQuj/9PbsV/mlmX03sjUvVFWcHJx/lFabSn03nhPnK1K H0psFoGEvHAWTPj7Moqa =iDGv -----END PGP SIGNATURE----- --gdrz6lrmamth7t2u--