| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 10 Mar 2022 15:10:12 -0800
From: Doug Anderson <dianders@...omium.org>
To: Kieran Bingham <kieran.bingham+renesas@...asonboard.com>
Cc: dri-devel <dri-devel@...ts.freedesktop.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Sam Ravnborg <sam@...nborg.org>,
LKML <linux-kernel@...r.kernel.org>,
Andrzej Hajda <andrzej.hajda@...el.com>,
Neil Armstrong <narmstrong@...libre.com>,
Robert Foss <robert.foss@...aro.org>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
Jonas Karlman <jonas@...boo.se>,
Jernej Skrabec <jernej.skrabec@...il.com>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com>
Subject: Re: [PATCH v3 3/3] drm/bridge: ti-sn65dsi86: Support hotplug detection
Hi,
On Thu, Mar 10, 2022 at 7:22 AM Kieran Bingham
<kieran.bingham+renesas@...asonboard.com> wrote:
>
> @@ -1135,6 +1161,36 @@ static void ti_sn_bridge_atomic_post_disable(struct drm_bridge *bridge,
> pm_runtime_put_sync(pdata->dev);
> }
>
> +static enum drm_connector_status ti_sn_bridge_detect(struct drm_bridge *bridge)
> +{
> + struct ti_sn65dsi86 *pdata = bridge_to_ti_sn65dsi86(bridge);
> + int val;
> +
> + regmap_read(pdata->regmap, SN_HPD_DISABLE_REG, &val);
Don't you need a pm_runtime_get_sync() before this and a
put_autosuspend() after? The "detect" will be used in the yes-HPD but
no-IRQ case, right? In that case there's nobody holding the pm_runtime
reference.
Also, a nit that it'd be great if you error checked the regmap_read().
I know this driver isn't very good about it, but it's probably
something to get better. i2c transactions can fail. I guess another
alternative would be to init "val" to 0...
> + return val & HPD_DEBOUNCED_STATE ? connector_status_connected
> + : connector_status_disconnected;
> +}
> +
> +static void ti_sn_bridge_hpd_enable(struct drm_bridge *bridge)
> +{
> + struct ti_sn65dsi86 *pdata = bridge_to_ti_sn65dsi86(bridge);
> +
> + /* The device must remain active for HPD to function */
> + pm_runtime_get_sync(pdata->dev);
> + regmap_write(pdata->regmap, SN_IRQ_HPD_REG,
> + IRQ_HPD_EN | IRQ_HPD_INSERTION_EN |
> + IRQ_HPD_REMOVAL_EN | IRQ_HPD_REPLUG_EN);
> +}
> +
> +static void ti_sn_bridge_hpd_disable(struct drm_bridge *bridge)
> +{
> + struct ti_sn65dsi86 *pdata = bridge_to_ti_sn65dsi86(bridge);
> +
> + regmap_write(pdata->regmap, SN_IRQ_HPD_REG, 0);
> + pm_runtime_put_autosuspend(pdata->dev);
Before doing the pm_runtime_put_autosuspend() it feels like you should
ensure that the interrupt has finished. Otherwise we could be midway
through processing an interrupt and the pm_runtime reference could go
away, right? Maybe we just disable the irq which I think will wait for
anything outstanding to finish?
> @@ -1223,6 +1282,34 @@ static int ti_sn_bridge_parse_dsi_host(struct ti_sn65dsi86 *pdata)
> return 0;
> }
>
> +static irqreturn_t ti_sn65dsi86_irq_handler(int irq, void *arg)
> +{
> + struct ti_sn65dsi86 *pdata = arg;
> + int ret;
> + unsigned int hpd;
> +
> + ret = regmap_read(pdata->regmap, SN_IRQ_HPD_STATUS_REG, &hpd);
> + if (ret || !hpd)
> + return IRQ_NONE;
> +
> + if (hpd & IRQ_HPD_INSERTION_STATUS)
> + drm_bridge_hpd_notify(&pdata->bridge, connector_status_connected);
> +
> + if (hpd & IRQ_HPD_REMOVAL_STATUS)
> + drm_bridge_hpd_notify(&pdata->bridge, connector_status_disconnected);
> +
> + /* When replugged, ensure we trigger a detect to update the display */
> + if (hpd & IRQ_HPD_REPLUG_STATUS)
> + drm_bridge_hpd_notify(&pdata->bridge, connector_status_disconnected);
How does the ordering work here if _both_ insertion and removal are
asserted? Is that somehow not possible? Should this be "else if" type
statements then, or give a warn if more than one bit is set, or ... ?
> + /* reset the status registers */
> + regmap_write(pdata->regmap, SN_IRQ_HPD_STATUS_REG,
> + IRQ_HPD_STATUS | IRQ_HPD_INSERTION_STATUS |
> + IRQ_HPD_REMOVAL_STATUS | IRQ_HPD_REPLUG_STATUS);
IMO this regmap_write() belongs right after the read and should be
based on what you read--you shouldn't just clear all of them. AKA:
a) Read to see what interrupt are asserted.
b) Ack the interrupts that you saw asserted.
c) Process the interrupts that you saw asserted.
If you process before acking then you can miss interrupts (in other
words if you do "a" then "c" then "b" then you can miss interrupts
that come in after "b" but before "c".
> @@ -1247,9 +1342,29 @@ static int ti_sn_bridge_probe(struct auxiliary_device *adev,
> pdata->bridge.type = pdata->next_bridge->type == DRM_MODE_CONNECTOR_DisplayPort
> ? DRM_MODE_CONNECTOR_DisplayPort : DRM_MODE_CONNECTOR_eDP;
>
> - if (pdata->bridge.type == DRM_MODE_CONNECTOR_DisplayPort)
> + if (pdata->bridge.type == DRM_MODE_CONNECTOR_DisplayPort) {
> pdata->bridge.ops = DRM_BRIDGE_OP_EDID;
>
> + if (!pdata->no_hpd)
> + pdata->bridge.ops |= DRM_BRIDGE_OP_DETECT;
> + }
> +
> + if (!pdata->no_hpd && pdata->irq > 0) {
> + dev_err(pdata->dev, "registering IRQ %d\n", pdata->irq);
> +
> + ret = devm_request_threaded_irq(pdata->dev, pdata->irq, NULL,
> + ti_sn65dsi86_irq_handler,
> + IRQF_ONESHOT, "sn65dsi86-irq",
> + pdata);
> + if (ret)
> + return dev_err_probe(pdata->dev, ret,
> + "Failed to register DP interrupt\n");
> +
> + /* Enable IRQ based HPD */
> + regmap_write(pdata->regmap, SN_IRQ_EN_REG, IRQ_EN);
Why not put the above regmap_write() in the ti_sn_bridge_hpd_enable() call?
-Doug
Powered by blists - more mailing lists