Re: [PATCH v2] gpu/drm/bridge/cadence: avoid flush_scheduled_work() usage

2022-06-29 Thread Tetsuo Handa
Ping? On 2022/06/13 22:57, Tetsuo Handa wrote: > Thus, how do we want to handle this race window? > > flush_delayed_work(>hdcp.check_work) followed by > flush_work(>hdcp.prop_work) (i.e. flush as much as possible) ? > > cancel_delayed_work_sync(>hdcp.check_work) followed by >

Re: [PATCH v2] gpu/drm/bridge/cadence: avoid flush_scheduled_work() usage

2022-06-13 Thread Tetsuo Handa
On 2022/06/10 23:35, Tetsuo Handa wrote: > Use local wq in order to avoid flush_scheduled_work() usage. > > Signed-off-by: Tetsuo Handa > --- > Changes in v2: > Replace flush_scheduled_work() with flush_workqueue(). > > Please see commit c4f135d643823a86 ("workqueue: Wrap flush_workqueue() >

[PATCH v2] gpu/drm/bridge/cadence: avoid flush_scheduled_work() usage

2022-06-10 Thread Tetsuo Handa
Use local wq in order to avoid flush_scheduled_work() usage. Signed-off-by: Tetsuo Handa --- Changes in v2: Replace flush_scheduled_work() with flush_workqueue(). Please see commit c4f135d643823a86 ("workqueue: Wrap flush_workqueue() using a macro") for background. This is a blind