Received: by 10.192.165.148 with SMTP id m20csp3112089imm; Mon, 7 May 2018 06:54:36 -0700 (PDT) X-Google-Smtp-Source: AB8JxZorGHWoQu3SJ8XCZHIGUiZ5bK9RoqF4kdaI6qgJafLERWuE54AQG43ngjV3nJA3cUt6wRtD X-Received: by 2002:a17:902:a717:: with SMTP id w23-v6mr5247812plq.130.1525701276184; Mon, 07 May 2018 06:54:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525701276; cv=none; d=google.com; s=arc-20160816; b=ilpwnOlQmB2FfwGuNPXNRx8WivehtotTB05QjD2k0pzTz4RmdcToMyomdmgq2eZW4t HwahwkNJ6e/nzh9nzlLBcI/3ieg1yLuSBksoGPUglLdILO2yQrK8g76xukkU0twDe61H M5foRFeYhDGInJNf5ihuJLRWrnmw9Fn5dYh52kh2b7pq3nRI1GnfY50BRuIVE07zQw7h alRev7QN2SDDNVYEMTF2bmD1tUZG85lq7DlsDS6i95H9lS0vmQhVWDOOUACQyfsUZL/W E3D8k3aHI99z+6bL447foyuX5jOow7jBfVV/YwqahPvsorVm5zMkz4yTJzRrGsfXaooZ am9Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=H6jsBUPEPY+xogQCYPeeSEYS1GN3NwSVqh7y1WLdonI=; b=vJ9ZvUAb2fRFRujTD2hsguYk21Ub4BHUogJUudEclGMH5uzIShacqaTYtyHDyN2tYq Vc+rt0Tu18lLRk6KqET1FXNnICBa8FP6ggotJmL2d3722whi5NmmkpSWOLSXGJvuFs+m zOvw76mKOMwWV8eg6CHJJgs7+kJsZYw8gpII0E43gcLChq3vKHB10Q1uMNWWVa0PE0fk /tVLXTBp/Y8DF2T1GXl2Laipnt5M1Cbb48LNzPS6QVLOX+Ws9oSracZM0KH+kibus2Dr mzP548cauANXJejkvdE7GtBkYhUjPRdE9BiZab6sWDURlezwBE49o/n7Q3fe0E7iEyLw QRvw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@ffwll.ch header.s=google header.b=eH4wEypA; 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 d1-v6si23256473plr.410.2018.05.07.06.54.21; Mon, 07 May 2018 06:54:36 -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; dkim=fail header.i=@ffwll.ch header.s=google header.b=eH4wEypA; 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 S1752364AbeEGNxu (ORCPT + 99 others); Mon, 7 May 2018 09:53:50 -0400 Received: from mail-wm0-f68.google.com ([74.125.82.68]:36044 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752098AbeEGNxp (ORCPT ); Mon, 7 May 2018 09:53:45 -0400 Received: by mail-wm0-f68.google.com with SMTP id n10-v6so15537613wmc.1 for ; Mon, 07 May 2018 06:53:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=H6jsBUPEPY+xogQCYPeeSEYS1GN3NwSVqh7y1WLdonI=; b=eH4wEypANojVwEahF/51QL24RT+25W2d29ssufS7fqfWTWGNrVJ7kYS3a4NVO3hp6r zmjT+BCAUGy3v6yCEjKNP1ZDIpWUkZSe9rzyPoaLjW954fd3ddgi4XgRgz06R0nksbud c05LS3aiFtg5/FxaCxCWKXfd+7u5fvMxMG53Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=H6jsBUPEPY+xogQCYPeeSEYS1GN3NwSVqh7y1WLdonI=; b=q9Uimilg9DGROUbA62uv0WJv/yJQqSn8+qlfj6Dfrj07BDOo7DPtfYlrZn6+fPTLoS QOL0AMpkzCZy4XVWqCWETJ/DxunDs79RG+gBUhksGOEWwZPCWasSTqRCbtN0LPwQbkQq qB4+U/uSyRqAx92XIrJFT6YeHGDvQk2Z6j7rvGf7B/ID0ut7a6XGhQrpFfkJe6rBfDOQ VbXY7f6U71MjYS60MCWNaVPrr8A8rpD/OHCBZkJCgolcCp1R906KOqOMSTzJHZnAlrIA nofUVJjEwZ9J3wKU9yf9wx60vwTq2k0/1k/zm7VzGQ+0PxkZMXPEjr5v6UtuUSwCnXYM F+Kw== X-Gm-Message-State: ALQs6tAx9shSikX67YdfZP+Ge8dnfJwVQm/fjgubB1oPg06/PMuk0R8K SKtDZI0Fa1MuYUVx5BcL0d5dJw== X-Received: by 2002:a50:b2e4:: with SMTP id p91-v6mr36122291edd.84.1525701224524; Mon, 07 May 2018 06:53:44 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:5635:0:39d2:f87e:2033:9f6]) by smtp.gmail.com with ESMTPSA id v22-v6sm12219741edq.15.2018.05.07.06.53.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 07 May 2018 06:53:43 -0700 (PDT) Date: Mon, 7 May 2018 15:53:41 +0200 From: Daniel Vetter To: Andrzej Hajda Cc: Peter Rosin , linux-kernel@vger.kernel.org, Archit Taneja , Laurent Pinchart , David Airlie , Peter Senna Tschudin , Martin Donnelly , Martyn Welch , Gustavo Padovan , Maarten Lankhorst , Sean Paul , Inki Dae , Joonyoung Shim , Seung-Woo Kim , Kyungmin Park , Kukjin Kim , Krzysztof Kozlowski , CK Hu , Philipp Zabel , Matthias Brugger , Rob Clark , Sandy Huang , Heiko =?iso-8859-1?Q?St=FCbner?= , Benjamin Gaignard , Vincent Abriou , dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org, linux-renesas-soc@vger.kernel.org, linux-rockchip@lists.infradead.org, Jyri Sarha , Daniel Vetter Subject: Re: [PATCH v2 26/26] drm/bridge: establish a link between the bridge supplier and consumer Message-ID: <20180507135341.GI12521@phenom.ffwll.local> Mail-Followup-To: Andrzej Hajda , Peter Rosin , linux-kernel@vger.kernel.org, Archit Taneja , Laurent Pinchart , David Airlie , Peter Senna Tschudin , Martin Donnelly , Martyn Welch , Gustavo Padovan , Maarten Lankhorst , Sean Paul , Inki Dae , Joonyoung Shim , Seung-Woo Kim , Kyungmin Park , Kukjin Kim , Krzysztof Kozlowski , CK Hu , Philipp Zabel , Matthias Brugger , Rob Clark , Sandy Huang , Heiko =?iso-8859-1?Q?St=FCbner?= , Benjamin Gaignard , Vincent Abriou , dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org, linux-renesas-soc@vger.kernel.org, linux-rockchip@lists.infradead.org, Jyri Sarha References: <20180504135212.26977-1-peda@axentia.se> <20180504135212.26977-27-peda@axentia.se> <4cdcd215-8caf-e045-a478-f438f128c9f2@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4cdcd215-8caf-e045-a478-f438f128c9f2@samsung.com> X-Operating-System: Linux phenom 4.15.0-3-amd64 User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 07, 2018 at 02:59:45PM +0200, Andrzej Hajda wrote: > On 04.05.2018 15:52, Peter Rosin wrote: > > If the bridge supplier is unbound, this will bring the bridge consumer > > down along with the bridge. Thus, there will no longer linger any > > dangling pointers from the bridge consumer (the drm_device) to some > > non-existent bridge supplier. > > I understand rationales behind this patch, but it is another step into > making drm_dev one big driver with subcomponents, where drm will work > only if every subcomponent is working/loaded. Do we need to go this way? > In case of many platforms such approach results in display turned on > very late on boot for example due to late initialization of some > regulator exposed by some i2c device, which is used by hdmi bridge. And > this hdmi bridge is just to provide alternative(rarely used) display > path, the main display path would work anyway. > > So the main question to drm maintainers is about evolution of bridges, > if drm_bridges should become mandatory components of drm device or they > could be added/removed dynamically? This is already the case. You currently cannot hotplug a drm_bridge, everything must be present. I don't think it makes sense to change that until we have physically hotpluggable drm_bridges in real hardware. I definitely don't want to refcount stuff to work around driver load bonghits on DT platforms, because refcounting is way too hard to get right :-) Afaik there's out-of-tree patches to solve 99% of the driver load fun on DT platforms, but because it's not a 100% solution it's blocked since forever. -Daniel > > Regards > Andrzej > > > > > > Signed-off-by: Peter Rosin > > --- > > drivers/gpu/drm/drm_bridge.c | 18 ++++++++++++++++++ > > include/drm/drm_bridge.h | 2 ++ > > 2 files changed, 20 insertions(+) > > > > diff --git a/drivers/gpu/drm/drm_bridge.c b/drivers/gpu/drm/drm_bridge.c > > index 78d186b6831b..0259f0a3ff27 100644 > > --- a/drivers/gpu/drm/drm_bridge.c > > +++ b/drivers/gpu/drm/drm_bridge.c > > @@ -26,6 +26,7 @@ > > #include > > > > #include > > +#include > > #include > > > > #include "drm_crtc_internal.h" > > @@ -127,12 +128,25 @@ int drm_bridge_attach(struct drm_encoder *encoder, struct drm_bridge *bridge, > > if (bridge->dev) > > return -EBUSY; > > > > + if (encoder->dev->dev != bridge->odev) { > > + bridge->link = device_link_add(encoder->dev->dev, > > + bridge->odev, 0); > > + if (!bridge->link) { > > + dev_err(bridge->odev, "failed to link bridge to %s\n", > > + dev_name(encoder->dev->dev)); > > + return -EINVAL; > > + } > > + } > > + > > bridge->dev = encoder->dev; > > bridge->encoder = encoder; > > > > if (bridge->funcs->attach) { > > ret = bridge->funcs->attach(bridge); > > if (ret < 0) { > > + if (bridge->link) > > + device_link_del(bridge->link); > > + bridge->link = NULL; > > bridge->dev = NULL; > > bridge->encoder = NULL; > > return ret; > > @@ -159,6 +173,10 @@ void drm_bridge_detach(struct drm_bridge *bridge) > > if (bridge->funcs->detach) > > bridge->funcs->detach(bridge); > > > > + if (bridge->link) > > + device_link_del(bridge->link); > > + bridge->link = NULL; > > + > > bridge->dev = NULL; > > } > > > > diff --git a/include/drm/drm_bridge.h b/include/drm/drm_bridge.h > > index b656e505d11e..804189c63a4c 100644 > > --- a/include/drm/drm_bridge.h > > +++ b/include/drm/drm_bridge.h > > @@ -261,6 +261,7 @@ struct drm_bridge_timings { > > * @list: to keep track of all added bridges > > * @timings: the timing specification for the bridge, if any (may > > * be NULL) > > + * @link: drm consumer <-> bridge supplier > > * @funcs: control functions > > * @driver_private: pointer to the bridge driver's internal context > > */ > > @@ -271,6 +272,7 @@ struct drm_bridge { > > struct drm_bridge *next; > > struct list_head list; > > const struct drm_bridge_timings *timings; > > + struct device_link *link; > > > > const struct drm_bridge_funcs *funcs; > > void *driver_private; > > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch