Re: [PATCH v2 0/5] Simplify panel bridge cleanup

2017-10-10 Thread Benjamin Gaignard
2017-10-10 5:36 GMT+02:00 Archit Taneja : > > > On 10/02/2017 03:02 PM, Benjamin Gaignard wrote: >> >> The goal of this series is to simplify driver code when they need to clean >> up >> a previously allocated panel bridge. >> Few drivers have "is_panel_bridge" flag to be able to distinguish a >> d

Re: [PATCH v2 0/5] Simplify panel bridge cleanup

2017-10-09 Thread Archit Taneja
On 10/02/2017 03:02 PM, Benjamin Gaignard wrote: The goal of this series is to simplify driver code when they need to clean up a previously allocated panel bridge. Few drivers have "is_panel_bridge" flag to be able to distinguish a drm_panel_bridge from "simple" drm_bridge. To remove this flag

Re: [PATCH v2 0/5] Simplify panel bridge cleanup

2017-10-03 Thread Daniel Vetter
On Mon, Oct 02, 2017 at 11:32:30AM +0200, Benjamin Gaignard wrote: > The goal of this series is to simplify driver code when they need to clean up > a previously allocated panel bridge. > Few drivers have "is_panel_bridge" flag to be able to distinguish a > drm_panel_bridge from "simple" drm_bridge

[PATCH v2 0/5] Simplify panel bridge cleanup

2017-10-02 Thread Benjamin Gaignard
The goal of this series is to simplify driver code when they need to clean up a previously allocated panel bridge. Few drivers have "is_panel_bridge" flag to be able to distinguish a drm_panel_bridge from "simple" drm_bridge. To remove this flag I propose to - let drm_panel_bridge_remove() check if