During system suspend after connector switch off its dpms field
is set to connector previous dpms state. To properly resume dpms field
should be set to its actual state (off) before resuming to previous dpms state.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
The patch removes master PM callbacks as their functionality
is already duplicated by suspend/resume drm callbacks.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_drm_drv.c | 29 -
1 file changed, 29 deletions(-)
diff --git
The main intent of this patchset is to allow use of suspend/resume drm driver
callbacks in KMS drivers, as these callbacks seems to me the best place
to implement suspend/resume functionality in drm driver.
Implementing this functionality in master component driver PM ops is problematic
as those
Implementing suspend/resume functionality in componentized drm drivers using
master component PM callbacks is problematic because those callbacks can be
called asynchronously regardless of existence/state of drm device.
The patch re-enables suspend/resume drm driver callbacks in drivers with
Currently suspend and resume callbacks are called only if driver have
modeset feature disabled.
This patch moves the check directly to i915 driver, it will allow to
remove the check from the core in the future.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/i915/i915_drv.c
On Fri, Oct 03, 2014 at 10:24:09AM +0200, Andrzej Hajda wrote:
The main intent of this patchset is to allow use of suspend/resume drm driver
callbacks in KMS drivers, as these callbacks seems to me the best place
to implement suspend/resume functionality in drm driver.
Implementing this
On 10/03/2014 10:31 AM, Daniel Vetter wrote:
On Fri, Oct 03, 2014 at 10:24:09AM +0200, Andrzej Hajda wrote:
The main intent of this patchset is to allow use of suspend/resume drm driver
callbacks in KMS drivers, as these callbacks seems to me the best place
to implement suspend/resume
On 3 October 2014 03:14, Kevin Hilman khil...@kernel.org wrote:
Ulf, Rafael,
Ulf Hansson ulf.hans...@linaro.org writes:
When there are more than one device in a PM domain these will obviously
be probed at different times. Depending on timing and the implemented
support for runtime PM in a
On 2 October 2014 17:54, Sylwester Nawrocki s.nawro...@samsung.com wrote:
On 02/10/14 15:30, Ulf Hansson wrote:
[...]
Correct me if I am wrong, but I think in principle these exynos
drivers don't use pm_runtime_set_active() during -probe() and are
instead relying on CONFIG_PM_RUNTIME to be
On Fri, Oct 3, 2014 at 11:42 AM, Andrzej Hajda a.ha...@samsung.com wrote:
On 10/03/2014 10:31 AM, Daniel Vetter wrote:
On Fri, Oct 03, 2014 at 10:24:09AM +0200, Andrzej Hajda wrote:
The main intent of this patchset is to allow use of suspend/resume drm
driver
callbacks in KMS drivers, as
Signed-off-by: Wolfram Sang w...@the-dreams.de
---
drivers/i2c/busses/i2c-exynos5.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-exynos5.c b/drivers/i2c/busses/i2c-exynos5.c
index 81e6263cd7da..271533d564ec 100644
---
Ulf Hansson ulf.hans...@linaro.org writes:
On 3 October 2014 03:14, Kevin Hilman khil...@kernel.org wrote:
Ulf, Rafael,
Ulf Hansson ulf.hans...@linaro.org writes:
When there are more than one device in a PM domain these will obviously
be probed at different times. Depending on timing and
On Fri, Oct 03, 2014 at 01:39:21PM +0200, Daniel Vetter wrote:
On Fri, Oct 3, 2014 at 11:42 AM, Andrzej Hajda a.ha...@samsung.com wrote:
But this is an issue closely connected with component framework.
Component framework separates master component probe and drm device
initialization. As a
* Factor out code for clearing raised IRQs from exynos_tmu_work() to
exynos_tmu_clear_irqs().
* Add a comment about documentation bugs to exynos_tmu_clear_irqs().
[ The documentation for Exynos3250, Exynos4412, Exynos5250 and
Exynos5260 incorrectly states that INTCLEAR register has
a
14 matches
Mail list logo
