Re: [PATCH v3] drm: of: Properly try all possible cases for bridge/panel detection

On Tue, Apr 5, 2022 at 10:01 AM Thierry Reding wrote: > > On Fri, Apr 01, 2022 at 09:44:46AM +0200, Paul Kocialkowski wrote: > > Hi Bjorn, > > > > On Thu 31 Mar 22, 20:16, Bjorn Andersson wrote: > > > On Tue 29 Mar 06:27 PDT 2022, Paul Kocialkowski wrote: > > > > > > > While bridge/panel detection

Re: [PATCH v3] drm: of: Properly try all possible cases for bridge/panel detection

Hi Paul, This patch breaks the ingenic-drm driver. It calls drm_of_find_panel_or_bridge(np, 0, i, ...) starting for i=0, until -ENODEV is returned, which does not happen anymore. The idea is to probe all the connected panels/bridges, should it be done differently now? Cheers, -Paul

Re: [PATCH v3] drm: of: Properly try all possible cases for bridge/panel detection

On Tue, Mar 29, 2022 at 3:27 PM Paul Kocialkowski wrote: > While bridge/panel detection was initially relying on the usual > port/ports-based of graph detection, it was recently changed to > perform the lookup on any child node that is not port/ports > instead when such a node is available, with

Re: [PATCH v3] drm: of: Properly try all possible cases for bridge/panel detection

On Fri, Apr 01, 2022 at 09:44:46AM +0200, Paul Kocialkowski wrote: > Hi Bjorn, > > On Thu 31 Mar 22, 20:16, Bjorn Andersson wrote: > > On Tue 29 Mar 06:27 PDT 2022, Paul Kocialkowski wrote: > > > > > While bridge/panel detection was initially relying on the usual > > > port/ports-based of graph d

Re: [PATCH v3] drm: of: Properly try all possible cases for bridge/panel detection

On Fri 01 Apr 00:44 PDT 2022, Paul Kocialkowski wrote: > Hi Bjorn, > > On Thu 31 Mar 22, 20:16, Bjorn Andersson wrote: > > On Tue 29 Mar 06:27 PDT 2022, Paul Kocialkowski wrote: > > > > > While bridge/panel detection was initially relying on the usual > > > port/ports-based of graph detection, i

Re: [PATCH v3] drm: of: Properly try all possible cases for bridge/panel detection

On Tue 29 Mar 06:27 PDT 2022, Paul Kocialkowski wrote: > While bridge/panel detection was initially relying on the usual > port/ports-based of graph detection, it was recently changed to > perform the lookup on any child node that is not port/ports > instead when such a node is available, with no

Re: (subset) [PATCH v3] drm: of: Properly try all possible cases for bridge/panel detection

On Tue, 29 Mar 2022 15:27:32 +0200, Paul Kocialkowski wrote: > While bridge/panel detection was initially relying on the usual > port/ports-based of graph detection, it was recently changed to > perform the lookup on any child node that is not port/ports > instead when such a node is available, wit