[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200821113809.GA283294@ravnborg.org>
Date: Fri, 21 Aug 2020 13:38:09 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Enric Balletbo i Serra <enric.balletbo@...labora.com>
Cc: Jernej Skrabec <jernej.skrabec@...l.net>, drinkcat@...omium.org,
Neil Armstrong <narmstrong@...libre.com>,
David Airlie <airlied@...ux.ie>,
Jonas Karlman <jonas@...boo.se>, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org,
Andrzej Hajda <a.hajda@...sung.com>,
Boris Brezillon <boris.brezillon@...labora.com>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
hsinyi@...omium.org, matthias.bgg@...il.com,
Collabora Kernel ML <kernel@...labora.com>
Subject: Re: [PATCH 3/3] drm/bridge: ps8640: Rework power state handling
Hi Enric.
>
> Let me reformulate the question for if it was not clear.
>
> What I did is be able to read the EDID every time userspace asks for it (so
> kernel enables all the required) and Sam is proposing to just fail if all is not
> setup. I can obviously do this but my question is, at which point I should leave
> all the logic enabled to be able to read the EDID (after probe?, after
> pre_enable, after enable?) It is not clear for me from the API.
I am not clear if my suggestion is a good suggestion.
I recall I saw something similar in another bridge driver.
If no-one else chimes in then go ahead with your original approach
where there is less restriction when it is possible to read edid.
Sam
Powered by blists - more mailing lists