From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 768BAC4727F for ; Thu, 1 Oct 2020 09:33:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B02202074B for ; Thu, 1 Oct 2020 09:33:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731657AbgJAJdS (ORCPT ); Thu, 1 Oct 2020 05:33:18 -0400 Received: from new3-smtp.messagingengine.com ([66.111.4.229]:35977 "EHLO new3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725921AbgJAJdS (ORCPT ); Thu, 1 Oct 2020 05:33:18 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id 3587E58023D; Thu, 1 Oct 2020 05:33:17 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Thu, 01 Oct 2020 05:33:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cerno.tech; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=X/hpZ4Y0ZMB/Qo1FM7dGX0+GqSj 9NQP7x2y+aZc2fP4=; b=YhzrqexPITb9eIHNrD4+gScUkQE9DitYdPele8TYbn/ aAEWxee68iNJfcXwf9lNRQSY8RoQAyTn7/r7Uc8AtgLd6Pix9os033nWhSLUZgSR hdZw+Hjp+KKXdDeeAfKXK6B4Qth+OzQWVoelivsZgkSWjnSatYxRsWAvI0j4XgyB TU45E9jc02aUSycslDFnu24K3+j44oni+YL0sDCyoPaI4eBUbi5m9MRBy+dcGRyv mbnwScdG1ShDDjv//5IbsN6lDDvQMPoo27xCgdQaHVn18o7jToZUKW4abBKVmIla yrre8y2tAE/tD4y3nDL7xY9dMyc0p4SChRrDKYHBRDQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=X/hpZ4 Y0ZMB/Qo1FM7dGX0+GqSj9NQP7x2y+aZc2fP4=; b=XMMnA9n6/Q1D1lx/9DuaNH gT8QDwdHnccc4+I9Pkc6SN6HnGAG1M2zPEwxGaYtUrud7fnaQLXn/xfzyCC2lcd0 dvF0ckIdH30WsGn08f1wd3Osug2xXk9bzH12usPsIq3j+5yhqPrbUNSMkBOzDezy llTf9gDt5ko4UCd0oU4YdoCdz0skrbRg1OurSFFXw3O5MKaN6DHc/sWP8pCHhW8D 3Dy46DrrdesxYxFdNHvDduQWYvlCvd20HPIVpIwUpoUaVPiH84P6LcL5sB44hs/x 0Gm4iMFoSj3Trzz81PLPpVr04/AOC/tK/vDmF+ixbDLKVn71bmBH1XnL88mPhfVQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrfeeggddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesghdtreertddtvdenucfhrhhomhepofgrgihimhgv ucftihhprghrugcuoehmrgigihhmvgestggvrhhnohdrthgvtghhqeenucggtffrrghtth gvrhhnpeelkeeghefhuddtleejgfeljeffheffgfeijefhgfeufefhtdevteegheeiheeg udenucfkphepledtrdekledrieekrdejieenucevlhhushhtvghrufhiiigvpedtnecurf grrhgrmhepmhgrihhlfhhrohhmpehmrgigihhmvgestggvrhhnohdrthgvtghh X-ME-Proxy: Received: from localhost (lfbn-tou-1-1502-76.w90-89.abo.wanadoo.fr [90.89.68.76]) by mail.messagingengine.com (Postfix) with ESMTPA id A2B92328005D; Thu, 1 Oct 2020 05:33:15 -0400 (EDT) Date: Thu, 1 Oct 2020 11:33:14 +0200 From: Maxime Ripard To: Nicolas Saenz Julienne Cc: Nathan Chancellor , Eric Anholt , Stefan Wahren , Tim Gover , Dave Stevenson , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Hoegeun Kwon , Chanwoo Choi , bcm-kernel-feedback-list@broadcom.com, linux-rpi-kernel@lists.infradead.org, Phil Elwell , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v5 80/80] ARM: dts: bcm2711: Enable the display pipeline Message-ID: <20201001093314.lhph4ykvtjs4bo3i@gilmour.lan> References: <20200929221526.GA1370981@ubuntu-m3-large-x86> <20200930140758.gummt3umouva3wyu@gilmour.lan> <20200930163823.GA237050@ubuntu-m3-large-x86> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="w2hnz5ekr63d3x66" Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --w2hnz5ekr63d3x66 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 01, 2020 at 11:22:03AM +0200, Nicolas Saenz Julienne wrote: > On Wed, 2020-09-30 at 09:38 -0700, Nathan Chancellor wrote: > > On Wed, Sep 30, 2020 at 04:07:58PM +0200, Maxime Ripard wrote: > > > Hi Nathan, > > >=20 > > > On Tue, Sep 29, 2020 at 03:15:26PM -0700, Nathan Chancellor wrote: > > > > On Thu, Sep 03, 2020 at 10:01:52AM +0200, Maxime Ripard wrote: > > > > > Now that all the drivers have been adjusted for it, let's bring i= n the > > > > > necessary device tree changes. > > > > >=20 > > > > > The VEC and PV3 are left out for now, since it will require a mor= e specific > > > > > clock setup. > > > > >=20 > > > > > Reviewed-by: Dave Stevenson > > > > > Tested-by: Chanwoo Choi > > > > > Tested-by: Hoegeun Kwon > > > > > Tested-by: Stefan Wahren > > > > > Signed-off-by: Maxime Ripard > > > >=20 > > > > Apologies if this has already been reported or have a solution but = this > > > > patch (and presumably series) breaks output to the serial console a= fter > > > > a certain point during init. On Raspbian, I see systemd startup mes= sages > > > > then the output just turns into complete garbage. It looks like this > > > > patch is merged first in linux-next, which is why my bisect fell on= the > > > > DRM merge. I am happy to provide whatever information could be help= ful > > > > for debugging this. I am on the latest version of the firmware > > > > (currently 26620cc9a63c6cb9965374d509479b4ee2c30241). > > >=20 > > > Unfortunately, the miniUART is in the same clock tree than the core > > > clock and will thus have those kind of issues when the core clock is > > > changed (which is also something that one should expect when using the > > > DRM or other drivers). > > >=20 > > > The only real workaround there would be to switch to one of the PL011 > > > UARTs. I guess we can also somehow make the UART react to the core cl= ock > > > frequency changes, but that's going to require some effort > > >=20 > > > Maxime > >=20 > > Ack, thank you for the reply! There does not really seem to be a whole > > ton of documentation around using one of the other PL011 UARTs so for > > now, I will just revert this commit locally. >=20 > Nathan, a less intrusive solution would be to add 'core_freq_min=3D500' i= nto your > config.txt. >=20 > Funnily enough core_freq=3D500 doesn't seem to work in that regard. It mi= ght be > related with what Maxime is commenting. Yeah, it fixes it here too Maxime --w2hnz5ekr63d3x66 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCX3WiWgAKCRDj7w1vZxhR xWyxAQCtT5n06PgaXjEzDsoo3iXgImo6rhnYHyBeb1jzJfG1XwEAimejVcajmPWZ 7Drs6MnyiOSSnqXdn9aEsubATlxJags= =6Z6g -----END PGP SIGNATURE----- --w2hnz5ekr63d3x66--