[PATCH 16/16] drm: exynos: mixer: fix using usleep() in atomic context

2015-09-25 Thread Andrzej Hajda
From: Tomasz Stanislawski This patch fixes calling usleep_range() after taking reg_slock using spin_lock_irqsave(). The mdelay() is used instead. Waiting in atomic context is not the best idea in general. Hopefully, waiting occurs only when Video Processor fails to

drm: exynos: mixer: fix using usleep() in atomic context

2015-01-22 Thread Seung-Woo Kim
Hello, On 2015년 01월 22일 07:46, Tobias Jakobi wrote: > Hello! > > > Inki Dae wrote: >> The use of spin lock, reg_slock, has been used for a long time and we >> hadn't some cleanups to spin lock codes so far. The spin lock is also >> used in here and there of mixer driver. And at least, it

drm: exynos: mixer: fix using usleep() in atomic context

2015-01-21 Thread Tobias Jakobi
Hello! Inki Dae wrote: > The use of spin lock, reg_slock, has been used for a long time and we > hadn't some cleanups to spin lock codes so far. The spin lock is also > used in here and there of mixer driver. And at least, it seems that > the use of spin lock isn't required in mixer_win_reset. I

drm: exynos: mixer: fix using usleep() in atomic context

2014-12-22 Thread Inki Dae
Sorry for late. 2014-12-17 16:54 GMT+09:00 Thierry Reding : > On Mon, Dec 01, 2014 at 05:16:17PM +0100, Tobias Jakobi wrote: >> On 2014-12-01 16:54, Thierry Reding wrote: >> >On Sun, Nov 30, 2014 at 01:35:25AM +0100, tjakobi at math.uni-bielefeld.de >> >wrote: >> >>From: Tomasz Stanislawski >>

drm: exynos: mixer: fix using usleep() in atomic context

2014-12-17 Thread Thierry Reding
On Mon, Dec 01, 2014 at 05:16:17PM +0100, Tobias Jakobi wrote: > On 2014-12-01 16:54, Thierry Reding wrote: > >On Sun, Nov 30, 2014 at 01:35:25AM +0100, tjakobi at math.uni-bielefeld.de > >wrote: > >>From: Tomasz Stanislawski > >> > >>This patch fixes calling usleep_range() after taking reg_slock

drm: exynos: mixer: fix using usleep() in atomic context

2014-12-01 Thread Tobias Jakobi
On 2014-12-01 16:54, Thierry Reding wrote: > On Sun, Nov 30, 2014 at 01:35:25AM +0100, tjakobi at math.uni-bielefeld.de > wrote: >> From: Tomasz Stanislawski >> >> This patch fixes calling usleep_range() after taking reg_slock >> using spin_lock_irqsave(). The mdelay() is used instead. >>

drm: exynos: mixer: fix using usleep() in atomic context

2014-12-01 Thread Thierry Reding
On Sun, Nov 30, 2014 at 01:35:25AM +0100, tjakobi at math.uni-bielefeld.de wrote: > From: Tomasz Stanislawski > > This patch fixes calling usleep_range() after taking reg_slock > using spin_lock_irqsave(). The mdelay() is used instead. > Waiting in atomic context is not the best idea in

drm: exynos: mixer: fix using usleep() in atomic context

2014-11-30 Thread tjak...@math.uni-bielefeld.de
From: Tomasz Stanislawski This patch fixes calling usleep_range() after taking reg_slock using spin_lock_irqsave(). The mdelay() is used instead. Waiting in atomic context is not the best idea in general. Hopefully, waiting occurs only when Video Processor fails to

[PATCHv3 3/5] drm: exynos: mixer: fix using usleep() in atomic context

2014-04-16 Thread Tomasz Stanislawski
This patch fixes calling usleep_range() after taking reg_slock using spin_lock_irqsave(). The mdelay() is used instead. Waiting in atomic context is not the best idea in general. Hopefully, waiting occurs only when Video Processor fails to reset correctly. Signed-off-by: Tomasz Stanislawski ---

[PATCHv2 2/4] drm: exynos: mixer: fix using usleep() in atomic context

2014-04-15 Thread Tomasz Stanislawski
This patch fixes calling usleep_range() after taking reg_slock using spin_lock_irqsave(). The mdelay() is used instead. Waiting in atomic context is not the best idea in general. Hopefully, waiting occurs only when Video Processor fails to reset correctly. Signed-off-by: Tomasz Stanislawski ---

[PATCH 2/4] drm: exynos: mixer: fix using usleep() in atomic context

2014-04-14 Thread Tomasz Stanislawski
This patch fixes calling usleep_range() after taking reg_slock using spin_lock_irqsave(). The mdelay() is used instead. Waiting in atomic context is not the best idea in general. Hopefully, waiting occurs only when Video Processor fails to reset correctly. Signed-off-by: Tomasz Stanislawski ---