ate_plane,
> .disable_plane = drm_atomic_helper_disable_plane,
> .destroy= drm_plane_cleanup,
> - .reset = drm_atomic_helper_plane_reset,
> - .atomic_duplicate_state = drm_atomic_helper_plane_duplicate_state,
> - .atomic_destroy_state = drm_atomic_helper_plane_destroy_sta
;
> ---
> drivers/gpu/drm/exynos/exynos_mixer.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of
Hi Marek,
2015-11-10 Marek Szyprowski :
> This patch adds common structure for keeping plane configuration and
> capabilities data. This patch is inspired by similar code developed by
> Tobias Jakobi.
>
> Signed-off-by: Marek Szyprowski
> ---
/drm/exynos/exynos_mixer.c | 3 +++
> 1 file changed, 3 insertions(+)
Good catch.
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to major
Hi Ville,
2015-11-13 Ville Syrjälä <ville.syrj...@linux.intel.com>:
> On Fri, Nov 13, 2015 at 11:45:58AM -0200, Gustavo Padovan wrote:
> > From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
> >
> > Fixes an regression added by 3ae2436 (drm/exynos/mixer: rep
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Fixes an regression added by 3ae2436 (drm/exynos/mixer: replace
direct cross-driver call with drm mode) and while this regression was
caused by a change in the exynos driver it makes sense to add the
check on atomic core to benefit
m.szyprow...@samsung.com>
> ---
> drivers/gpu/drm/exynos/exynos_drm_drv.h | 2 ++
> drivers/gpu/drm/exynos/exynos_drm_plane.c | 51
> +++
> 2 files changed, 53 insertions(+)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
> ---
> drivers/gpu/drm/exynos/exynos_mixer.c | 33 +++--
> 1 file changed, 3 insertions(+), 30 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line "unsubscribe
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Fixes an regression added by 3ae2436 (drm/exynos/mixer: replace
direct cross-driver call with drm mode). The whole atomic update
was failing if the hdmi display is not present/active. Add a test
to only run atomic_check() if th
t;
> Signed-off-by: Seung-Woo Kim <sw0312@samsung.com>
> Signed-off-by: Marek Szyprowski <m.szyprow...@samsung.com>
> ---
> drivers/gpu/drm/exynos/exynos_drm_gsc.c | 1 -
> 1 file changed, 1 deletion(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co
oo Kim <sw0312@samsung.com>
> Signed-off-by: Marek Szyprowski <m.szyprow...@samsung.com>
> ---
> drivers/gpu/drm/exynos/exynos_drm_gsc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Szyprowski <m.szyprow...@samsung.com>
> ---
> drivers/gpu/drm/exynos/exynos_drm_rotator.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line &
xynos/exynos7_drm_decon.c | 10 --
> 1 file changed, 10 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to major
s/exynos_drm_vidi.c | 5 -
> drivers/gpu/drm/exynos/exynos_mixer.c | 7 ---
> 9 files changed, 38 insertions(+), 53 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line
1 file changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
fimd_dp_clock_enable() was setting the always to enabled,
this patch fix this to actually use the value that is set to 'val'.
Reported-by: Emilio López <emilio.lo...@collabora.co.uk>
Signed-off-by: Gustavo Padovan &
;
> Signed-off-by: Inki Dae <inki@samsung.com>
> ---
> drivers/gpu/drm/exynos/exynos_dp_core.c | 23 ---
> 1 file changed, 23 deletions(-)
This sounds reasonable to me.
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
-
> drivers/gpu/drm/exynos/exynos_hdmi.c | 68
> ++--
> 1 file changed, 26 insertions(+), 42 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line "unsubscr
<a.ha...@samsung.com>
> ---
> drivers/gpu/drm/exynos/exynos_hdmi.c | 10 --
> 1 file changed, 10 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line "unsubscribe linux-
ings/video/exynos_hdmi.txt | 7 +++
> 1 file changed, 3 insertions(+), 4 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to major
>
> Signed-off-by: Andrzej Hajda <a.ha...@samsung.com>
> ---
> drivers/gpu/drm/exynos/exynos_hdmi.c | 56
> +++-
> drivers/gpu/drm/exynos/regs-hdmi.h | 4 +--
> 2 files changed, 38 insertions(+), 22 deletions(-)
Reviewed-by: Gustav
dxu3.
>
> Signed-off-by: Andrzej Hajda <a.ha...@samsung.com>
> ---
> drivers/gpu/drm/exynos/exynos_hdmi.c | 93
>
> 1 file changed, 8 insertions(+), 85 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora
s(+), 3 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Andrzej,
2015-09-25 Andrzej Hajda <a.ha...@samsung.com>:
> The patch removes unused hdmi_context field.
>
> Signed-off-by: Andrzej Hajda <a.ha...@samsung.com>
> ---
> drivers/gpu/drm/exynos/exynos_hdmi.c | 1 -
> 1 file changed, 1 deletion(-)
Reviewed-by:
+
> 1 file changed, 9 insertions(+), 16 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to major
s/gpu/drm/exynos/exynos_hdmi.c | 15 +--
> 1 file changed, 9 insertions(+), 6 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Gustavo
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a me
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
CRTC's mode_fixup() isn't used anymore in exynos, remove it.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 15 ---
drivers/gpu/drm/exynos/exynos_drm
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
The only thing mode_fixup was doing was set the adjusted_mode->vrefresh to
60, but it already has the value of 60 when the decon_mode_fixup() is
called. That means this call is actually pointless and can be removed.
Signed-off-by
From: Daniel Kurtz <djku...@chromium.org>
All the user of these functions are inside exynos-drm driver and
you don't need to export the symbols for that case.
Signed-off-by: Daniel Kurtz <djku...@chromium.org>
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
--
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Let pm_runtime handle the enabling/disabling of the device with proper
refcnt instead of rely on specific flags to track the enabled state.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
drivers/gp
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
The DP device will be properly enabled at the enable() call just
after the bind call finishes.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
drivers/gpu/drm/exynos/exynos_dp_core.c | 4
1 fil
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Let pm_runtime handle the enabling/disabling of the device with
proper refcnt instead of rely on specific flags to track the enabled
state.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
drivers/gp
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Hi,
This series adds proper runtime PM suport to CRTCs and Encoders, so
now instead of relying on 'suspended' or 'enabled' flags to track when
the CRTC or Encoder is enabled we let the pm_runtime subsystem do it for us
and remo
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Let pm_runtime handle the enabling/disabling of the device with proper
refcnt instead of rely on specific flags to track the enabled state.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
drivers/gp
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
This callback is no longer used by any of the exynos_crtc drivers, remove
it.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 10 --
drivers/gp
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Let pm_runtime handle the enabling/disabling of the device with proper
refcnt instead of rely on specific flags to track the enabled state.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
drivers/gp
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
It turns out that .commit() was never executed, because
at the time .mode_set_nofb() called it ctx->suspended was still false
and .commit() would return. It removes the callback from FIMD DECON 7 and
DECON 5433.
Signed-off-by
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Instead of having a .clock_enable callback enable the dp clock directly
from FIMD.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
drivers/gpu/drm/exynos/exynos_dp_core.c | 13 ---
drivers/gp
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Let pm_runtime handle the enabling/disabling of the device with
proper refcnt instead of rely on specific flags to track the enabled
state.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
drivers/gp
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Let pm_runtime handle the enabling/disabling of the device with
proper refcnt instead of rely on specific flags to track the enabled
state.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
drivers/gp
Hi Inki,
2015-09-04 Inki Dae <inki@samsung.com>:
> Hi Gustavo,
>
> I had already a review but I didn't give any comment to you. Sorry about
> that. This patch looks good to me but one thing isn't clear. Below is my
> comment.
>
>
> On 2015년 09월 04일 05:14, G
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Set one of the planes for each crtc driver as a cursor plane enabled
window managers to fully work on exynos.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
v2: use the top window for cursor on each crtc
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Define DEFAULT_WIN as zero to help set the primary plane on all CRTCs.
Some CRTCs were defining a variable to store the default window, but that
is not necessary as the default (primary) window is always the window zero.
Sign
From: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
Set one of the planes for each crtc driver as a cursor plane enabled
window managers to fully work on exynos.
Signed-off-by: Gustavo Padovan <gustavo.pado...@collabora.co.uk>
---
drivers/gpu/drm/exynos/exynos5433_drm_
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Exynos atomic commit procedures already does this job of waiting for
pending updates to finish, that means using pending_flip_queue is
pointless now because the disable CRTC procedure will never happen
during a page_flip.
Signed-off
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Now that atomic modesetting is implemented for exynos enable the
DRIVER_ATOMIC flag on the driver's features.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_drv.c | 3 ++-
1 file changed
Hi,
What about this patch? We need it to avoid the WARN_ON added by patch
2/2 that was already picked up by Daniel.
Gustavo
2015-08-13 Gustavo Padovan gust...@padovan.org:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
These legacy helpers should only be used by shadow
Hi Inki,
2015-08-24 Inki Dae inki@samsung.com:
On 2015년 08월 16일 01:26, Gustavo Padovan wrote:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
.prepare_plane() and .cleanup_plane() allows to perform extra operations
before and after the update of planes. For FIMD for example
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Add infrastructure to wait for all planes updates to finish by using
an atomic_t variable to track how many pending updates we are waiting
plus a wait_queue for the wait part.
It also changes vblank behaviour and keeps it enabled for all
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
The atomic modesetting interfaces supports async commits that should be
implemented by the drivers. If drm core requests an async commit
exynos_atomic_commit() will now schedule a work task to run the update later.
It also serializes commits
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Unify handling of finished plane update to prepare for a following patch
that will check for the START and START_S regs to really make sure that
the plane was updated.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Only set/clear the update bit in the CRTC's .atomic_begin()/flush()
so all planes are really committed at the same time.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
v2: rename prepare_plane/cleanup_plane
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
.atomic_begin() and .atomic_flush() allows to perform extra operations
before and after the update of planes. For FIMD for example this will
be used to enable disable the shadow protection bit.
Signed-off-by: Gustavo Padovan gustavo.pado
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Hi,
This patchset adds a couple of changes to improve atomic modesetting:
* add check for the START shadow register for FIMD to only finish the update
when the screen was actually updated.
* add asynchronous atomic commit, so now page
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
This macro is need to get the value of the START shadow register, that
will tell if an framebuffer is currently displayed on the screen or not.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
include/video/samsung_fimd.h
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Only set/clear the update bit in the CRTC's .atomic_begin()/flush()
so all planes are really committed at the same time.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 57
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
The current code was ignoring the end of update for all overlay planes,
caring only for the primary plane update in case of pageflip.
This change adds a change to start to check for pending updates for all
planes through exynos_plane
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct drm_crtc already stores the enabled state of the crtc
thus we don't need to replicate enabled in exynos_drm_crtc.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 16
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Set one of the planes for each crtc driver as a cursor plane enabled
window managers to fully work on exynos.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 9
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct exynos_drm_encoder was justing wrapping struct drm_encoder, it had
only a drm_encoder member and the internal exynos_drm_encoders ops that
was directly mapped to the drm_encoder helper funcs.
So now exynos DRM uses struct drm_encoder
Hi Inki,
2015-08-15 Inki Dae inki@samsung.com:
2015-08-13 0:54 GMT+09:00 Gustavo Padovan gust...@padovan.org:
2015-08-12 Gustavo Padovan gustavo.pado...@collabora.co.uk:
Hi Inki,
2015-08-11 Inki Dae inki@samsung.com:
On 2015년 08월 11일 09:38, Gustavo Padovan wrote:
Hi
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
The current code was ignoring the end of update for all overlay planes,
caring only for the primary plane update in case of pageflip.
This change adds a change to start to check for pending updates for all
planes through exynos_plane
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct drm_crtc already stores the enabled state of the crtc
thus we don't need to replicate enabled in exynos_drm_crtc.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 16
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Add infrastructure to wait for all planes updates to finish by using
an atomic_t variable to track how many pending updates we are waiting
plus a wait_queue for the wait part.
It also changes vblank behaviour and keeps it enabled for all
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Only set/clear the update bit in the CRTC's .atomic_begin()/flush()
so all planes are really committed at the same time.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 57
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Now that atomic modesetting is implemented for exynos enable the
DRIVER_ATOMIC flag on the driver's features.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_drv.c | 3 ++-
1 file changed
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
The atomic modesetting interfaces supports async commits that should be
implemented by the drivers. If drm core requests an async commit
exynos_atomic_commit() will now schedule a work task to run the update later.
It also serializes commits
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Exynos atomic commit procedures already does this job of waiting for
pending updates to finish, that means using pending_flip_queue is
pointless now because the disable CRTC procedure will never happen
during a page_flip.
Signed-off
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
fimd_update_plane() programs BUF_START[win] and during the update
BUF_START[win] is copied to BUF_START_S[win] (its shadow register)
and starts scanning out, then it raises a irq.
The fimd_irq_handler, in the case we have a pending_fb
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
This macro is need to get the value of the START shadow register, that
will tell if an framebuffer is currently displayed on the screen or not.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
include/video/samsung_fimd.h
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Hi,
This patchset adds a couple of changes to improve atomic modesetting:
* add check for the START shadow register for FIMD to only finish the update
when the screen was actually updated.
* add asynchronous atomic commit, so now page
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Unify handling of finished plane update to prepare for a following patch
that will check for the START and START_S regs to really make sure that
the plane was updated.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
.prepare_plane() and .cleanup_plane() allows to perform extra operations
before and after the update of planes. For FIMD for example this will
be used to enable disable the shadow protection bit.
Signed-off-by: Gustavo Padovan gustavo.pado
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Legacy s/r hooks are only used for shadow-attaching drivers, warn
when a KMS driver tries to use them.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/drm_drv.c | 2 ++
1 file changed, 2 insertions(+)
diff
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
These legacy helpers should only be used by shadow-attaching drivers.
KMS drivers has its own way to handle suspend/resume and don't need to
use these two helpers.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers
Hi Inki,
2015-08-11 Inki Dae inki@samsung.com:
On 2015년 08월 11일 09:38, Gustavo Padovan wrote:
Hi Inki,
2015-08-07 Inki Dae inki@samsung.com:
Hi Gustavo,
On 2015년 08월 06일 22:31, Gustavo Padovan wrote:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct
2015-08-12 Gustavo Padovan gustavo.pado...@collabora.co.uk:
Hi Inki,
2015-08-11 Inki Dae inki@samsung.com:
On 2015년 08월 11일 09:38, Gustavo Padovan wrote:
Hi Inki,
2015-08-07 Inki Dae inki@samsung.com:
Hi Gustavo,
On 2015년 08월 06일 22:31, Gustavo Padovan wrote
Hi Inki,
2015-08-07 Inki Dae inki@samsung.com:
Hi Gustavo,
On 2015년 08월 06일 22:31, Gustavo Padovan wrote:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct exynos_drm_encoder was justing wrapping struct drm_encoder, it had
only a drm_encoder member and the internal
Hi Inki,
2015-08-06 Inki Dae inki@samsung.com:
On 2015년 08월 06일 08:24, Gustavo Padovan wrote:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Hi,
This patchset is another important step in the exynos clean up, it removes
two exynos internal structs in favor of wider use
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct exynos_drm_encoder was justing wrapping struct drm_encoder, it had
only a drm_encoder member and the internal exynos_drm_encoders ops that
was directly mapped to the drm_encoder helper funcs.
So now exynos DRM uses struct drm_encoder
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
As we are removing the exynos encoder move the encoder setup operation
directly inside the exynos_drm_load()
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_drv.c | 12
2015-08-05 Inki Dae inki@samsung.com:
Hi Inki,
On 2015년 08월 04일 23:47, Gustavo Padovan wrote:
Hi Inki,
2015-08-04 Inki Dae inki@samsung.com:
On 2015년 08월 04일 04:09, Gustavo Padovan wrote:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct exynos_drm_encoder
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Hi,
This patchset is another important step in the exynos clean up, it removes
two exynos internal structs in favor of wider use of struct drm_encoder.
Structs exynos_drm_display and exynos_drm_encoder were doing exactly what
struct
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
This functions was just hiding the encoder and connector creation in
a way that was less clean than if we get rid of it. For example,
exynos_encoder ops had .create_connector() defined only because we were
handing off the encoder and connector
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
These two display_ops are not used anywhere, remove them.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_drv.h | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/gpu/drm
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
All CRTCs can only be LCD, HDMI or VIDI, so basically all CRTCs will be a
possible CRTCs. This patch removes an extra function with switch that was
only checking if the CRTC type was one of those three above.
Signed-off-by: Gustavo Padovan
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
exynos_dp_commit() was getting called twice by exynos encoder core, once
inside the .enable() call and another time by .commit() itself.
The remove of the second call caused the wake of a bug, the operations
orders inside exynos_dp_commit
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
.commit() is not used anymore, Exynos encoders now follow the
.enable()/.disable() semantics from drm atomic core, so remove this
callback.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
hdmi_commit() was getting called twice by exynos encoder core, once inside
the .enable() call and another time by .commit() itself.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 13
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
phy_power_on() and phy_power_off() already checks for NULL pointer.
This patch removes the wrappers exynos_dp_phy_init() and
exynos_dp_phy_exit() since the only think they were doing was a check for
NULL phy.
Signed-off-by: Gustavo Padovan
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
This struct was just representing encoder information, it was a member of
struct exynos_drm_encoder, so any code trying to access encoder data would
have to go through the encoder struct, get the display struct and then get
the data it want
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
The DRM Core doesn't have a dpms() operation anymore, everything
now is enable() or disable().
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
v2: set dp-dpms_mode after enable/disable
---
drivers/gpu/drm/exynos
Hi Inki,
2015-08-04 Inki Dae inki@samsung.com:
On 2015년 08월 04일 04:09, Gustavo Padovan wrote:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct exynos_drm_encoder was justing wrapping struct drm_encoder, it had
only a drm_encoder member and the internal
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
The DRM Core doesn't have a dpms() operation anymore, everything
now is enable() or disable().
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_dp_core.c | 37
drivers/gpu
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct exynos_drm_encoder was justing wrapping struct drm_encoder, it had
only a drm_encoder member and the internal exynos_drm_encoders ops that
was directly mapped to the drm_encoder helper funcs.
So now exynos DRM uses struct drm_encoder
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
phy_power_on() and phy_power_off() already checks for NULL pointer.
This patch removes the wrappers exynos_dp_phy_init() and
exynos_dp_phy_exit() since the only think they were doing was a check for
NULL phy.
Signed-off-by: Gustavo Padovan
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
hdmi_commit() was getting called twice by exynos encoder core, once inside
the .enable() call and another time by .commit() itself.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 13
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
This struct was just representing encoder information, it was a member of
struct exynos_drm_encoder, so any code trying to access encoder data would
have to go through the encoder struct, get the display struct and then get
the data it want
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
.commit() is not used anymore, Exynos encoders now follow the
.enable()/.disable() semantics from drm atomic core, so remove this
callback.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
All CRTCs can only be LCD, HDMI or VIDI, so basically all CRTCs will be a
possible CRTCs. This patch removes an extra function with switch that was
only checking if the CRTC type was one of those three above.
Signed-off-by: Gustavo Padovan
1 - 100 of 556 matches
Mail list logo