Re: [PATCH 1/1] drm/bridge: Fix handling of bridges with pre_enable_prev_first flag

2023-07-17 Thread Frieder Schrempf
On 14.07.23 19:16, Dave Stevenson wrote: > Hi Frieder > > On Mon, 10 Jul 2023 at 08:46, Frieder Schrempf > wrote: >> >> On 07.07.23 21:00, Vladimir Lypak wrote: >>> [Sie erhalten nicht häufig E-Mails von vladimir.ly...@gmail.com. Weitere >>> Informationen, warum dies wichtig ist, finden Sie unte

Re: [PATCH 1/1] drm/bridge: Fix handling of bridges with pre_enable_prev_first flag

2023-07-14 Thread Dave Stevenson
Hi Frieder On Mon, 10 Jul 2023 at 08:46, Frieder Schrempf wrote: > > On 07.07.23 21:00, Vladimir Lypak wrote: > > [Sie erhalten nicht häufig E-Mails von vladimir.ly...@gmail.com. Weitere > > Informationen, warum dies wichtig ist, finden Sie unter > > https://aka.ms/LearnAboutSenderIdentificatio

Re: [PATCH 1/1] drm/bridge: Fix handling of bridges with pre_enable_prev_first flag

2023-07-10 Thread Frieder Schrempf
On 07.07.23 21:00, Vladimir Lypak wrote: > [Sie erhalten nicht häufig E-Mails von vladimir.ly...@gmail.com. Weitere > Informationen, warum dies wichtig ist, finden Sie unter > https://aka.ms/LearnAboutSenderIdentification ] > > In function drm_atomic_bridge_chain_post_disable handling of > pre_e

[PATCH 1/1] drm/bridge: Fix handling of bridges with pre_enable_prev_first flag

2023-07-07 Thread Vladimir Lypak
In function drm_atomic_bridge_chain_post_disable handling of pre_enable_prev_first flag is broken because "next" variable will always end up set to value of "bridge". This breaks loop which should disable bridges in reverse: next = list_next_entry(bridge, chain_node); if (next->pre_enable_prev_