Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp2947000pxu; Mon, 7 Dec 2020 22:23:59 -0800 (PST) X-Google-Smtp-Source: ABdhPJxSitxla6+BldswoTQZ2DR/u9lHE3gMMH9OzCWjRr1NBqueiXecEZtcR3yDD5g7OrcnW5CW X-Received: by 2002:a17:906:fb9b:: with SMTP id lr27mr22460381ejb.175.1607408639142; Mon, 07 Dec 2020 22:23:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607408639; cv=none; d=google.com; s=arc-20160816; b=uIY3UZt9ETIV51/OyMaHlu3Fb2VqXm1Svsa/Q15qsR66v4/3F0tKgxs27I79TY+6ud lKEiZx7kjbwxhdQ5KpCCSyYKcYnLcHFUGpUuo58ilYGy52zQ3nPe4FZYWZrl/WT9JER1 sDOCex2EyhpXkISri97OtodCfRw4CW/mFCqhDOjk73ZhlBeFTc2AOxucjzWXXyMKUv9C DmmyYLwNGZCw3HrYBXM/7m2/fh58C1yRpXqtxK3guE3H/5438FRtCsrpHMqVXjE6dPAE 2yb2h/O5N2842OgcNxS161Cn0rizduyXqEMz86xPEgHLrshTQtKhoXe4uA/X9QV6lj0Z pnzg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=kona2eM0qXcbkBAmoaqF+fQGQ1zMy08WyKLleCF6hKo=; b=1CNIUqN1BlYB2Xae6JU0/eQkLx2fwh59aFSJSY0IkOVnH/LUkwNcoWqIkt0uZL+6t8 TIx9UOaRmSh4X95ve4mgFeKB3VHBiaCvwa2cwZViISGFqfClf10y88Oi0KYDe90qJ2p3 cb3DQuyUqLIP5UqV7OrgDPBA/NTYca8tlmsVfqh8REYpiR/x1KzRCmdlKDV/ehkpsSfz 3nyD2Cvgei/M4Z8xFcgaj/HAl7k2RP7XChMxwBRxmIjnY12lwEL0I9dhxzpOdat7EId0 XMMkCLJ8NSyZt/6FcbsjNyylWO0fp9alM57R0Cb4icW+nLZaGA5vQociPztr1TWVL0WG WYMQ== 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 z10si10714123edp.346.2020.12.07.22.23.36; Mon, 07 Dec 2020 22:23:59 -0800 (PST) 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 S1726417AbgLHFtr (ORCPT + 99 others); Tue, 8 Dec 2020 00:49:47 -0500 Received: from asavdk4.altibox.net ([109.247.116.15]:59832 "EHLO asavdk4.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726338AbgLHFtr (ORCPT ); Tue, 8 Dec 2020 00:49:47 -0500 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 asavdk4.altibox.net (Postfix) with ESMTPS id 448C080684; Tue, 8 Dec 2020 06:48:57 +0100 (CET) Date: Tue, 8 Dec 2020 06:48:55 +0100 From: Sam Ravnborg To: Bjorn Andersson Cc: Thierry Reding , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Daniel Vetter , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH] drm/panel: Make backlight attachment lazy Message-ID: <20201208054855.GA18863@ravnborg.org> References: <20201208044446.973238-1-bjorn.andersson@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201208044446.973238-1-bjorn.andersson@linaro.org> X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=Itgwjo3g c=1 sm=1 tr=0 a=S6zTFyMACwkrwXSdXUNehg==:117 a=S6zTFyMACwkrwXSdXUNehg==:17 a=kj9zAlcOel0A:10 a=KKAkSRfTAAAA:8 a=KJCBkObgxTU_UUeBqkUA:9 a=CjuIK1q_8ugA:10 a=cvBusfyB2V15izCimMoJ:22 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Bjorn, On Mon, Dec 07, 2020 at 10:44:46PM -0600, Bjorn Andersson wrote: > Some bridge chips, such as the TI SN65DSI86 DSI/eDP bridge, provides > means of generating a PWM signal for backlight control of the attached > panel. The provided PWM chip is typically controlled by the > pwm-backlight driver, which if tied to the panel will provide DPMS. > > But with the current implementation the panel will refuse to probe > because the bridge driver has yet to probe and register the PWM chip, > and the bridge driver will refuse to probe because it's unable to find > the panel. > > Mitigate this catch-22 situation by allowing the panel driver to probe > and retry the attachment of the backlight as the panel is turned on or > off. > > Signed-off-by: Bjorn Andersson > --- > drivers/gpu/drm/drm_panel.c | 47 +++++++++++++++++++++++++++---------- > include/drm/drm_panel.h | 8 +++++++ > 2 files changed, 43 insertions(+), 12 deletions(-) > > diff --git a/drivers/gpu/drm/drm_panel.c b/drivers/gpu/drm/drm_panel.c > index f634371c717a..7487329bd22d 100644 > --- a/drivers/gpu/drm/drm_panel.c > +++ b/drivers/gpu/drm/drm_panel.c > @@ -43,6 +43,34 @@ static LIST_HEAD(panel_list); > * take look at drm_panel_bridge_add() and devm_drm_panel_bridge_add(). > */ > > +#if IS_REACHABLE(CONFIG_BACKLIGHT_CLASS_DEVICE) > +static int drm_panel_of_backlight_lazy(struct drm_panel *panel) > +{ > + struct backlight_device *backlight; > + > + if (!panel || !panel->dev) > + return -EINVAL; > + > + backlight = devm_of_find_backlight(panel->dev); > + > + if (IS_ERR(backlight)) { > + if (PTR_ERR(backlight) == -EPROBE_DEFER) { > + panel->backlight_init_pending = true; > + return 0; > + } > + > + return PTR_ERR(backlight); Use dev_err_probe() > + } > + > + panel->backlight = backlight; > + panel->backlight_init_pending = false; > + > + return 0; > +} > +#else > +static int drm_panel_of_backlight_lazy(struct drm_panel *panel) { return 0; } > +#endif > + > /** > * drm_panel_init - initialize a panel > * @panel: DRM panel > @@ -161,6 +189,9 @@ int drm_panel_enable(struct drm_panel *panel) > return ret; > } > > + if (panel->backlight_init_pending) > + drm_panel_of_backlight_lazy(panel); > + > ret = backlight_enable(panel->backlight); > if (ret < 0) > DRM_DEV_INFO(panel->dev, "failed to enable backlight: %d\n", > @@ -187,6 +218,9 @@ int drm_panel_disable(struct drm_panel *panel) > if (!panel) > return -EINVAL; > > + if (panel->backlight_init_pending) > + drm_panel_of_backlight_lazy(panel); > + > ret = backlight_disable(panel->backlight); > if (ret < 0) > DRM_DEV_INFO(panel->dev, "failed to disable backlight: %d\n", > @@ -328,18 +362,7 @@ EXPORT_SYMBOL(of_drm_get_panel_orientation); > */ > int drm_panel_of_backlight(struct drm_panel *panel) > { > - struct backlight_device *backlight; > - > - if (!panel || !panel->dev) > - return -EINVAL; > - > - backlight = devm_of_find_backlight(panel->dev); > - > - if (IS_ERR(backlight)) > - return PTR_ERR(backlight); > - > - panel->backlight = backlight; > - return 0; > + return drm_panel_of_backlight_lazy(panel); Could you update the drm_panel_of_backlight() implementation (and do not forget the documentation) and avoid drm_panel_of_backlight_lazy()? Sam > } > EXPORT_SYMBOL(drm_panel_of_backlight); > #endif > diff --git a/include/drm/drm_panel.h b/include/drm/drm_panel.h > index 33605c3f0eba..b126abebb2f3 100644 > --- a/include/drm/drm_panel.h > +++ b/include/drm/drm_panel.h > @@ -149,6 +149,14 @@ struct drm_panel { > */ > struct backlight_device *backlight; > > + /** > + * @backlight_init_pending > + * > + * Backlight driver is not yet available so further attempts to > + * initialize @backlight is necessary. > + */ > + bool backlight_init_pending; > + We have not done so today for other fields, but it would be good to document this is for drm_panel use only and drivers shall not touch. Sam