Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp181896pxa; Fri, 21 Aug 2020 04:43:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyEJg5w9gZuxfdFqeoFgpH1zsJTjp+a89c+J2JN2/zyZl9L2OTd860bYiE7RRfYMEOinRTW X-Received: by 2002:a17:906:2b57:: with SMTP id b23mr2456917ejg.26.1598010192060; Fri, 21 Aug 2020 04:43:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598010192; cv=none; d=google.com; s=arc-20160816; b=lZ0zPqkr6VKNg9aMnFYptdAgDYESmH2mYsq05p3WWR0KPtWXAdZTZ8hKts70vuKuyk hjdoPZv4g8MQfFGI2KjQbTPO8cyQSODo4ILvwICrBlrXCvv+KNLLitJhRCnXYNgniSIf xRIw0D9fcGBl3aYn52XYFfqI4OQg49rENNNfIxyPmTYbFswdxLUiJYZqorxWs5DsaGwI DG9987Me9bFc4nlS3/aGOSdJaVC3qNyJV/bFFVw2fD7O3cv4+/S2Jkd8MwbjvEVrEByy O2ab2ky0Zt5HjAKLUgvpfl84145zK0KqiHYz7IuloG93mzKaTpLK0WpreOVpvYH3n0Cb 0grw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=9uSN1VFAjh/1GOPyLEgmJC4fQrDMvTsXRZuW05MN98I=; b=uUD1ao/d8F0bvycaaimdcL/2/6RR4CpV0Oxdw2TxXrF1de01IGT6y/hJTa0meJbGL4 V+nwzWGsoj8OL7qsRN9UIMCbyCW+RQ68ZIPRoZDZJg8HTJ5haCXTet8WK5r45lSiyvbx Qbl+x04Z/1QhoADVsjW913KkDB7vYvauShn59FMlhlHVjcQEVL5UJDcqqxuV891JYp2D DfORV0PC5YmqobUhNhaW6+cYLXkLtt/Z0n4GiY8O5GP+odmTjyuC5mKLwIp5R+Y/3YjF eYOPK4pbGuTj8bzD9eqSZY9AtHIBNx8PHGwQafxga4Vs9qN7XYaeZViCGhyorL9vz2Cq fpOA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f12si1246864edx.86.2020.08.21.04.42.48; Fri, 21 Aug 2020 04:43:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728471AbgHULiy (ORCPT + 99 others); Fri, 21 Aug 2020 07:38:54 -0400 Received: from asavdk3.altibox.net ([109.247.116.14]:39102 "EHLO asavdk3.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728344AbgHULiS (ORCPT ); Fri, 21 Aug 2020 07:38:18 -0400 Received: from ravnborg.org (unknown [188.228.123.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by asavdk3.altibox.net (Postfix) with ESMTPS id 96E5E2001E; Fri, 21 Aug 2020 13:38:11 +0200 (CEST) Date: Fri, 21 Aug 2020 13:38:09 +0200 From: Sam Ravnborg To: Enric Balletbo i Serra Cc: Jernej Skrabec , drinkcat@chromium.org, Neil Armstrong , David Airlie , Jonas Karlman , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Andrzej Hajda , Boris Brezillon , Laurent Pinchart , hsinyi@chromium.org, matthias.bgg@gmail.com, Collabora Kernel ML Subject: Re: [PATCH 3/3] drm/bridge: ps8640: Rework power state handling Message-ID: <20200821113809.GA283294@ravnborg.org> References: <20200615205320.790334-1-enric.balletbo@collabora.com> <20200615205320.790334-4-enric.balletbo@collabora.com> <20200620214225.GD74146@ravnborg.org> <0220cfe5-2ac9-2d8b-529d-bb1a61478395@collabora.com> <20200624070738.GA1807736@ravnborg.org> <20b2f097-d789-3f5a-cd7e-3701669f43cb@collabora.com> <5af757da-87ec-c0d1-374d-0a69401e09a3@collabora.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5af757da-87ec-c0d1-374d-0a69401e09a3@collabora.com> X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=f+hm+t6M c=1 sm=1 tr=0 a=S6zTFyMACwkrwXSdXUNehg==:117 a=S6zTFyMACwkrwXSdXUNehg==:17 a=kj9zAlcOel0A:10 a=WqFqRLcIwFt0jbhFSLsA:9 a=CjuIK1q_8ugA:10 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Enric. > > Let me reformulate the question for if it was not clear. > > What I did is be able to read the EDID every time userspace asks for it (so > kernel enables all the required) and Sam is proposing to just fail if all is not > setup. I can obviously do this but my question is, at which point I should leave > all the logic enabled to be able to read the EDID (after probe?, after > pre_enable, after enable?) It is not clear for me from the API. I am not clear if my suggestion is a good suggestion. I recall I saw something similar in another bridge driver. If no-one else chimes in then go ahead with your original approach where there is less restriction when it is possible to read edid. Sam