From: Archit Taneja <architt@codeaurora.org>
To: Eric Anholt <eric@anholt.net>,
dri-devel@lists.freedesktop.org,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Thierry Reding <thierry.reding@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] drm/bridge: Support hotplugging panel-bridge.
Date: Fri, 16 Jun 2017 11:13:01 +0530 [thread overview]
Message-ID: <777ee1b1-e5ce-ea29-8a48-f792354a22d1@codeaurora.org> (raw)
In-Reply-To: <20170615204130.19255-2-eric@anholt.net>
On 06/16/2017 02:11 AM, Eric Anholt wrote:
> If the panel-bridge is being set up after the drm_mode_config_reset(),
> then the connector's state would never get initialized, and we'd
> dereference the NULL in the hotplug path. We also need to register
> the connector, so that userspace can get at it.
>
Shouldn't the KMS driver make sure the panel-bridge is set up before
drm_mode_config_reset? Is it the case when we're inserting the
panel-bridge driver as a module?
All the connectors that have been added are registered automatically
when drm_dev_register() is called by the KMS driver. Registering a
connector in the middle of setting up our driver is prone to race
conditions if the userspace decides to use them immediately.
Thanks,
Archit
> Signed-off-by: Eric Anholt <eric@anholt.net>
> ---
> drivers/gpu/drm/bridge/panel.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/bridge/panel.c b/drivers/gpu/drm/bridge/panel.c
> index 67fe19e5a9c6..8ed8a70799c7 100644
> --- a/drivers/gpu/drm/bridge/panel.c
> +++ b/drivers/gpu/drm/bridge/panel.c
> @@ -82,11 +82,14 @@ static int panel_bridge_attach(struct drm_bridge *bridge)
>
> drm_mode_connector_attach_encoder(&panel_bridge->connector,
> bridge->encoder);
> + drm_atomic_helper_connector_reset(&panel_bridge->connector);
>
> ret = drm_panel_attach(panel_bridge->panel, &panel_bridge->connector);
> if (ret < 0)
> return ret;
>
> + drm_connector_register(&panel_bridge->connector);
> +
> return 0;
> }
>
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-06-16 5:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 20:41 [PATCH 0/7] RPi touchscreen as a panel driver again Eric Anholt
2017-06-15 20:41 ` [PATCH 1/7] drm/bridge: Support hotplugging panel-bridge Eric Anholt
2017-06-16 5:43 ` Archit Taneja [this message]
2017-06-16 14:43 ` Eric Anholt
2017-06-20 3:48 ` Archit Taneja
2017-06-20 7:31 ` Laurent Pinchart
2017-06-20 17:31 ` Eric Anholt
2017-06-22 7:50 ` Benjamin Gaignard
2017-06-22 8:17 ` Archit Taneja
2017-06-22 9:23 ` Boris Brezillon
2017-06-22 12:29 ` Andrzej Hajda
2017-06-22 12:41 ` Boris Brezillon
2017-06-22 13:16 ` Andrzej Hajda
2017-06-22 13:34 ` Boris Brezillon
2017-06-23 7:22 ` Andrzej Hajda
2017-06-23 7:32 ` Boris Brezillon
2017-06-23 13:54 ` Archit Taneja
2017-06-23 21:50 ` Eric Anholt
2017-06-27 6:53 ` Archit Taneja
2017-06-22 9:31 ` Philippe CORNU
2017-06-23 21:36 ` Eric Anholt
2017-06-23 9:04 ` Daniel Vetter
2017-06-15 20:41 ` [PATCH 2/7] drm/vc4: Fix DSI T_INIT timing Eric Anholt
2017-06-15 20:41 ` [PATCH 3/7] drm/vc4: Fix misleading name of the continuous flag Eric Anholt
2017-06-15 20:41 ` [PATCH 4/7] drm/vc4: Use drm_mode_vrefresh() in DSI fixup, in case vrefresh is 0 Eric Anholt
2017-06-15 20:41 ` [PATCH 5/7] dt-bindings: Document the Raspberry Pi Touchscreen nodes Eric Anholt
2017-06-23 18:44 ` Rob Herring
2017-06-15 20:41 ` [PATCH 6/7] drm/panel: Add support for the Raspberry Pi 7" Touchscreen Eric Anholt
2017-06-15 20:41 ` [PATCH 7/7] ARM: dts: bcm2835: Enable the Raspberry Pi touchscreen panel Eric Anholt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=777ee1b1-e5ce-ea29-8a48-f792354a22d1@codeaurora.org \
--to=architt@codeaurora.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome