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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 18 Mar 2019 22:18:11 +0530
From:   Jagan Teki <>
To:     Paul Kocialkowski <>
Cc:     Andrzej Hajda <>,
        Laurent Pinchart <>,
        Chen-Yu Tsai <>,
        Maxime Ripard <>,
        David Airlie <>,
        Daniel Vetter <>,
        Rob Herring <>,
        Mark Rutland <>,
        Michael Trimarchi <>,
        dri-devel <>,
        linux-kernel <>,
        devicetree <>,
        linux-arm-kernel <>,
        linux-sunxi <>,
Subject: Re: [linux-sunxi] [PATCH 1/6] drm/bridge: Export drm_bridge_detach

Hi Paul,

On Fri, Mar 15, 2019 at 6:58 PM Paul Kocialkowski
<> wrote:
> Hi Jakan,
> On Fri, 2019-03-15 at 18:38 +0530, Jagan Teki wrote:
> > Export drm_bridge_detach from drm bridge core so-that it
> > can use on respective interface or bridge driver while
> > detaching the bridge.
> I don't see why this change is required based on the commit log. The
> DRM bridge code clearly indicates that drm_bridge_attach should *not*
> be balanced with a drm_bridge_detach call in the driver, so this seems
> quite wrong.
> The DRM core itself should handle detaching the bridge, not the driver.
> Is there any reason why you need to do things differently for DSI?

Yes, you are correct the detach of bridge is being taking care via
drm_encoder_cleanup. This patch exported explicitly, since we need to
taken care bridge detach during unbind even exynos_drm_dsi in other
patch seems using detach by explicitly pointing. so I think the better
approach is to use drm_encoder_cleanup in unbind, what do you say?


Powered by blists - more mailing lists