Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp2580663ybh; Mon, 9 Mar 2020 08:43:04 -0700 (PDT) X-Google-Smtp-Source: ADFU+vsAjqS51A8xaCXubOCyJzdDx7LXizu0mM5v24ezBCfCgFBwSabh7K+e6EnEHxpeZ5jxqwiP X-Received: by 2002:aca:56c2:: with SMTP id k185mr6305674oib.141.1583768578393; Mon, 09 Mar 2020 08:42:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1583768578; cv=none; d=google.com; s=arc-20160816; b=Dfn4ZVvTZBlitremJ4Uv5m/wygolOKfhnuzfTaN6lIyLkWYBg32oCrv829UbPBaTkM svLL1WWwsxDOtCq95lrKqRMLUAQeYXACXjJ3jMvL7LitX8O/XdYP9Gf8VOLrcAHUiCjp Q2rXtPnEmFZy5amlR3b1+KzcNGOP6ciqyDGy48DQyH1XXL4y1Mm3Au0jJeKMZtAwX+SY W4d0Z0rlikTZChdOriCEMqR6DwFQrK+C6e1RSSQqUYje1VYD3Li/S/RW5Aux1R4kjz7N AHlnAiCZROssJ9orhRA3WBZoI93IZP5Oft+DxqsBDL6LXQ5MvHO5MNciwRtgJE/pHJyT zLmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:from:subject; bh=qjhS1O/R0gf+B9kRW1XZBljKmR5pkbgbmjsinXbYLjc=; b=hsVwwrFd7pGiQ9HXj577eF6m9J7FYOOFvp/QNEBFjcqpHJ1Rpg7P+MHOARhZ9emg+B P0SvNY5Ts6jUIjHwqkBc/QIESJsi3YGSqqn9H/8jNez7iyMcoh2heGZwS+RurEDUxHw6 c0dmzsFRdf529+fTZ0g/m5czxmhMPrL6U9IKvYcYXK/CRxRrmbdUcFB5BrO8FDmCYhVH guQbY06lKLVEB9wWaXU6b8I+tzfOHWb0Tne0cv66SLY0zlIdmmFE/QkLaRaZhLtke8Mu 93/ExW1aepnNRlLtNnEUrw7Q76kLSmJGQvHer7V4zHXT42haiCrn4xvLUBMQHxoWWPU+ jKNw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w7si1348698otj.281.2020.03.09.08.42.45; Mon, 09 Mar 2020 08:42:58 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727142AbgCIPlY (ORCPT + 99 others); Mon, 9 Mar 2020 11:41:24 -0400 Received: from mout.kundenserver.de ([212.227.17.13]:49707 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726926AbgCIPlY (ORCPT ); Mon, 9 Mar 2020 11:41:24 -0400 Received: from [192.168.178.72] ([109.104.48.84]) by mrelayeu.kundenserver.de (mreue108 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MKbXu-1ium9B35Dg-00Kyek; Mon, 09 Mar 2020 16:41:09 +0100 Subject: Re: [PATCH] ARM: dts: bcm283x: Use firmware PM driver for V3D From: Stefan Wahren To: Nicolas Saenz Julienne , Rob Herring , Mark Rutland , Florian Fainelli , Ray Jui , Scott Branden , bcm-kernel-feedback-list@broadcom.com, Eric Anholt Cc: devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, wahrenst@gmx.net References: <20200303173217.3987-1-nsaenzjulienne@suse.de> <736f0c59-352b-03b2-f77f-bfc22171b3fb@i2se.com> <03fcb1e2bc7f3ff389b6dfbf3964e159a93ae835.camel@suse.de> <01ceb60e-a791-b6ca-352e-ad2e79f264e3@i2se.com> Message-ID: Date: Mon, 9 Mar 2020 16:41:07 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <01ceb60e-a791-b6ca-352e-ad2e79f264e3@i2se.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Provags-ID: V03:K1:bO13uPSY3dmn10K0yyew7rJcTEabzPG7iig+bLHIqMdpoENbY+b i5HPjy0tu/jYA0LrpGE+k0GsKdKtgwqmRIj9y1ptLNcbLmd9N+F9KEFtjZGij4I37XblbUq fqQ9peqnPWdyim6yKiTK7tFw2kP8moAwNhgBKv4YRUmkoVKcXCSVJOt2Luvm0g26hOIMQIV NLsBaNij49eW2oy8Oes0A== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:x2sZWdZtJyo=:I/UXkQxEboRRIvWWiPhTa0 VMx+4afGgdfVE7WafXkNF9ptPv3Ds9xntQBroxJRda+hEKq19GQxZ4iLEiT6P1eaWkc+8gxE6 I/4azArlMrE8SO8Kr97+j0xAS+lZ7TyFoUtjw40Vl/JptNfNjZTx/gEVMiuXar3qTXPFoy5fC w4drlHOMVBo4nST9iA2cAOTO0MrWHT8IQSt8NY/0ESe8lervSYyr5B6+iZ88X7gs5MMDQnwm0 F/xmt4Rs4tN6xHN5u3WDF3P4uijVgswW+LIIClb6xrdr4iaAtJnEoHA7hIDmcYzm2xi3nXqHS w3ZzTdaLbPqjrU88ATC2htvx1WXcX4vLly8+pk9IYtGY6ugUui47lqGGxrdQp826YEf5n9Gdg cLpWITFvZScth3CGKANFdcCb5iwr86D024EzDIyioXO87pW2loOedI2sR8APOzbUkySsUmBfp z3nzZd9a6Zsl25bhfwPlee67S0AL/PAj0dHftkZjYbt+Ej/qC1YdRg86KAV1P8/E9opufkKXZ yUJmRcph+DYgMJbBTJkzPq86wWLmvCZtACs1I0ypq4w8FtJKBiSAtht2Y8kiKSct3JDPDJk87 0YepSuA9fHWuzB7tTJxS4tmm+9yZ8OuP//2cg1Jrtlh+YYe2z2HnfVkhviyNbd1xP0cIG2xYG 2MoYu9IE89vaDn1cNl4iS+jSUK1ktzsIVDQRy88mWLKW0fwJl4AEAaVFayaLfeywknATWUhhg i2FvWKMqHWdtYJlgOp18OsR79VSww0K4QQLkKWsyRlcVT9xG6InshXOYiMJlERrw8frm7X0oJ xz4GcfbDOOZXkqa4d35peC4wd2ecz5UicCRzKeKd499dIH+CoJwM4v+g06yUPzL+wgx+OX+ Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Nicolas, On 06.03.20 21:33, Stefan Wahren wrote: > Hi Nicolas, > > Am 05.03.20 um 11:44 schrieb Nicolas Saenz Julienne: >> Hi Stefan, >> >> On Tue, 2020-03-03 at 20:24 +0100, Stefan Wahren wrote: >>>>>> Note: I tested this on RPi3b, RPi3a+ and RPi2b. >>>>> as i already wrote this prevent X to start on current Raspbian on my >>>>> Raspberry Pi 3A+ (multi_v7_defconfig, no u-boot). We must be careful here. >>>>> >>>>> I will take a look at the debug UART. Maybe there are more helpful >>>>> information. >>>> It seems we're seeing different things, I tested this on raspbian >>>> (multi_v7_defconfig) and on arm64. I'll try again from scratch tomorrow. >>> My modifications to the Raspbian image (from 13.2.2020) are little: >>> >>> - specify devicetree to config.txt >>> - change console to ttyS1 and remove "silent" in cmdline.txt >>> - rename all original kernel7*.img >>> - copy dtb and kernel7.img to boot partition >>> - copy kernel modules to root partition >> Would you mind retesting with the latest linux-next? I validated an image based >> on 5.6.0-rc4-next-20200305-00001-g285a7a64cd56 and a fresh raspbian download on >> RPi3a+ without X issues. > i retested with todays linux-next and the issue persists on my RPi 3A+ / > HP ZR2440w with this patch applied. I tested my display with a RPI 3B, 3B+ and a Zero W. All of them had the same issue. Btw i used this display the last years for testing the Raspberry Pi. After that i connected the RPI 3B to my TV screen and it works with the patch applied. > > I will try more hardware combinations tomorrow to see, this issue is > more board or display related. > > Best regards > Stefan > >