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 Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AD855C3DA7A for ; Mon, 2 Jan 2023 13:51:49 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 1098A10E33D; Mon, 2 Jan 2023 13:51:49 +0000 (UTC) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by gabe.freedesktop.org (Postfix) with ESMTPS id 4836710E30C for ; Mon, 2 Jan 2023 13:51:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1672667506; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Yafyz4ioVVvoQAhwV2aIRVvfD9yfwhAh4dPTo7SXFJY=; b=SbGAmqTDs85+QPY3fBBL8d/iNFN4cm2IWZKLg9uuJg/weKA3lzN6OvBzxT9mZhlhlec8Cu wQnCr8s4zvY+cyu9VSA2SlIhPQf9/jOk26S4CQD22xJPFaKYejt8sa8P21BlYe9MjtmrN6 xao+EqKb6r1TfWyT6OVMTAzsVNhFAMo= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-45-GEUwwVr3M8m4HIjq9B3t8w-1; Mon, 02 Jan 2023 08:51:45 -0500 X-MC-Unique: GEUwwVr3M8m4HIjq9B3t8w-1 Received: by mail-wm1-f71.google.com with SMTP id m38-20020a05600c3b2600b003d23f8c6ebdso10422412wms.0 for ; Mon, 02 Jan 2023 05:51:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Yafyz4ioVVvoQAhwV2aIRVvfD9yfwhAh4dPTo7SXFJY=; b=HBamu4UWPy5M2x6kOjg+U1nEuFoldnOfDiLGCikG29SmtN2JZ9tGaaK2Unf2SZSrnN WwqVn1Mt1+5olSjFEVaJODfSW4kIsifF7O+ngFtDb82mcx3CvL5XIF5avm27McjI8ki7 hykvXZ9jaT+SUABWSNhRB9mFQ5tBdnko0ZIvr+SQwWRBo80LeT6LhWva+n40g3GWZYbX uA3t7CD+l9B+V94wTLVunVk2FWVuXvb04c7mFEjfGLvN12+oy8s/zD21sRTLxegKJiJC 6nNzLBukI0Gn9yL71meL5N45GthKV/490JPFh2yI9VEE4TM4v1NfRmsB9NBjegD4/dQF MJFg== X-Gm-Message-State: AFqh2kpPIQzh8dEQXDGSJcUL7sCXDpRIG9sbRU2uqILaqEyPt5O1yBn7 lE1/9wA3SCo4NpsZJ4WyYWlkCGNa9+NPhJs3UD1cb0c8DIVgEzUSG8768YI5HWZ/JTDEc+sC+mX NDfIPDbfBE8zzQzsjCzKCq2x4/74V X-Received: by 2002:a05:600c:3d0e:b0:3d2:3ca2:2d4f with SMTP id bh14-20020a05600c3d0e00b003d23ca22d4fmr31097439wmb.36.1672667503873; Mon, 02 Jan 2023 05:51:43 -0800 (PST) X-Google-Smtp-Source: AMrXdXvbJtUehka09TTHzpZ3/tNKAm+H+SNwIOl23IORGJcibzel5onetyN+N+qYZrSa/x/EZ634SA== X-Received: by 2002:a05:600c:3d0e:b0:3d2:3ca2:2d4f with SMTP id bh14-20020a05600c3d0e00b003d23ca22d4fmr31097417wmb.36.1672667503668; Mon, 02 Jan 2023 05:51:43 -0800 (PST) Received: from [192.168.1.130] (205.pool92-176-231.dynamic.orange.es. [92.176.231.205]) by smtp.gmail.com with ESMTPSA id f18-20020a05600c4e9200b003d35c845cbbsm48786206wmq.21.2023.01.02.05.51.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 02 Jan 2023 05:51:43 -0800 (PST) Message-ID: Date: Mon, 2 Jan 2023 14:51:42 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: [PATCH v4 2/4] drm: panel: Add Himax HX8394 panel controller driver To: =?UTF-8?Q?Ond=c5=99ej_Jirman?= , linux-kernel@vger.kernel.org, =?UTF-8?Q?Kamil_Trzci=c5=84ski?= , Martijn Braam , Sam Ravnborg , Robert Mader , Tom Fitzhenry , Peter Robinson , Onuralp Sezer , dri-devel@lists.freedesktop.org, Maya Matuszczyk , Neal Gompa , linux-arm-kernel@lists.infradead.org, Krzysztof Kozlowski , Jagan Teki , Daniel Vetter , David Airlie , Thierry Reding References: <20221230113155.3430142-1-javierm@redhat.com> <20221230113155.3430142-3-javierm@redhat.com> <20221230154043.7v3zmzqdrnouqzd2@core> <7120dfd4-305f-69ac-fee8-123196ed06a9@redhat.com> <20230102105915.gbfhletcm4dunrlf@core> From: Javier Martinez Canillas In-Reply-To: <20230102105915.gbfhletcm4dunrlf@core> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" Hello Ondřej, On 1/2/23 11:59, Ondřej Jirman wrote: [...] >> Yes, because as you said were debug printks. Feel free to propose adding the >> debug printks if you consider useful for normal usage and not just for devel >> purposes. > > I already did, and used them do debug and fix the issues. This submission just > doesn't include the fixes. > I missed the fixes, I think that cherry-picked and squashed from your tree before you added commit f19ce7bb7d72 ("arm64: dts: rk3399-pinephone-pro: Use unused GPLL for VOPs DCLK") at least. >>> hooks. Have you tested the driver thoroughly with various DRM apps, >>> with DPM/suspend/resume, etc.? >>> >> >> I did not. I wasn't expecting suspend and resume to work on the PPP given its >> support is quite minimal currently. > > System suspend/resume works and is used by distributions. Display blanking is > also used by normal distros, even if you don't use system suspend/resume. > I know but my point was that the PPP mainline support isn't ready to be used as a daily driver in practice. So I didn't consider susped/resume or display blank as a requirement to upstream an initial support for the panel driver. [...] >>> Also, have you checked the clocks are actually configured correctly by the >>> rk3399 cru driver? I have a lot of trouble with that, too. clk driver sometimes >>> selects the fractional clock, but does not give it the necessary >20x difference >>> between input/output clock rates. You'll only notice if you measure clock rates >>> directly, by looking at actual refresh rate, by using some testing DRM app. >>> Clock subsystem sometimes shuffles things around if you switch VOPs and use big >>> VOP for mipi-dsi display, instead of the default small VOP. >>> >> >> I have not. Just verified that the display was working on my PPP and could start >> a mutter wayland session. We could fix the clock configuration as follow-up IMO. > > The display output will be broken after you fix the assigned-clocks in DT to > expected values (use GPLL parent, to make the HW generate the exact pixel clock > defined in the display mode). So this needs to be dealt with now, not later. > > > The driver issues are all known at this time and have fixes available, unlike > a year ago: > My goal was to have some initial support in mainline even if there could be some issues. IMO it is better to use upstream as a baseline and attempt to support the PPP incrementally. But since you are aware of the issues and know what are the available fixes, I'll let you continue with the effort and take care of the patches. Hopefully there may be things that will be helpful, such as the binding schema patch and the collected tags. I can also take care of pushing the DRM bits to the drm-misc-next tree once you feel that those are ready to get merged. -- Best regards, Javier Martinez Canillas Core Platforms Red Hat