Hi,
On Mon, Sep 12, 2022 at 11:48 AM Brian Norris wrote:
>
> On Thu, Aug 25, 2022 at 11:06 AM Brian Norris
> wrote:
> > On Thu, Aug 25, 2022 at 10:37 AM Doug Anderson
> > wrote:
> > > Given that this is _not_ an area that I'm an expert in nor is it an
> > > area where the consequences are
On Thu, Aug 25, 2022 at 11:06 AM Brian Norris wrote:
> On Thu, Aug 25, 2022 at 10:37 AM Doug Anderson wrote:
> > Given that this is _not_ an area that I'm an expert in nor is it an
> > area where the consequences are super easy to analyze, I'm a little
> > hesitant to apply this to drm-misc-next
Hi,
On Thu, Aug 25, 2022 at 10:37 AM Doug Anderson wrote:
> Reviewed-by: Douglas Anderson
Thanks :)
> Given that this is _not_ an area that I'm an expert in nor is it an
> area where the consequences are super easy to analyze, I'm a little
> hesitant to apply this to drm-misc-next myself.
Hi,
On Mon, Aug 22, 2022 at 6:08 PM Brian Norris wrote:
>
> This reverts commit 211f276ed3d96e964d2d1106a198c7f4a4b3f4c0.
>
> For quite some time, core DRM helpers already ensure that any relevant
> connectors/CRTCs/etc. are disabled, as well as their associated
> components (e.g., bridges) when
This reverts commit 211f276ed3d96e964d2d1106a198c7f4a4b3f4c0.
For quite some time, core DRM helpers already ensure that any relevant
connectors/CRTCs/etc. are disabled, as well as their associated
components (e.g., bridges) when suspending the system. Thus,
analogix_dp_bridge_{enable,disable}()
