Re: [GIT PULL] exynos-drm-next
On Wed, Jul 03, 2024 at 04:59:12PM +0900, Inki Dae wrote: > Hi Dave and Daniel, > >Just three cleanup patches to Exynos Virtual Display driver >for improved management. > > Please kindly let me know if there is any problem. > > Thanks, > Inki Dae > > > The following changes since commit fb625bf6187d97c3cd28d680b14bf80f84207e5a: > > Merge tag 'drm-habanalabs-next-2024-06-23' of > https://github.com/HabanaAI/drivers.accel.habanalabs.kernel into drm-next > (2024-06-28 09:41:04 +1000) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos > tags/exynos-drm-next-for-v6.11 > > for you to fetch changes up to 2210093478443cd57cff5950379fec31ee8a5f79: > > drm/exynos/vidi: convert to struct drm_edid (2024-07-03 13:00:16 +0900) Pulled, thanks. -Sima > > > Some cleanups to Exynos Virtual Display driver > - Use drm_edid_duplicate() instead of kmemdup(). > - Replace existing EDID handling with struct drm_edid functions > for improved management. > - Keep an allocated raw_edid or NULL and handle fake_edid_info in get_modes(). > > > Inki Dae (1): > Merge tag 'exynos-drm-fixes-for-v6.10-rc4' of > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into > exynos-drm-next > > Jani Nikula (4): > drm/exynos/vidi: fix memory leak in .get_modes() > drm/exynos/vidi: use drm_edid_duplicate() > drm/exynos/vidi: simplify fake edid handling > drm/exynos/vidi: convert to struct drm_edid > > Krzysztof Kozlowski (1): > drm/exynos: dp: drop driver owner initialization > > Marek Szyprowski (1): > drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID > found > > drivers/gpu/drm/exynos/exynos_dp.c | 1 - > drivers/gpu/drm/exynos/exynos_drm_vidi.c | 83 > ++-- > drivers/gpu/drm/exynos/exynos_hdmi.c | 7 ++- > 3 files changed, 42 insertions(+), 49 deletions(-) -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
[GIT PULL] exynos-drm-next
Hi Dave and Daniel, Just three cleanup patches to Exynos Virtual Display driver for improved management. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit fb625bf6187d97c3cd28d680b14bf80f84207e5a: Merge tag 'drm-habanalabs-next-2024-06-23' of https://github.com/HabanaAI/drivers.accel.habanalabs.kernel into drm-next (2024-06-28 09:41:04 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v6.11 for you to fetch changes up to 2210093478443cd57cff5950379fec31ee8a5f79: drm/exynos/vidi: convert to struct drm_edid (2024-07-03 13:00:16 +0900) Some cleanups to Exynos Virtual Display driver - Use drm_edid_duplicate() instead of kmemdup(). - Replace existing EDID handling with struct drm_edid functions for improved management. - Keep an allocated raw_edid or NULL and handle fake_edid_info in get_modes(). Inki Dae (1): Merge tag 'exynos-drm-fixes-for-v6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into exynos-drm-next Jani Nikula (4): drm/exynos/vidi: fix memory leak in .get_modes() drm/exynos/vidi: use drm_edid_duplicate() drm/exynos/vidi: simplify fake edid handling drm/exynos/vidi: convert to struct drm_edid Krzysztof Kozlowski (1): drm/exynos: dp: drop driver owner initialization Marek Szyprowski (1): drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found drivers/gpu/drm/exynos/exynos_dp.c | 1 - drivers/gpu/drm/exynos/exynos_drm_vidi.c | 83 ++-- drivers/gpu/drm/exynos/exynos_hdmi.c | 7 ++- 3 files changed, 42 insertions(+), 49 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave and Daniel, Just two cleanups - one is remove the .owner field from the platform_driver declarations in Exynos DRM modules and other is to drop the device_node cleanup code in exynos_hdmi.c using the scope-based resource management. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 83221064c28a0f9fdc4f63ab4fce2e51bfe23315: Merge tag 'drm-xe-next-2024-04-23' of https://gitlab.freedesktop.org/drm/xe/kernel into drm-next (2024-04-24 10:51:29 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-6.10 for you to fetch changes up to d65bfb9546eb627e3c578336355c5b81797f2255: gpu: drm: exynos: hdmi: eliminate uses of of_node_put() (2024-04-25 09:37:12 +0900) Two cleanups - Drop .owner from platform_driver declaration of each exynos drm module. - Drop the cleanup code to device_node object in exynos_hdmi.c using the scope-based resource management feature[1]. [1] https://lwn.net/Articles/934679/?ref=upstract.com Krzysztof Kozlowski (11): drm/exynos: fimc: drop driver owner initialization drm/exynos: fimd: drop driver owner initialization drm/exynos: dsi: drop driver owner initialization drm/exynos: g2d: drop driver owner initialization drm/exynos: gsc: drop driver owner initialization drm/exynos: mic: drop driver owner initialization drm/exynos: rotator: drop driver owner initialization drm/exynos: scaler: drop driver owner initialization drm/exynos: vidi: drop driver owner initialization drm/exynos: hdmi: drop driver owner initialization drm/exynos: mixer: drop driver owner initialization Shivani Gupta (1): gpu: drm: exynos: hdmi: eliminate uses of of_node_put() drivers/gpu/drm/exynos/exynos_drm_dsi.c | 1 - drivers/gpu/drm/exynos/exynos_drm_fimc.c| 1 - drivers/gpu/drm/exynos/exynos_drm_fimd.c| 1 - drivers/gpu/drm/exynos/exynos_drm_g2d.c | 1 - drivers/gpu/drm/exynos/exynos_drm_gsc.c | 1 - drivers/gpu/drm/exynos/exynos_drm_mic.c | 1 - drivers/gpu/drm/exynos/exynos_drm_rotator.c | 1 - drivers/gpu/drm/exynos/exynos_drm_scaler.c | 1 - drivers/gpu/drm/exynos/exynos_drm_vidi.c| 1 - drivers/gpu/drm/exynos/exynos_hdmi.c| 16 +--- drivers/gpu/drm/exynos/exynos_mixer.c | 1 - 11 files changed, 5 insertions(+), 21 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave and Daniel, Just one fixup to shutdown relevant issue and two cleanups. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit a2f8994c1001cfa48483a3afa3550016a3ab0a3e: Merge tag 'exynos-drm-next-for-v6.7-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into exynos-drm-next (2023-12-12 13:06:29 +0900) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v6.8 for you to fetch changes up to ead5a41c8f8a13ad7b1c9fd2d7edb1ea909b777f: drm/exynos: dpi: Change connector type to DPI (2023-12-12 13:06:38 +0900) One bug fix - Add a missing call to drm_atomic_helper_shutdown() in Exynos DRM driver. This function is necessary during system shutdown and when the driver is unbound. Without this function, components like panels may not shut down properly, potentially leading to power issue as mentioned in the kernel documentation, specially in the "driver instance overview" secstion of 'drm_drv.c'. Two cleanups - Convert '.remove()' callback function in the Exynos DRM platform driver to a version that returns void instead of an integer. - Change connector type of exynos_drm_dpi.c module to DPI. Douglas Anderson (1): drm/exynos: Call drm_atomic_helper_shutdown() at shutdown/unbind time Paul Cercueil (1): drm/exynos: dpi: Change connector type to DPI Uwe Kleine-König (1): drm/exynos: Convert to platform remove callback returning void drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 6 ++ drivers/gpu/drm/exynos/exynos7_drm_decon.c| 6 ++ drivers/gpu/drm/exynos/exynos_dp.c| 6 ++ drivers/gpu/drm/exynos/exynos_drm_dpi.c | 2 +- drivers/gpu/drm/exynos/exynos_drm_drv.c | 16 +--- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 6 ++ drivers/gpu/drm/exynos/exynos_drm_fimd.c | 6 ++ drivers/gpu/drm/exynos/exynos_drm_g2d.c | 6 ++ drivers/gpu/drm/exynos/exynos_drm_gsc.c | 6 ++ drivers/gpu/drm/exynos/exynos_drm_mic.c | 6 ++ drivers/gpu/drm/exynos/exynos_drm_rotator.c | 6 ++ drivers/gpu/drm/exynos/exynos_drm_scaler.c| 6 ++ drivers/gpu/drm/exynos/exynos_drm_vidi.c | 6 ++ drivers/gpu/drm/exynos/exynos_hdmi.c | 6 ++ drivers/gpu/drm/exynos/exynos_mixer.c | 6 ++ 15 files changed, 40 insertions(+), 56 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave and Daniel, Just one fixup and cleanup. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit d9aa1da9a8cfb0387eb5703c15bd1f54421460ac: Merge tag 'drm-intel-gt-next-2023-08-04' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2023-08-07 13:49:25 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v6.6 for you to fetch changes up to 6b83c85b64078ff49b4d3d0b2cd2c2bf6f1b6a85: drm/exynos: remove redundant of_match_ptr (2023-08-08 09:35:19 +0900) Fixup - fix a possible null pointer dereference issue in exynos_drm_crtc_atomic_disable(), which was reported by the automatic static analysis tool. And below is a relevant link, https://sites.google.com/view/basscheck/home Cleanup - drop the use of of_match_ptr which is redundant. Tuo Li (1): drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable() Zhu Wang (1): drm/exynos: remove redundant of_match_ptr drivers/gpu/drm/exynos/exynos_drm_crtc.c | 5 ++--- drivers/gpu/drm/exynos/exynos_drm_gsc.c | 2 +- 2 files changed, 3 insertions(+), 4 deletions(-)
Re: [GIT PULL] exynos-drm-next
Hi Daniel, 2023년 3월 29일 (수) 오후 2:39, 대인기 님이 작성: > > > > > -Original Message- > > From: Daniel Vetter > > Sent: Wednesday, March 29, 2023 2:31 AM > > To: Inki Dae > > Cc: airl...@linux.ie; dan...@ffwll.ch; dri-devel@lists.freedesktop.org; > > linux-samsung-...@vger.kernel.org > > Subject: Re: [GIT PULL] exynos-drm-next > > > > On Tue, Mar 28, 2023 at 01:05:24PM +0900, Inki Dae wrote: > > > Hi Dave and Daniel, > > > > > >Just one patch series that moves the existing Exynos DSI driver > > >to drm/bridge directory to support both SoCs family - Exynos > > >and I.MX - because same Exynos MIPI DSI ip can be used by the two > > >different SoC family. > > > > > >Of course, there are some concerns about this patch series because > > Exynos > > >and I.MX SoCs have different HW characteristic but use the same HW > > driver. > > >However, I believe that there should be no problem as Exynos and I.MX > > >developers have conducted tests and reviews enough for about a year > > >since last April. > > > > > >This would be the first case that we allow different vendor SoCs to use > > >same device driver at least in DRM world so we anticipate experiencing > > >and resolving new issues through ongoing maintenance, and ultimately, > > >the experiences gained here will undoubtedly be able to contribute > > >the development of the community as well. > > > > > >Please kindly let me know if there is any problem. > > > > > > Thanks, > > > Inki Dae Could you kindly help me understand if there are any missed steps on my part? I applied for commit access to the drm and drm-misc repositories through the link provided below two weeks ago, but haven't received any updates on my request. https://gitlab.freedesktop.org/freedesktop/freedesktop/-/issues/569 Thanks, Inki Dae > > > > > > The following changes since commit > > 46f28427f6f824b6cff06fa025a55350b7de454a: > > > > > > Merge tag 'drm-rcar-next-20230325' of > > git://git.kernel.org/pub/scm/linux/kernel/git/pinchartl/linux into drm-next > > (2023-03-27 18:20:20 +0200) > > > > > > are available in the Git repository at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos > > tags/exynos-drm-next-for-v6.4 > > > > Merged, but usually all drm bridge stuff goes through drm-misc, least so > > that there's some amount of collaboration and not so much inter-tree > > syncing. > > > > Please apply for drm-misc commit rights (at least a quick check shows no > > one from samsung) and land future bridge patches through that tree. > > > > Cheers, Daniel > > I will apply for drm-misc commit rights. :) > > Thanks, > Inki Dae > > > > > > > > > for you to fetch changes up to b2cfec52feb3bb737c4b65018ef4bfe9789e4be8: > > > > > > drm: bridge: samsung-dsim: Add i.MX8M Plus support (2023-03-28 09:05:41 > > +0900) > > > > > > > > > A patch series for moving MIPI-DSI driver for Exynos DRM to drm/bridge > > > directory so that I.MX SoC family can also share the same device driver. > > > Samsung MIPI DSIM device is a common IP that can be used by Exynos and > > I.MX8M > > > Mini/Nano/Plus SoC. Regarding this, this patch series has added several > > > things below to existing MIPI DSI driver, > > > - Add exynos_dsi_type enum type to provide controller data from > > different > > > platforms. > > > - Add two pipeline detection ways support - existing Exynos DSI child > > node > > > and I.MX family of-graph port or ports. > > > - Consider component and bridged based DRM drivers. > > > - Add device tree binding support of I.MX family. > > > > > > > > > Jagan Teki (14): > > > drm: exynos: dsi: Drop explicit call to bridge detach > > > drm: exynos: dsi: Lookup OF-graph or Child node devices > > > drm: exynos: dsi: Mark PHY as optional > > > drm: exynos: dsi: Add platform PLL_P (PMS_P) offset > > > drm: exynos: dsi: Introduce hw_type platform data > > > drm: exynos: dsi: Add atomic check > > > drm: exynos: dsi: Add input_bus_flags > > > drm: exynos: dsi: Add atomic_ge
RE: [GIT PULL] exynos-drm-next
> -Original Message- > From: Daniel Vetter > Sent: Wednesday, March 29, 2023 2:31 AM > To: Inki Dae > Cc: airl...@linux.ie; dan...@ffwll.ch; dri-devel@lists.freedesktop.org; > linux-samsung-...@vger.kernel.org > Subject: Re: [GIT PULL] exynos-drm-next > > On Tue, Mar 28, 2023 at 01:05:24PM +0900, Inki Dae wrote: > > Hi Dave and Daniel, > > > >Just one patch series that moves the existing Exynos DSI driver > >to drm/bridge directory to support both SoCs family - Exynos > >and I.MX - because same Exynos MIPI DSI ip can be used by the two > >different SoC family. > > > >Of course, there are some concerns about this patch series because > Exynos > >and I.MX SoCs have different HW characteristic but use the same HW > driver. > >However, I believe that there should be no problem as Exynos and I.MX > >developers have conducted tests and reviews enough for about a year > >since last April. > > > >This would be the first case that we allow different vendor SoCs to use > >same device driver at least in DRM world so we anticipate experiencing > >and resolving new issues through ongoing maintenance, and ultimately, > >the experiences gained here will undoubtedly be able to contribute > >the development of the community as well. > > > >Please kindly let me know if there is any problem. > > > > Thanks, > > Inki Dae > > > > The following changes since commit > 46f28427f6f824b6cff06fa025a55350b7de454a: > > > > Merge tag 'drm-rcar-next-20230325' of > git://git.kernel.org/pub/scm/linux/kernel/git/pinchartl/linux into drm-next > (2023-03-27 18:20:20 +0200) > > > > are available in the Git repository at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos > tags/exynos-drm-next-for-v6.4 > > Merged, but usually all drm bridge stuff goes through drm-misc, least so > that there's some amount of collaboration and not so much inter-tree > syncing. > > Please apply for drm-misc commit rights (at least a quick check shows no > one from samsung) and land future bridge patches through that tree. > > Cheers, Daniel I will apply for drm-misc commit rights. :) Thanks, Inki Dae > > > > > for you to fetch changes up to b2cfec52feb3bb737c4b65018ef4bfe9789e4be8: > > > > drm: bridge: samsung-dsim: Add i.MX8M Plus support (2023-03-28 09:05:41 > +0900) > > > > > > A patch series for moving MIPI-DSI driver for Exynos DRM to drm/bridge > > directory so that I.MX SoC family can also share the same device driver. > > Samsung MIPI DSIM device is a common IP that can be used by Exynos and > I.MX8M > > Mini/Nano/Plus SoC. Regarding this, this patch series has added several > > things below to existing MIPI DSI driver, > > - Add exynos_dsi_type enum type to provide controller data from > different > > platforms. > > - Add two pipeline detection ways support - existing Exynos DSI child > node > > and I.MX family of-graph port or ports. > > - Consider component and bridged based DRM drivers. > > - Add device tree binding support of I.MX family. > > > > > > Jagan Teki (14): > > drm: exynos: dsi: Drop explicit call to bridge detach > > drm: exynos: dsi: Lookup OF-graph or Child node devices > > drm: exynos: dsi: Mark PHY as optional > > drm: exynos: dsi: Add platform PLL_P (PMS_P) offset > > drm: exynos: dsi: Introduce hw_type platform data > > drm: exynos: dsi: Add atomic check > > drm: exynos: dsi: Add input_bus_flags > > drm: exynos: dsi: Add atomic_get_input_bus_fmts > > drm: exynos: dsi: Consolidate component and bridge > > drm: exynos: dsi: Add host helper for te_irq_handler > > drm: bridge: Generalize Exynos-DSI driver into a Samsung DSIM bridge > > dt-bindings: display: exynos: dsim: Add NXP i.MX8M Mini/Nano support > > drm: bridge: samsung-dsim: Add i.MX8M Mini/Nano support > > dt-bindings: display: exynos: dsim: Add NXP i.MX8M Plus support > > > > Marek Szyprowski (1): > > drm: exynos: dsi: Handle proper host initialization > > > > Marek Vasut (1): > > drm: bridge: samsung-dsim: Add i.MX8M Plus support > > > > .../bindings/display/exynos/exynos_dsim.txt|2 + > > MAINTAINERS|9 + > > drivers/gpu/drm/bridg
Re: [GIT PULL] exynos-drm-next
On Tue, Mar 28, 2023 at 01:05:24PM +0900, Inki Dae wrote: > Hi Dave and Daniel, > >Just one patch series that moves the existing Exynos DSI driver >to drm/bridge directory to support both SoCs family - Exynos >and I.MX - because same Exynos MIPI DSI ip can be used by the two >different SoC family. > >Of course, there are some concerns about this patch series because Exynos >and I.MX SoCs have different HW characteristic but use the same HW driver. >However, I believe that there should be no problem as Exynos and I.MX >developers have conducted tests and reviews enough for about a year >since last April. > >This would be the first case that we allow different vendor SoCs to use >same device driver at least in DRM world so we anticipate experiencing >and resolving new issues through ongoing maintenance, and ultimately, >the experiences gained here will undoubtedly be able to contribute >the development of the community as well. > >Please kindly let me know if there is any problem. > > Thanks, > Inki Dae > > The following changes since commit 46f28427f6f824b6cff06fa025a55350b7de454a: > > Merge tag 'drm-rcar-next-20230325' of > git://git.kernel.org/pub/scm/linux/kernel/git/pinchartl/linux into drm-next > (2023-03-27 18:20:20 +0200) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos > tags/exynos-drm-next-for-v6.4 Merged, but usually all drm bridge stuff goes through drm-misc, least so that there's some amount of collaboration and not so much inter-tree syncing. Please apply for drm-misc commit rights (at least a quick check shows no one from samsung) and land future bridge patches through that tree. Cheers, Daniel > > for you to fetch changes up to b2cfec52feb3bb737c4b65018ef4bfe9789e4be8: > > drm: bridge: samsung-dsim: Add i.MX8M Plus support (2023-03-28 09:05:41 > +0900) > > > A patch series for moving MIPI-DSI driver for Exynos DRM to drm/bridge > directory so that I.MX SoC family can also share the same device driver. > Samsung MIPI DSIM device is a common IP that can be used by Exynos and I.MX8M > Mini/Nano/Plus SoC. Regarding this, this patch series has added several > things below to existing MIPI DSI driver, > - Add exynos_dsi_type enum type to provide controller data from > different > platforms. > - Add two pipeline detection ways support - existing Exynos DSI child > node > and I.MX family of-graph port or ports. > - Consider component and bridged based DRM drivers. > - Add device tree binding support of I.MX family. > > > Jagan Teki (14): > drm: exynos: dsi: Drop explicit call to bridge detach > drm: exynos: dsi: Lookup OF-graph or Child node devices > drm: exynos: dsi: Mark PHY as optional > drm: exynos: dsi: Add platform PLL_P (PMS_P) offset > drm: exynos: dsi: Introduce hw_type platform data > drm: exynos: dsi: Add atomic check > drm: exynos: dsi: Add input_bus_flags > drm: exynos: dsi: Add atomic_get_input_bus_fmts > drm: exynos: dsi: Consolidate component and bridge > drm: exynos: dsi: Add host helper for te_irq_handler > drm: bridge: Generalize Exynos-DSI driver into a Samsung DSIM bridge > dt-bindings: display: exynos: dsim: Add NXP i.MX8M Mini/Nano support > drm: bridge: samsung-dsim: Add i.MX8M Mini/Nano support > dt-bindings: display: exynos: dsim: Add NXP i.MX8M Plus support > > Marek Szyprowski (1): > drm: exynos: dsi: Handle proper host initialization > > Marek Vasut (1): > drm: bridge: samsung-dsim: Add i.MX8M Plus support > > .../bindings/display/exynos/exynos_dsim.txt|2 + > MAINTAINERS|9 + > drivers/gpu/drm/bridge/Kconfig | 12 + > drivers/gpu/drm/bridge/Makefile|1 + > drivers/gpu/drm/bridge/samsung-dsim.c | 1967 > > drivers/gpu/drm/exynos/Kconfig |1 + > drivers/gpu/drm/exynos/exynos_drm_dsi.c| 1813 +- > include/drm/bridge/samsung-dsim.h | 115 ++ > 8 files changed, 2191 insertions(+), 1729 deletions(-) > create mode 100644 drivers/gpu/drm/bridge/samsung-dsim.c > create mode 100644 include/drm/bridge/samsung-dsim.h -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
[GIT PULL] exynos-drm-next
Hi Dave and Daniel, Just one patch series that moves the existing Exynos DSI driver to drm/bridge directory to support both SoCs family - Exynos and I.MX - because same Exynos MIPI DSI ip can be used by the two different SoC family. Of course, there are some concerns about this patch series because Exynos and I.MX SoCs have different HW characteristic but use the same HW driver. However, I believe that there should be no problem as Exynos and I.MX developers have conducted tests and reviews enough for about a year since last April. This would be the first case that we allow different vendor SoCs to use same device driver at least in DRM world so we anticipate experiencing and resolving new issues through ongoing maintenance, and ultimately, the experiences gained here will undoubtedly be able to contribute the development of the community as well. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 46f28427f6f824b6cff06fa025a55350b7de454a: Merge tag 'drm-rcar-next-20230325' of git://git.kernel.org/pub/scm/linux/kernel/git/pinchartl/linux into drm-next (2023-03-27 18:20:20 +0200) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v6.4 for you to fetch changes up to b2cfec52feb3bb737c4b65018ef4bfe9789e4be8: drm: bridge: samsung-dsim: Add i.MX8M Plus support (2023-03-28 09:05:41 +0900) A patch series for moving MIPI-DSI driver for Exynos DRM to drm/bridge directory so that I.MX SoC family can also share the same device driver. Samsung MIPI DSIM device is a common IP that can be used by Exynos and I.MX8M Mini/Nano/Plus SoC. Regarding this, this patch series has added several things below to existing MIPI DSI driver, - Add exynos_dsi_type enum type to provide controller data from different platforms. - Add two pipeline detection ways support - existing Exynos DSI child node and I.MX family of-graph port or ports. - Consider component and bridged based DRM drivers. - Add device tree binding support of I.MX family. Jagan Teki (14): drm: exynos: dsi: Drop explicit call to bridge detach drm: exynos: dsi: Lookup OF-graph or Child node devices drm: exynos: dsi: Mark PHY as optional drm: exynos: dsi: Add platform PLL_P (PMS_P) offset drm: exynos: dsi: Introduce hw_type platform data drm: exynos: dsi: Add atomic check drm: exynos: dsi: Add input_bus_flags drm: exynos: dsi: Add atomic_get_input_bus_fmts drm: exynos: dsi: Consolidate component and bridge drm: exynos: dsi: Add host helper for te_irq_handler drm: bridge: Generalize Exynos-DSI driver into a Samsung DSIM bridge dt-bindings: display: exynos: dsim: Add NXP i.MX8M Mini/Nano support drm: bridge: samsung-dsim: Add i.MX8M Mini/Nano support dt-bindings: display: exynos: dsim: Add NXP i.MX8M Plus support Marek Szyprowski (1): drm: exynos: dsi: Handle proper host initialization Marek Vasut (1): drm: bridge: samsung-dsim: Add i.MX8M Plus support .../bindings/display/exynos/exynos_dsim.txt|2 + MAINTAINERS|9 + drivers/gpu/drm/bridge/Kconfig | 12 + drivers/gpu/drm/bridge/Makefile|1 + drivers/gpu/drm/bridge/samsung-dsim.c | 1967 drivers/gpu/drm/exynos/Kconfig |1 + drivers/gpu/drm/exynos/exynos_drm_dsi.c| 1813 +- include/drm/bridge/samsung-dsim.h | 115 ++ 8 files changed, 2191 insertions(+), 1729 deletions(-) create mode 100644 drivers/gpu/drm/bridge/samsung-dsim.c create mode 100644 include/drm/bridge/samsung-dsim.h
[GIT PULL] exynos-drm-next
Hi Dave and Daniel, Just one fixup series to restore proper bridge chain order of Exynos Display pipeline. This is also required by a patch series[1] which makes existing Exynos DSI driver to be common driver so that it can be used by Exynos and I.MX8MM SoC commonly - under the review yet. [1] https://lore.kernel.org/linux-arm-kernel/d4267645-448c-f702-fcc3-6c534d9ec...@denx.de/T/ Please let me know if there is any problem. Thanks, Inki Dae The following changes since commit 68de345e101ce9a24e5c8849e69dd0dba2e8c9b2: Merge tag 'drm-misc-next-2023-01-24' of git://anongit.freedesktop.org/drm/drm-misc into drm-next (2023-01-25 12:14:08 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v6.3 for you to fetch changes up to 1a1ce789e6c5da5a16d3d17bc228c6ab0b5863ed: drm: exynos: dsi: Restore proper bridge chain order (2023-01-26 15:11:24 +0900) One fixup series - Make sure to restore bridge chain order by enabling the drm panel prepare_prev_first flag of the bridge and panel drivers - tc358764 display bridge device and Samsung s6e3ha2/s6e63j0x03/s6e8aa0 panel devices. In case of any boards using Exynos5433 SoC, below Display pipeline could be configured. Decon -> MIC -> MIPI-DSI -> Panel So, this patch series makes sure to enable previous bridge device before enabling MIPI-DSI device. Jagan Teki (2): drm: panel: Enable prepare_prev_first flag for samsung-s6e panels drm: exynos: dsi: Restore proper bridge chain order Marek Szyprowski (1): drm/bridge: tc358764: Enable pre_enable_prev_first flag drivers/gpu/drm/bridge/tc358764.c| 1 + drivers/gpu/drm/exynos/exynos_drm_dsi.c | 9 +++-- drivers/gpu/drm/panel/panel-samsung-s6e3ha2.c| 1 + drivers/gpu/drm/panel/panel-samsung-s6e63j0x03.c | 1 + drivers/gpu/drm/panel/panel-samsung-s6e8aa0.c| 1 + 5 files changed, 11 insertions(+), 2 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave and Daniel, Sorry for late. Just one cleanup and fixup which corrects return type. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 320305923c88258ce50c75bf721e9bf2e420ab27: Merge tag 'du-next-20220907' of git://linuxtv.org/pinchartl/media into drm-next (2022-09-23 03:52:08 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v6.1 for you to fetch changes up to 1261255531088208daeca818e2b486030b5339e5: drm/exynos: Fix return type for mixer_mode_valid and hdmi_mode_valid (2022-09-26 10:13:00 +0900) Cleanup - Use drm_display_info.is_hdmi instead of drm_detect_hdmi_monitor() for efficiency. Fixup - Correct return type of mixer_mode_valid and hdmi_mode_valid functions. This was reported by Dan Carpenter, https://github.com/ClangBuiltLinux/linux/issues/1703 Nathan Huckleberry (1): drm/exynos: Fix return type for mixer_mode_valid and hdmi_mode_valid hongao (1): drm/exynos: replace drm_detect_hdmi_monitor() with drm_display_info.is_hdmi drivers/gpu/drm/exynos/exynos_hdmi.c | 6 +++--- drivers/gpu/drm/exynos/exynos_mixer.c | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave and Daniel, Just two cleanups which remove invalid maintainer info and one fixup for releasing resouce. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit c6a3d73592ae20f2f6306f823aa5121c83c88223: Merge tag 'drm-intel-gt-next-2022-06-29' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2022-07-01 14:14:52 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.20 for you to fetch changes up to 48b927770f8ad3f8cf4a024a552abf272af9f592: drm/exynos/exynos7_drm_decon: free resources when clk_set_parent() failed. (2022-07-12 13:56:54 +0900) Two cleanups - Remove Joonyoung Shim from MAINTAINERS and relevant yaml files. He left from Samsung so his email address isn't valid anymore. Fixup - Fix resume function issue of exynos decon driver by calling clk_disable_unprepare() properly if clk_prepare_enable() failed. Jian Zhang (1): drm/exynos/exynos7_drm_decon: free resources when clk_set_parent() failed. Krzysztof Kozlowski (2): drm/exynos: MAINTAINERS: move Joonyoung Shim to credits dt-bindings: remove Joonyoung Shim from maintainers CREDITS | 4 .../display/samsung/samsung,exynos-hdmi-ddc.yaml| 1 - .../bindings/display/samsung/samsung,exynos-hdmi.yaml | 1 - .../bindings/display/samsung/samsung,exynos-mixer.yaml | 1 - .../display/samsung/samsung,exynos5433-decon.yaml | 1 - .../display/samsung/samsung,exynos5433-mic.yaml | 1 - .../bindings/display/samsung/samsung,exynos7-decon.yaml | 1 - .../bindings/display/samsung/samsung,fimd.yaml | 1 - .../bindings/phy/samsung,exynos-hdmi-phy.yaml | 1 - MAINTAINERS | 1 - drivers/gpu/drm/exynos/exynos7_drm_decon.c | 17 + 11 files changed, 17 insertions(+), 13 deletions(-)
[GIT PULL] exynos-drm-next for v5.18
Hi Dave and Daniel, Just adding BGR pixel format support per a plane. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit fedc89821990013608bc210c9aef5bb33a1345a7: drm/exynos: Search for TE-gpio in DSI panel's node (2022-03-04 17:13:51 +0900) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-v5.18 for you to fetch changes up to 2d684f4e155c1e80ff63bd503930171c460eac5b: drm/exynos: fimd: add BGR support for exynos4/5 (2022-03-04 17:13:52 +0900) New feature - Add BGR pixel format support for FIMD device. As for this, this patch uses undocumented register, WIN_RGB_ORDER, but it is safe because product kernels have been using same register. Martin Jücker (1): drm/exynos: fimd: add BGR support for exynos4/5 drivers/gpu/drm/exynos/exynos_drm_fimd.c | 42 ++-- include/video/samsung_fimd.h | 4 +++ 2 files changed, 44 insertions(+), 2 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave and Daniel, Just four cleanups such as replacing the use of legacy interface, implementing generic gem mmap, fixing a build warning and dropping unnecessary code. Please let me know if there is any problem. Thanks, Inki Dae The following changes since commit 1c405ca11bf563de1725e5ecfb4a74ee289d2ee9: Merge tag 'mediatek-drm-next-5.17' of https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux into drm-next (2021-12-17 16:16:16 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.17 for you to fetch changes up to 760cceff996135fd4830f3d339446a04bd37ca0c: drm/exynos: drop the use of label from exynos_dsi_register_te_irq (2021-12-22 11:39:39 +0900) Four cleanups - Replacing lagacy gpio interface of dsi driver with gpiod one. - Implementing a generic GEM object mmap and use it instead of exynos specific one. - Dropping the use of label from dsi driver. Which also fixes a build warning. - Just trivial cleanup by dropping unnecessay code. Bernard Zhao (1): drm/exynos: remove useless type conversion Inki Dae (1): drm/exynos: drop the use of label from exynos_dsi_register_te_irq Maíra Canal (1): drm/exynos: Replace legacy gpio interface for gpiod interface Thomas Zimmermann (1): drm/exynos: Implement mmap as GEM object function drivers/gpu/drm/exynos/exynos_drm_drv.c | 13 ++-- drivers/gpu/drm/exynos/exynos_drm_dsi.c | 49 +++ drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 20 ++--- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 4 +-- drivers/gpu/drm/exynos/exynos_drm_gem.c | 43 ++- drivers/gpu/drm/exynos/exynos_drm_gem.h | 5 6 files changed, 32 insertions(+), 102 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave, Just two fixups - fixing one build warning and missing unlock, and one cleanup - replaceing atomic_t with refcount_t. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 397ab98e2d69cede8a28eab77a171983d14e: Merge tag 'drm-msm-next-2021-08-12' of https://gitlab.freedesktop.org/drm/msm into drm-next (2021-08-17 10:53:52 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.15 for you to fetch changes up to c626f386428bbe06476b0b497c1330aa4463: drm/exynos: Always initialize mapping in exynos_drm_register_dma() (2021-08-22 01:56:39 +0900) Two fixups - Fix missing unlock issue in exynos_drm_g2d.c - Fix a build warning in exynos_drm_dma.c One cleanup - Replace atomic_t with refcount_t in exynos_drm_g2d.c Nathan Chancellor (1): drm/exynos: Always initialize mapping in exynos_drm_register_dma() Wei Yongjun (1): drm/exynos: g2d: fix missing unlock on error in g2d_runqueue_worker() Xiyu Yang (1): drm/exynos: Convert from atomic_t to refcount_t on g2d_cmdlist_userptr->refcount drivers/gpu/drm/exynos/exynos_drm_dma.c | 2 ++ drivers/gpu/drm/exynos/exynos_drm_g2d.c | 14 -- 2 files changed, 10 insertions(+), 6 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave, Just two cleanups to replace pm_runtime_get_sync() with pm_runtime_resume_and_get(). Please kinkdly let me know if there is any problem. Thanks, Inki Dae The following changes since commit c707b73f0cfb1acc94a20389aecde65e6385349b: Merge tag 'amd-drm-next-5.14-2021-06-09' of https://gitlab.freedesktop.org/agd5f/linux into drm-next (2021-06-10 13:47:13 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.14 for you to fetch changes up to 445d3bed75de4082c7c7794030ac9a5b8bfde886: drm/exynos: use pm_runtime_resume_and_get() (2021-06-11 10:56:38 +0900) Two cleanups - These patches make Exynos DRM driver to use pm_runtime_resume_and_get() function instead of m_runtime_get_sync() to deal with usage counter. pm_runtime_get_sync() increases the usage counter even when it failed, which could make callers to forget to decrease the usage counter. pm_runtime_resume_and_get() decreases the usage counter regardless of whether it failed or not. Inki Dae (1): drm/exynos: use pm_runtime_resume_and_get() Tian Tao (1): drm/exynos: Use pm_runtime_resume_and_get() to replace open coding drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 7 ++- drivers/gpu/drm/exynos/exynos7_drm_decon.c| 7 ++- drivers/gpu/drm/exynos/exynos_drm_dsi.c | 7 ++- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 8 +++- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 25 - drivers/gpu/drm/exynos/exynos_drm_g2d.c | 9 - drivers/gpu/drm/exynos/exynos_drm_gsc.c | 7 ++- drivers/gpu/drm/exynos/exynos_drm_mic.c | 6 ++ drivers/gpu/drm/exynos/exynos_drm_rotator.c | 7 ++- drivers/gpu/drm/exynos/exynos_drm_scaler.c| 10 ++ drivers/gpu/drm/exynos/exynos_hdmi.c | 8 +++- drivers/gpu/drm/exynos/exynos_mixer.c | 7 ++- 12 files changed, 86 insertions(+), 22 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave, Just one patch to clean up the use of request_irq funtion. This patch has a dependency of one patch[1] so merged it on top of tag 'irq-no-autoen-2021-03-25' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip after top of drm next branch. Please kindly let me know if there is any problem. Thanks, Inki Dae [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next-history.git/commit/?id=cbe16f35bee6880becca6f20d2ebf6b457148552 The following changes since commit 99e5730dd2b11fedc890bbc9c803f69aad24e3ca: Merge tag 'irq-no-autoen-2021-03-25' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip into exynos-drm-next (2021-03-29 20:35:13 +0900) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.13 for you to fetch changes up to a4e5eed2c6a689ef2b6ad8d7ae86665c69039379: drm/exynos: move to use request_irq by IRQF_NO_AUTOEN flag (2021-03-29 20:37:17 +0900) One cleanup - Based on the patch[1], clean up the use of request_irq function series. [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next-history.git/commit/?id=cbe16f35bee6880becca6f20d2ebf6b457148552 Tian Tao (1): drm/exynos: move to use request_irq by IRQF_NO_AUTOEN flag drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 4 ++-- drivers/gpu/drm/exynos/exynos_drm_dsi.c | 7 +++ 2 files changed, 5 insertions(+), 6 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Just a new mode support for HDMI and two clenups. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 22f8c80566c4a29a0d8b5ebf24aa1fd1679b39e5: Merge tag 'drm-misc-next-2020-11-18' of ssh://git.freedesktop.org/git/drm/drm-misc into drm-next (2020-11-27 09:36:33 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.11 for you to fetch changes up to e11e6df2a86779cfc73c4fb2e957ff7a70d89f68: drm/exynos: use exynos_dsi as drvdata (2020-12-01 11:38:29 +0900) Add a new mode support for HDMI - support for 1920x1200x60Hz mode. Cleanups - Drop in_bridge_node from exynos_dsi - Use a exynos_dsi object instead of a encoder object as drvdata. Marek Szyprowski (1): drm/exynos/hdmi: add support for 1920x1200@60Hz mode Michael Tretter (2): drm/exynos: remove in_bridge_node from exynos_dsi drm/exynos: use exynos_dsi as drvdata drivers/gpu/drm/exynos/exynos_drm_dsi.c | 31 --- drivers/gpu/drm/exynos/exynos_hdmi.c| 9 + 2 files changed, 21 insertions(+), 19 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Just two cleanups. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit b40be05ed255d9a0257fb66ab2728ecca2c9d597: Merge branch 'for-5.10-drm-sg-fix' of https://github.com/mszyprow/linux into drm-next (2020-09-17 16:07:11 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-v5.10 for you to fetch changes up to ddfd4ab6bb08832e1261d7c8c4ae11e5568485af: drm/exynos: Fix dma_parms allocation (2020-09-22 13:49:09 +0900) Two cleanups - Simply use dev_err_probe() instead of returning -EPROBE_DEFER. - Drop drm_parms allocation and deallocation code which aren't needed. Krzysztof Kozlowski (2): drm/exynos: dsi: Simplify with dev_err_probe() drm/exynos: hdmi: Simplify with dev_err_probe() Marek Szyprowski (1): drm/exynos: Fix dma_parms allocation drivers/gpu/drm/exynos/exynos_drm_dma.c | 27 +-- drivers/gpu/drm/exynos/exynos_drm_dsi.c | 7 ++- drivers/gpu/drm/exynos/exynos_hdmi.c| 7 ++- 3 files changed, 5 insertions(+), 36 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Just several fixups and cleanups. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 1493bddcca4d601ca6f3dd27f2226f37a0f39732: Merge tag 'drm-misc-next-2020-05-14' of git://anongit.freedesktop.org/drm/drm-misc into drm-next (2020-05-15 12:23:25 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.8 for you to fetch changes up to f84e1ba336a4f47ae251e4d2d8a694902571b0df: drm/exynos-vidi: convert platform driver to use dev_groups (2020-05-18 13:19:18 +0900) Check imported buffer mapping in generic way - This patch reworks exynos_drm_gem_prime_import_sg_table function, which checks if the imported buffer has been mapped as contiguous or not in generic way, and flag a exynos gem buffer type properly according to the mapped way. Fixups - Drop a reference count to in_bridge_node correctly. - Enable the runtime power management correctly. . The runtime pm should be enabled before calling compont_add(). Cleanups - Do not register "by hand" a sysfs file, and use dev_groups instead. - Drop internal 'pages' array which aren't needed. - Remove dead-code. - Correct type casting. - Drop unnecessary error messages. Bernard Zhao (1): drm/exynos: make pointer to const data const type Christophe JAILLET (1): drm/exynos: dsi: Remove bridge node reference in error handling path in probe function Emil Velikov (1): drm/exynos-vidi: convert platform driver to use dev_groups Marek Szyprowski (4): drm/exynos: gem: Remove dead-code drm/exynos: gem: rework scatter-list contiguity check on prime import drm/exynos: gem: Get rid of the internal 'pages' array drm/exynos: mixer: Fix enabling of the runtime power management Markus Elfring (1): drm/exynos: Delete an error message in three functions drivers/gpu/drm/exynos/exynos_drm_drv.c | 1 - drivers/gpu/drm/exynos/exynos_drm_dsi.c | 26 ++-- drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 28 + drivers/gpu/drm/exynos/exynos_drm_gem.c | 182 ++-- drivers/gpu/drm/exynos/exynos_drm_gem.h | 16 +-- drivers/gpu/drm/exynos/exynos_drm_mic.c | 2 +- drivers/gpu/drm/exynos/exynos_drm_rotator.c | 4 +- drivers/gpu/drm/exynos/exynos_drm_scaler.c | 4 +- drivers/gpu/drm/exynos/exynos_drm_vidi.c| 26 ++-- drivers/gpu/drm/exynos/exynos_mixer.c | 6 +- 10 files changed, 103 insertions(+), 192 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
Hi Dave, 20. 3. 18. 오전 11:17에 Dave Airlie 이(가) 쓴 글: > This seems to contain a exynos drm fixes backmerge, please don't do > that without a headsup. > > Can you send one without that or do you need a fixes backmerge, if so > please request me to do that first, then rebase this and send it. Sorry for confusing you. Dropped the backmerge from exynos drm fixes and pushed it again. Please let me know if there is any problem. Thanks, Inki Dae > > Dave. > > On Mon, 16 Mar 2020 at 11:04, Inki Dae wrote: >> >> Just two cleanups - one is to mask encoder bitmask using >> drm_encoder_mask(), and other is to use mode->clock >> instead of calculating it again. >> >> Please kindly let me know if there is any problem. >> >> Thanks, >> Inki Dae >> >> The following changes since commit 69ddce0970d9d1de63bed9c24eefa0814db29a5a: >> >> Merge tag 'amd-drm-next-5.7-2020-03-10' of >> git://people.freedesktop.org/~agd5f/linux into drm-next (2020-03-13 09:09:11 >> +1000) >> >> are available in the git repository at: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos >> tags/exynos-drm-next-for-v5.7 >> >> for you to fetch changes up to 0c9a609ca444298e438ee9c6daaf53c14277f1ad: >> >> drm/exynos: Use mode->clock instead of reverse calculating it from the >> vrefresh (2020-03-16 09:50:28 +0900) >> >> >> Two cleanups >> . Replace the hand rolled encoder bitmask thing with drm_encoder_mask() >> . Use mode->clock instead of reverse calculating it from the vrefresh >> >> >> Inki Dae (1): >> Merge tag 'exynos-drm-fixes-for-v5.6-rc5-v2' of >> git://git.kernel.org/.../daeinki/drm-exynos into exynos-drm-next >> >> Marek Szyprowski (1): >> drm/exynos: Fix cleanup of IOMMU related objects >> >> Ville Syrjälä (2): >> drm/exynos: Use drm_encoder_mask() >> drm/exynos: Use mode->clock instead of reverse calculating it from the >> vrefresh >> >> drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 5 +++-- >> drivers/gpu/drm/exynos/exynos7_drm_decon.c| 7 --- >> drivers/gpu/drm/exynos/exynos_drm_dma.c | 28 >> ++- >> drivers/gpu/drm/exynos/exynos_drm_drv.c | 5 ++--- >> drivers/gpu/drm/exynos/exynos_drm_drv.h | 6 -- >> drivers/gpu/drm/exynos/exynos_drm_fimc.c | 5 +++-- >> drivers/gpu/drm/exynos/exynos_drm_fimd.c | 5 +++-- >> drivers/gpu/drm/exynos/exynos_drm_g2d.c | 5 +++-- >> drivers/gpu/drm/exynos/exynos_drm_gsc.c | 5 +++-- >> drivers/gpu/drm/exynos/exynos_drm_rotator.c | 5 +++-- >> drivers/gpu/drm/exynos/exynos_drm_scaler.c| 6 -- >> drivers/gpu/drm/exynos/exynos_mixer.c | 7 +-- >> 12 files changed, 56 insertions(+), 33 deletions(-) >> ___ >> dri-devel mailing list >> dri-devel@lists.freedesktop.org >> https://protect2.fireeye.com/url?k=2f99e96f-720f5018-2f986220-0cc47a312ab0-6a58a038adb2e152=https://lists.freedesktop.org/mailman/listinfo/dri-devel > > ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
This seems to contain a exynos drm fixes backmerge, please don't do that without a headsup. Can you send one without that or do you need a fixes backmerge, if so please request me to do that first, then rebase this and send it. Dave. On Mon, 16 Mar 2020 at 11:04, Inki Dae wrote: > > Just two cleanups - one is to mask encoder bitmask using > drm_encoder_mask(), and other is to use mode->clock > instead of calculating it again. > > Please kindly let me know if there is any problem. > > Thanks, > Inki Dae > > The following changes since commit 69ddce0970d9d1de63bed9c24eefa0814db29a5a: > > Merge tag 'amd-drm-next-5.7-2020-03-10' of > git://people.freedesktop.org/~agd5f/linux into drm-next (2020-03-13 09:09:11 > +1000) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos > tags/exynos-drm-next-for-v5.7 > > for you to fetch changes up to 0c9a609ca444298e438ee9c6daaf53c14277f1ad: > > drm/exynos: Use mode->clock instead of reverse calculating it from the > vrefresh (2020-03-16 09:50:28 +0900) > > > Two cleanups > . Replace the hand rolled encoder bitmask thing with drm_encoder_mask() > . Use mode->clock instead of reverse calculating it from the vrefresh > > > Inki Dae (1): > Merge tag 'exynos-drm-fixes-for-v5.6-rc5-v2' of > git://git.kernel.org/.../daeinki/drm-exynos into exynos-drm-next > > Marek Szyprowski (1): > drm/exynos: Fix cleanup of IOMMU related objects > > Ville Syrjälä (2): > drm/exynos: Use drm_encoder_mask() > drm/exynos: Use mode->clock instead of reverse calculating it from the > vrefresh > > drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 5 +++-- > drivers/gpu/drm/exynos/exynos7_drm_decon.c| 7 --- > drivers/gpu/drm/exynos/exynos_drm_dma.c | 28 > ++- > drivers/gpu/drm/exynos/exynos_drm_drv.c | 5 ++--- > drivers/gpu/drm/exynos/exynos_drm_drv.h | 6 -- > drivers/gpu/drm/exynos/exynos_drm_fimc.c | 5 +++-- > drivers/gpu/drm/exynos/exynos_drm_fimd.c | 5 +++-- > drivers/gpu/drm/exynos/exynos_drm_g2d.c | 5 +++-- > drivers/gpu/drm/exynos/exynos_drm_gsc.c | 5 +++-- > drivers/gpu/drm/exynos/exynos_drm_rotator.c | 5 +++-- > drivers/gpu/drm/exynos/exynos_drm_scaler.c| 6 -- > drivers/gpu/drm/exynos/exynos_mixer.c | 7 +-- > 12 files changed, 56 insertions(+), 33 deletions(-) > ___ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Just two cleanups - one is to mask encoder bitmask using drm_encoder_mask(), and other is to use mode->clock instead of calculating it again. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 69ddce0970d9d1de63bed9c24eefa0814db29a5a: Merge tag 'amd-drm-next-5.7-2020-03-10' of git://people.freedesktop.org/~agd5f/linux into drm-next (2020-03-13 09:09:11 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.7 for you to fetch changes up to 0c9a609ca444298e438ee9c6daaf53c14277f1ad: drm/exynos: Use mode->clock instead of reverse calculating it from the vrefresh (2020-03-16 09:50:28 +0900) Two cleanups . Replace the hand rolled encoder bitmask thing with drm_encoder_mask() . Use mode->clock instead of reverse calculating it from the vrefresh Inki Dae (1): Merge tag 'exynos-drm-fixes-for-v5.6-rc5-v2' of git://git.kernel.org/.../daeinki/drm-exynos into exynos-drm-next Marek Szyprowski (1): drm/exynos: Fix cleanup of IOMMU related objects Ville Syrjälä (2): drm/exynos: Use drm_encoder_mask() drm/exynos: Use mode->clock instead of reverse calculating it from the vrefresh drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 5 +++-- drivers/gpu/drm/exynos/exynos7_drm_decon.c| 7 --- drivers/gpu/drm/exynos/exynos_drm_dma.c | 28 ++- drivers/gpu/drm/exynos/exynos_drm_drv.c | 5 ++--- drivers/gpu/drm/exynos/exynos_drm_drv.h | 6 -- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 5 +++-- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 5 +++-- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 5 +++-- drivers/gpu/drm/exynos/exynos_drm_gsc.c | 5 +++-- drivers/gpu/drm/exynos/exynos_drm_rotator.c | 5 +++-- drivers/gpu/drm/exynos/exynos_drm_scaler.c| 6 -- drivers/gpu/drm/exynos/exynos_mixer.c | 7 +-- 12 files changed, 56 insertions(+), 33 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Just two changes - one changes Exynos drm specfic callback names for consistency, and other corrects the use of Exynos prefix. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit d7ca2d19c751b6715e9cb899a6b94f47b3499d02: Merge tag 'drm-msm-next-2020-01-14' of https://gitlab.freedesktop.org/drm/msm into drm-next (2020-01-20 14:09:43 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.6 for you to fetch changes up to c0bf499f6f84634c14cdec0afd1f17ff4121afa2: drm/exynos: Rename Exynos to lowercase (2020-01-21 09:09:42 +0900) Change Exynos DRM specific callback function names - it changes enable and disable callback functions names of struct exynos_drm_crtc_ops to atomic_enable and atomic_disable for consistency. Modify "EXYNOS" prefix to "Exynos" - "Exynos" name is a regular trademarked name promoted by its manufacturer, Samsung Electronics Co., Ltd.. This patch corrects the name. Inki Dae (1): drm/exynos: change callback names Krzysztof Kozlowski (1): drm/exynos: Rename Exynos to lowercase drivers/gpu/drm/exynos/Kconfig| 6 +++--- drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 10 +- drivers/gpu/drm/exynos/exynos7_drm_decon.c| 10 +- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 8 drivers/gpu/drm/exynos/exynos_drm_drv.h | 8 drivers/gpu/drm/exynos/exynos_drm_fimd.c | 10 +- drivers/gpu/drm/exynos/exynos_drm_vidi.c | 8 drivers/gpu/drm/exynos/exynos_mixer.c | 8 include/uapi/drm/exynos_drm.h | 2 +- 9 files changed, 35 insertions(+), 35 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Just one build warning fixup. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 3275a71e76fac5bc276f0d60e027b18c2e8d7a5b: Merge tag 'drm-next-5.5-2019-10-09' of git://people.freedesktop.org/~agd5f/linux into drm-next (2019-10-26 05:56:57 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.5 for you to fetch changes up to 5a884be5478990ed013c2b160d90615426848c61: drm/exynos: Move static keyword to the front of declaration (2019-10-28 21:12:27 +0900) Fix a build warning at mixer driver - it fixes a build warning message, 'static' is not at beginning of declaration [-Wold-style-declaration], by moving static keyword. Krzysztof Wilczynski (1): drm/exynos: Move static keyword to the front of declaration drivers/gpu/drm/exynos/exynos_mixer.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Just one patch which drops the use of drmP.h header file. Please kindly let me know if there is any problem. Thanks, INki Dae The following changes since commit 578d2342ec702e5fb8a77983fabb3754ae3e9660: Merge tag 'drm-next-5.4-2019-08-23' of git://people.freedesktop.org/~agd5f/linux into drm-next (2019-08-27 17:22:15 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.4 for you to fetch changes up to 226024b16685522ef8a97d881cffb90500ef1903: drm/exynos: drop use of drmP.h (2019-09-01 20:55:12 +0900) - JUst one cleanup which drops the use of drmP.h header file. Sam Ravnborg (1): drm/exynos: drop use of drmP.h drivers/gpu/drm/exynos/exynos_drm_drv.c | 8 drivers/gpu/drm/exynos/exynos_drm_fimc.c| 2 ++ drivers/gpu/drm/exynos/exynos_drm_gsc.c | 2 ++ drivers/gpu/drm/exynos/exynos_drm_ipp.c | 5 - drivers/gpu/drm/exynos/exynos_drm_ipp.h | 2 -- drivers/gpu/drm/exynos/exynos_drm_rotator.c | 2 ++ drivers/gpu/drm/exynos/exynos_drm_scaler.c | 1 + 7 files changed, 19 insertions(+), 3 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Just two cleanups - one is to drop drmP.h header, and other is to add COMPILE_TEST flag for increasing build test coverage. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 14808a12bdbdc21143eba70ea07830197b3a04ff: Merge tag 'drm-next-5.3-2019-06-25' of git://people.freedesktop.org/~agd5f/linux into drm-next (2019-06-27 12:33:57 +1000) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.3 for you to fetch changes up to 156bdac99061b4013c8e47799c6e574f7f84e9f4: drm/exynos: trigger build of all modules (2019-06-27 22:30:56 +0900) - Drop the use of drmP.h header file drmP.h header file has been deprecated so this patch drops the use of this header, and instead includes appropriate header files required. - Add COMPILE_TEST flag This patch adds COMPILE_TEST dependency to exynos drm driver to increase build test coverage. And also, it includes vmalloc.h header file to fix one build warning which is introduced when building the Linux kernel using sh. Sam Ravnborg (2): drm/exynos: drop drmP.h usage drm/exynos: trigger build of all modules drivers/gpu/drm/exynos/Kconfig| 6 ++-- drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 7 +++-- drivers/gpu/drm/exynos/exynos7_drm_decon.c| 8 -- drivers/gpu/drm/exynos/exynos_dp.c| 13 - drivers/gpu/drm/exynos/exynos_drm_crtc.c | 2 +- drivers/gpu/drm/exynos/exynos_drm_dma.c | 6 ++-- drivers/gpu/drm/exynos/exynos_drm_dpi.c | 8 +++--- drivers/gpu/drm/exynos/exynos_drm_drv.c | 12 drivers/gpu/drm/exynos/exynos_drm_drv.h | 8 +- drivers/gpu/drm/exynos/exynos_drm_dsi.c | 21 +++--- drivers/gpu/drm/exynos/exynos_drm_fb.c| 6 ++-- drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 8 -- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 15 +- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 14 + drivers/gpu/drm/exynos/exynos_drm_g2d.c | 11 --- drivers/gpu/drm/exynos/exynos_drm_gem.c | 7 +++-- drivers/gpu/drm/exynos/exynos_drm_gsc.c | 13 + drivers/gpu/drm/exynos/exynos_drm_ipp.c | 3 +- drivers/gpu/drm/exynos/exynos_drm_mic.c | 22 +++--- drivers/gpu/drm/exynos/exynos_drm_plane.c | 4 +-- drivers/gpu/drm/exynos/exynos_drm_rotator.c | 10 +++ drivers/gpu/drm/exynos/exynos_drm_scaler.c| 12 drivers/gpu/drm/exynos/exynos_drm_vidi.c | 9 +++--- drivers/gpu/drm/exynos/exynos_hdmi.c | 41 +-- drivers/gpu/drm/exynos/exynos_mixer.c | 31 ++-- 25 files changed, 158 insertions(+), 139 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
Hi Dave, 19. 4. 24. 오전 11:03에 Dave Airlie 이(가) 쓴 글: > Hi Inki, > CC [M] drivers/gpu/drm/exynos/exynos_drm_scaler.o > /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/exynos/exynos_drm_rotator.c: > In function ‘rotator_unbind’: > /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/exynos/exynos_drm_rotator.c:262:21: > warning: unused variable ‘drm_dev’ [-Wunused-variable] > struct drm_device *drm_dev = data; > ^~~ > /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/exynos/exynos_drm_scaler.c: > In function ‘scaler_unbind’: > /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/exynos/exynos_drm_scaler.c:472:21: > warning: unused variable ‘drm_dev’ [-Wunused-variable] > struct drm_device *drm_dev = data; > ^~~ > LD [M] drivers/gpu/drm/exynos/exynosdrm.o > > are those new? please fix and resent the pull > Sorry for this. I missed to remove them with some cleanup. Will resend the pull. Thanks, Inki Dae > Dave. > > On Mon, 22 Apr 2019 at 19:50, Inki Dae wrote: >> >> Hi Dave, >> >>Just log cleanup patches of Exynos KMS and DMA drivers >>including one trivial style fixup. >> >>Please kinkdly let me know if there is any problem. >> >> >> Thanks, >> Inki Dae >> >> >> The following changes since commit dbb92471674a48892f5e50779425e03388073ab9: >> >> Revert "drm: allow render capable master with DRM_AUTH ioctls" (2019-04-18 >> 06:46:33 +1000) >> >> are available in the git repository at: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos >> tags/exynos-drm-next-for-v5.2 >> >> for you to fetch changes up to 35319804851fad62dfa6284f4e638a7e2a620fe8: >> >> drm/ipp: clean up debug messages (2019-04-22 12:13:44 +0900) >> >> >> Log cleanups >> - Correct the use of log macro in error case. >> - Drop unnecessary messages. >> - Replace DRM_ERROR/DEBUG with DRM_DEV_ERROR/DEBUG. >> - Print out debug messages with correct device name in vidi and ipp drivers. >> >> One trivial cleanup >> - Just fix checkpatch error, "foo* bar" to "foo *bar" in g2d driver. >> >> >> Inki Dae (6): >> drm/fimd: use DRM_ERROR instead of DRM_INFO in error case >> drm/exynos: remove unnecessary messages >> drm/exynos: use DRM_DEV_ERROR to print out error message >> drm/exynos: use DRM_DEV_DEBUG* instead of DRM_DEBUG macro >> drm/vidi: replace platform_device pointer with device one >> drm/ipp: clean up debug messages >> >> Seung-Woo Kim (1): >> drm/exynos: g2d: remove style error >> >> drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 6 +- >> drivers/gpu/drm/exynos/exynos7_drm_decon.c| 26 +++ >> drivers/gpu/drm/exynos/exynos_dp.c| 9 ++- >> drivers/gpu/drm/exynos/exynos_drm_dma.c | 2 +- >> drivers/gpu/drm/exynos/exynos_drm_dpi.c | 9 ++- >> drivers/gpu/drm/exynos/exynos_drm_dsi.c | 7 +- >> drivers/gpu/drm/exynos/exynos_drm_fb.c| 9 ++- >> drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 26 --- >> drivers/gpu/drm/exynos/exynos_drm_fimc.c | 97 >> ++- >> drivers/gpu/drm/exynos/exynos_drm_fimd.c | 48 +++-- >> drivers/gpu/drm/exynos/exynos_drm_g2d.c | 51 +++--- >> drivers/gpu/drm/exynos/exynos_drm_gem.c | 35 +- >> drivers/gpu/drm/exynos/exynos_drm_gsc.c | 72 ++-- >> drivers/gpu/drm/exynos/exynos_drm_ipp.c | 71 >> drivers/gpu/drm/exynos/exynos_drm_ipp.h | 9 +-- >> drivers/gpu/drm/exynos/exynos_drm_mic.c | 29 >> drivers/gpu/drm/exynos/exynos_drm_plane.c | 15 +++-- >> drivers/gpu/drm/exynos/exynos_drm_rotator.c | 5 +- >> drivers/gpu/drm/exynos/exynos_drm_scaler.c| 5 +- >> drivers/gpu/drm/exynos/exynos_drm_vidi.c | 49 -- >> drivers/gpu/drm/exynos/exynos_hdmi.c | 75 - >> drivers/gpu/drm/exynos/exynos_mixer.c | 43 +++- >> 22 files changed, 400 insertions(+), 298 deletions(-) >> ___ >> dri-devel mailing list >> dri-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/dri-devel > > ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
Hi Inki, CC [M] drivers/gpu/drm/exynos/exynos_drm_scaler.o /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/exynos/exynos_drm_rotator.c: In function ‘rotator_unbind’: /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/exynos/exynos_drm_rotator.c:262:21: warning: unused variable ‘drm_dev’ [-Wunused-variable] struct drm_device *drm_dev = data; ^~~ /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/exynos/exynos_drm_scaler.c: In function ‘scaler_unbind’: /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/exynos/exynos_drm_scaler.c:472:21: warning: unused variable ‘drm_dev’ [-Wunused-variable] struct drm_device *drm_dev = data; ^~~ LD [M] drivers/gpu/drm/exynos/exynosdrm.o are those new? please fix and resent the pull Dave. On Mon, 22 Apr 2019 at 19:50, Inki Dae wrote: > > Hi Dave, > >Just log cleanup patches of Exynos KMS and DMA drivers >including one trivial style fixup. > >Please kinkdly let me know if there is any problem. > > > Thanks, > Inki Dae > > > The following changes since commit dbb92471674a48892f5e50779425e03388073ab9: > > Revert "drm: allow render capable master with DRM_AUTH ioctls" (2019-04-18 > 06:46:33 +1000) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos > tags/exynos-drm-next-for-v5.2 > > for you to fetch changes up to 35319804851fad62dfa6284f4e638a7e2a620fe8: > > drm/ipp: clean up debug messages (2019-04-22 12:13:44 +0900) > > > Log cleanups > - Correct the use of log macro in error case. > - Drop unnecessary messages. > - Replace DRM_ERROR/DEBUG with DRM_DEV_ERROR/DEBUG. > - Print out debug messages with correct device name in vidi and ipp drivers. > > One trivial cleanup > - Just fix checkpatch error, "foo* bar" to "foo *bar" in g2d driver. > > > Inki Dae (6): > drm/fimd: use DRM_ERROR instead of DRM_INFO in error case > drm/exynos: remove unnecessary messages > drm/exynos: use DRM_DEV_ERROR to print out error message > drm/exynos: use DRM_DEV_DEBUG* instead of DRM_DEBUG macro > drm/vidi: replace platform_device pointer with device one > drm/ipp: clean up debug messages > > Seung-Woo Kim (1): > drm/exynos: g2d: remove style error > > drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 6 +- > drivers/gpu/drm/exynos/exynos7_drm_decon.c| 26 +++ > drivers/gpu/drm/exynos/exynos_dp.c| 9 ++- > drivers/gpu/drm/exynos/exynos_drm_dma.c | 2 +- > drivers/gpu/drm/exynos/exynos_drm_dpi.c | 9 ++- > drivers/gpu/drm/exynos/exynos_drm_dsi.c | 7 +- > drivers/gpu/drm/exynos/exynos_drm_fb.c| 9 ++- > drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 26 --- > drivers/gpu/drm/exynos/exynos_drm_fimc.c | 97 > ++- > drivers/gpu/drm/exynos/exynos_drm_fimd.c | 48 +++-- > drivers/gpu/drm/exynos/exynos_drm_g2d.c | 51 +++--- > drivers/gpu/drm/exynos/exynos_drm_gem.c | 35 +- > drivers/gpu/drm/exynos/exynos_drm_gsc.c | 72 ++-- > drivers/gpu/drm/exynos/exynos_drm_ipp.c | 71 > drivers/gpu/drm/exynos/exynos_drm_ipp.h | 9 +-- > drivers/gpu/drm/exynos/exynos_drm_mic.c | 29 > drivers/gpu/drm/exynos/exynos_drm_plane.c | 15 +++-- > drivers/gpu/drm/exynos/exynos_drm_rotator.c | 5 +- > drivers/gpu/drm/exynos/exynos_drm_scaler.c| 5 +- > drivers/gpu/drm/exynos/exynos_drm_vidi.c | 49 -- > drivers/gpu/drm/exynos/exynos_hdmi.c | 75 - > drivers/gpu/drm/exynos/exynos_mixer.c | 43 +++- > 22 files changed, 400 insertions(+), 298 deletions(-) > ___ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Just log cleanup patches of Exynos KMS and DMA drivers including one trivial style fixup. Please kinkdly let me know if there is any problem. Thanks, Inki Dae The following changes since commit dbb92471674a48892f5e50779425e03388073ab9: Revert "drm: allow render capable master with DRM_AUTH ioctls" (2019-04-18 06:46:33 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.2 for you to fetch changes up to 35319804851fad62dfa6284f4e638a7e2a620fe8: drm/ipp: clean up debug messages (2019-04-22 12:13:44 +0900) Log cleanups - Correct the use of log macro in error case. - Drop unnecessary messages. - Replace DRM_ERROR/DEBUG with DRM_DEV_ERROR/DEBUG. - Print out debug messages with correct device name in vidi and ipp drivers. One trivial cleanup - Just fix checkpatch error, "foo* bar" to "foo *bar" in g2d driver. Inki Dae (6): drm/fimd: use DRM_ERROR instead of DRM_INFO in error case drm/exynos: remove unnecessary messages drm/exynos: use DRM_DEV_ERROR to print out error message drm/exynos: use DRM_DEV_DEBUG* instead of DRM_DEBUG macro drm/vidi: replace platform_device pointer with device one drm/ipp: clean up debug messages Seung-Woo Kim (1): drm/exynos: g2d: remove style error drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 6 +- drivers/gpu/drm/exynos/exynos7_drm_decon.c| 26 +++ drivers/gpu/drm/exynos/exynos_dp.c| 9 ++- drivers/gpu/drm/exynos/exynos_drm_dma.c | 2 +- drivers/gpu/drm/exynos/exynos_drm_dpi.c | 9 ++- drivers/gpu/drm/exynos/exynos_drm_dsi.c | 7 +- drivers/gpu/drm/exynos/exynos_drm_fb.c| 9 ++- drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 26 --- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 97 ++- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 48 +++-- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 51 +++--- drivers/gpu/drm/exynos/exynos_drm_gem.c | 35 +- drivers/gpu/drm/exynos/exynos_drm_gsc.c | 72 ++-- drivers/gpu/drm/exynos/exynos_drm_ipp.c | 71 drivers/gpu/drm/exynos/exynos_drm_ipp.h | 9 +-- drivers/gpu/drm/exynos/exynos_drm_mic.c | 29 drivers/gpu/drm/exynos/exynos_drm_plane.c | 15 +++-- drivers/gpu/drm/exynos/exynos_drm_rotator.c | 5 +- drivers/gpu/drm/exynos/exynos_drm_scaler.c| 5 +- drivers/gpu/drm/exynos/exynos_drm_vidi.c | 49 -- drivers/gpu/drm/exynos/exynos_hdmi.c | 75 - drivers/gpu/drm/exynos/exynos_mixer.c | 43 +++- 22 files changed, 400 insertions(+), 298 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Just adding s5pv210 SoC support of rotator module and changing email address of scaler module author. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 2cc3b81dfa7f7de0d647e7f1473de811eef8b0de: Merge tag 'drm-intel-next-2019-02-02' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2019-02-04 15:37:58 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v5.1 for you to fetch changes up to 9c0c4997b8a80ec4ba77c4ebe3e74ec0db2d547d: drm/exynos: Change Andrzej Pietrasiewicz's e-mail address (2019-02-07 19:59:44 +0900) - Add rotator support for s5pv210 . With this patch series, s5pv210 SoC can use rotator module but only NV12 and XRGB formats are supported. - Modify e-mail address . It changes email address of scaler module author. Andrzej Pietrasiewicz (1): drm/exynos: Change Andrzej Pietrasiewicz's e-mail address Paweł Chmiel (2): drm/exynos: rotator: Add support for s5pv210 dt-bindings: gpu: samsung-rotator: Document s5pv210 support .../devicetree/bindings/gpu/samsung-rotator.txt| 7 --- drivers/gpu/drm/exynos/exynos_drm_rotator.c| 23 ++ drivers/gpu/drm/exynos/exynos_drm_scaler.c | 2 +- drivers/gpu/drm/exynos/regs-scaler.h | 2 +- 4 files changed, 29 insertions(+), 5 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Three patch series - code refactoring for simplifying DMA mapping, enhancing plane alpha and blend mode support for Exynos5433 Decon device, and fixing color format setting of Mixer driver. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 167bfe534dc2de680ef706dbb903c9a7bfcb2dd8: Documentation: drm: Remove dangling pointer from drm-mm.rst (2018-11-30 08:55:37 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v4.21 for you to fetch changes up to 13e810f199b48383523707aa69fb9673d688055a: drm/exynos: mixer: Fix color range setting (2018-12-05 17:35:21 +0900) - Refactoring of DMA and IOMMU code . This patch series simplifies DMA mapping creation by avoiding looping all components to get dma device object, reduces code size by merging IOMMU and DMA code. - Enhance plane alpha and blend mode support . This patch series adds configurable plane and pixel blend mode support for Exynos5433 DECON device. - Fix color format setting of Mixer driver . This patch series fixes color format and range setting by splitting range and format. Andrzej Hajda (6): drm/exynos: simplify DMA mapping drm/exynos/iommu: remove DRM_EXYNOS_IOMMU Kconfig symbol drm/exynos/iommu: integrate IOMMU/DMA internal API drm/exynos/iommu: move IOMMU specific stuff into exynos_drm_iommu.c drm/exynos/iommu: replace preprocessor conditionals with C conditionals drm/exynos/iommu: merge IOMMU and DMA code Christoph Manszewski (4): drm/exynos: decon: Make plane alpha configurable drm/exynos: decon: Make pixel blend mode configurable drm/exynos: mixer: Fix color format setting drm/exynos: mixer: Fix color range setting drivers/gpu/drm/exynos/Kconfig| 5 - drivers/gpu/drm/exynos/Makefile | 3 +- drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 87 +- drivers/gpu/drm/exynos/exynos7_drm_decon.c| 5 +- drivers/gpu/drm/exynos/exynos_drm_dma.c | 157 ++ drivers/gpu/drm/exynos/exynos_drm_drv.c | 55 ++--- drivers/gpu/drm/exynos/exynos_drm_drv.h | 11 ++ drivers/gpu/drm/exynos/exynos_drm_fb.c| 1 - drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 1 - drivers/gpu/drm/exynos/exynos_drm_fimc.c | 5 +- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 5 +- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 5 +- drivers/gpu/drm/exynos/exynos_drm_gem.c | 1 - drivers/gpu/drm/exynos/exynos_drm_gsc.c | 5 +- drivers/gpu/drm/exynos/exynos_drm_iommu.c | 111 -- drivers/gpu/drm/exynos/exynos_drm_iommu.h | 134 -- drivers/gpu/drm/exynos/exynos_drm_rotator.c | 5 +- drivers/gpu/drm/exynos/exynos_drm_scaler.c| 5 +- drivers/gpu/drm/exynos/exynos_mixer.c | 30 ++--- drivers/gpu/drm/exynos/regs-decon5433.h | 22 drivers/gpu/drm/exynos/regs-mixer.h | 9 +- 21 files changed, 314 insertions(+), 348 deletions(-) create mode 100644 drivers/gpu/drm/exynos/exynos_drm_dma.c delete mode 100644 drivers/gpu/drm/exynos/exynos_drm_iommu.c delete mode 100644 drivers/gpu/drm/exynos/exynos_drm_iommu.h ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Adding out-bridge support for the use of LVDS bridge device to MIPI-DSI driver, Samsung 16x16 tiled format support to scalder and gsc drivers and configurable plane alpha and pixel blend mode supports to mixer driver including one cleanup for removing exynos specific suspend_state. As for Samsung 16x16 tiled format support, I picked one patch up, which adds DRM_FORMAT_MOD_SAMSUNG_16_16_TILE definition to drm_forcc.h header file. The only user of this format is exynos so I requested ack-by[1] to relevant maintainers on 27 Aug. but no any response. [1] https://patchwork.freedesktop.org/patch/243921/ Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 0320ac5188eab5c6e8b92b110d1eae967ac272d2: Merge tag 'du-next-20180914' of git://linuxtv.org/pinchartl/media into drm-next (2018-09-20 14:12:07 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v4.20 for you to fetch changes up to 6ac99a328ee16d3f8cc253f1df62623cee3e9ea5: drm/exynos: mixer: Make plane alpha configurable (2018-10-01 11:49:59 +0900) Add out-bridge support - This patch series enables out-bridge for LVDS bridge device support, and also includes two cleanups and one relevant dt binding update for this. Add Samsung 16x16 tiled format support - This patch series adds Samsung 16x16 tiled format to scaler and gsc drivers. As for this, it adds Samsung specific format to drm_forcc.h header. For the git-pull request with relevant patches, I requested ack-by[1] to relevant maintainers but there was no any response. I'm pretty sure no problem to go to mainline though Exynos tree because the only user of it is Exynos. [1] https://patchwork.freedesktop.org/patch/243921/ Add configurable plane alpha and pixel blend mode support - This patch series makes mixer driver to be configuragle for pixel blend mode and plane alpha, which also includes one fixup to set all default values correctly after reset. One cleanup - This patch replaces drm_atomic_helper_suspend/resume() with drm_mode_config_helper_suspend/resume() to remove exynos specific suspend_state. Andrzej Hajda (1): dt-bindings: exynos_dsim: update of graph bindings Andrzej Pietrasiewicz (2): drm: drm_fourcc: add Samsung 16x16 tile format drm/exynos: scaler: Add support for tiled formats Christoph Manszewski (3): drm/exynos: drm_plane: Correct exynos_drm_plane_reset drm/exynos: mixer: Make pixel blend mode configurable drm/exynos: mixer: Make plane alpha configurable Maciej Purski (3): drm/exynos: rename bridge_node to in_bridge_node drm/exynos: move connector creation to attach callback drm/exynos: enable out_bridge in exynos_dsi_enable Marek Szyprowski (1): drm/exynos: gsc: Add support for tiled formats Souptick Joarder (1): gpu/drm/exynos: Convert drm_atomic_helper_suspend/resume() .../bindings/display/exynos/exynos_dsim.txt| 25 +--- drivers/gpu/drm/exynos/exynos_drm_drv.c| 26 +--- drivers/gpu/drm/exynos/exynos_drm_drv.h| 3 +- drivers/gpu/drm/exynos/exynos_drm_dsi.c| 107 +--- drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 17 --- drivers/gpu/drm/exynos/exynos_drm_fbdev.h | 10 -- drivers/gpu/drm/exynos/exynos_drm_gsc.c| 46 +-- drivers/gpu/drm/exynos/exynos_drm_plane.c | 16 ++- drivers/gpu/drm/exynos/exynos_drm_scaler.c | 137 - drivers/gpu/drm/exynos/exynos_mixer.c | 56 ++--- drivers/gpu/drm/exynos/regs-mixer.h| 5 +- include/uapi/drm/drm_fourcc.h | 9 ++ 12 files changed, 249 insertions(+), 208 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Two big cleanups to suspend/resume code and g2d driver including trivial one. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 2d3bda7071a713fa4ecf9d0acb7faede6d59100a: Merge tag 'exynos-drm-fixes-for-v4.18-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into exynos-drm-next (2018-07-24 15:28:44 +0900) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v4.19 for you to fetch changes up to 3f2b78d630b46c7921cb415be35f686e5293c3a4: drm/exynos/mixer: Remove unused local variable priv (2018-07-24 16:28:53 +0900) Cleanups - Change g2d driver to component based driver . g2d driver was last customed sub driver so this patch series changes it to component based driver, which also makes gem handling to be more simplify. - Cleanup of Exynos DRM suspend/resume . Register exynos drm core suspend/resume functions to prepare/complete callbacks of dev_pm_ops instead of suspend/resume callbacks to ensure exynos_drm_suspend() is called before any suspend callback from the real devices to avoid some issues on boards with complex pipelines. . Also Add pm_runtime_furce_suspend/resume as SYSTEM_SLEEP_PM_OPS to ensure that resources of each devices will be released for the system PM suspend/resume cycle. - Remove local value not used. Krzysztof Kozlowski (1): drm/exynos/mixer: Remove unused local variable priv Marek Szyprowski (6): drm/exynos: g2d: Convert to driver component API drm/exynos: gem: Simplify access to exynos GEM objects drm/exynos: Use common exynos_drm_gem_get()/put() functions for GEM lookup drm/exynos: Drop useless check from exynos_drm_{suspend,resume} drm/exynos: Suspend/resume display pipeline as early/late as possible drm/exynos: Ensure suspended runtime PM state during system suspend drivers/gpu/drm/exynos/Makefile | 2 +- drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 2 + drivers/gpu/drm/exynos/exynos7_drm_decon.c| 2 + drivers/gpu/drm/exynos/exynos_dp.c| 3 + drivers/gpu/drm/exynos/exynos_drm_core.c | 119 -- drivers/gpu/drm/exynos/exynos_drm_drv.c | 29 +-- drivers/gpu/drm/exynos/exynos_drm_drv.h | 47 +--- drivers/gpu/drm/exynos/exynos_drm_dsi.c | 2 + drivers/gpu/drm/exynos/exynos_drm_fb.c| 10 +- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 2 + drivers/gpu/drm/exynos/exynos_drm_g2d.c | 300 ++ drivers/gpu/drm/exynos/exynos_drm_g2d.h | 11 + drivers/gpu/drm/exynos/exynos_drm_gem.c | 58 + drivers/gpu/drm/exynos/exynos_drm_gem.h | 24 +-- drivers/gpu/drm/exynos/exynos_drm_ipp.c | 10 +- drivers/gpu/drm/exynos/exynos_drm_mic.c | 2 + drivers/gpu/drm/exynos/exynos_hdmi.c | 2 + drivers/gpu/drm/exynos/exynos_mixer.c | 4 +- 18 files changed, 179 insertions(+), 450 deletions(-) delete mode 100644 drivers/gpu/drm/exynos/exynos_drm_core.c ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Adding S5PV210 FIMD variant and IPPv2 support. As for IPPv2, we have applied the use of IPPv2 userspace API to a real user, which was what other maintainers pointed out. And it includes two cleanups to MIPI-DSI driver and GEM module. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit a02cbe2e34c576cdc5e7846a3cd55245ab81db47: Merge branch 'vmwgfx-fixes-4.17' of git://people.freedesktop.org/~thomash/linux into drm-fixes (2018-05-04 10:03:27 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v4.18 for you to fetch changes up to e892fa718da5758ff877592f33fea368ca8a: drm/exynos/dsi: remove mode_set callback (2018-05-14 08:06:45 +0900) - Add S5PV210 FIMD variant support. - Add IPP v2 framework. . it is a rewritten version of the Exynos mem-to-mem image processing framework which supprts color space conversion, image up/down-scaling and rotation. This new version replaces existing userspace API with new easy-to-use and simple ones so we have already applied the use of these API to real user, Tizen Platform[1], and also makes existing Scaler, FIMC, GScaler and Rotator drivers to use IPP v2 core API. And below are patch lists we have applied to a real user, https://git.tizen.org/cgit/platform/adaptation/samsung_exynos/libtdm-exynos/log/?h=tizen=grep=ipp https://git.tizen.org/cgit/platform/adaptation/samsung_exynos/libtdm-exynos/commit/?h=tizen=b59be207365d10efd489e6f71c8a045b558c44fe https://git.tizen.org/cgit/platform/kernel/linux-exynos/log/?h=tizen=grep=ipp TDM(Tizen Display Manager) is a Display HAL for Tizen platform. Ps. Only real user using IPP API is Tizen. [1] https://www.tizen.org/ - Two cleanups . One is to just remove mode_set callback from MIPI-DSI driver because drm_display_mode data is already available from crtc atomic state. . And other is to just use new return type, vm_fault_t for page fault handler. Andrzej Hajda (2): drm/exynos/mixer: fix synchronization check in interlaced mode drm/exynos/dsi: remove mode_set callback Andrzej Pietrasiewicz (1): drm/exynos: Add driver for Exynos Scaler module Inki Dae (1): Merge tag 'exynos-drm-fixes-for-v4.17-rc5' of git://git.kernel.org/.../daeinki/drm-exynos into exynos-drm-next Marek Szyprowski (4): drm/exynos: ipp: Add IPP v2 framework drm/exynos: rotator: Convert driver to IPP v2 core API drm/exynos: gsc: Convert driver to IPP v2 core API drm/exynos: fimc: Convert driver to IPP v2 core API Pawel Chmiel (1): drm/exynos: Allow DRM_EXYNOS on s5pv210. Peter Rosin (1): drm/exynos: hdmi: avoid duplicating drm_bridge_attach Souptick Joarder (1): gpu: drm: exynos: Change return type to vm_fault_t Tobias Jakobi (1): drm/exynos: mixer: avoid Oops in vp_video_buffer() Tomasz Figa (1): drm/exynos: fimd: Add support for S5PV210 FIMD variant .../devicetree/bindings/gpu/samsung-scaler.txt | 27 + drivers/gpu/drm/exynos/Kconfig | 18 +- drivers/gpu/drm/exynos/Makefile|2 + drivers/gpu/drm/exynos/exynos_drm_drv.c| 35 +- drivers/gpu/drm/exynos/exynos_drm_drv.h| 10 + drivers/gpu/drm/exynos/exynos_drm_dsi.c| 40 +- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 1080 +++- drivers/gpu/drm/exynos/exynos_drm_fimc.h | 23 - drivers/gpu/drm/exynos/exynos_drm_fimd.c |8 + drivers/gpu/drm/exynos/exynos_drm_gem.c| 21 +- drivers/gpu/drm/exynos/exynos_drm_gem.h|3 +- drivers/gpu/drm/exynos/exynos_drm_gsc.c| 1075 ++- drivers/gpu/drm/exynos/exynos_drm_gsc.h| 24 - drivers/gpu/drm/exynos/exynos_drm_ipp.c| 916 + drivers/gpu/drm/exynos/exynos_drm_ipp.h| 175 drivers/gpu/drm/exynos/exynos_drm_rotator.c| 758 -- drivers/gpu/drm/exynos/exynos_drm_scaler.c | 694 + drivers/gpu/drm/exynos/exynos_hdmi.c |2 - drivers/gpu/drm/exynos/exynos_mixer.c | 22 +- drivers/gpu/drm/exynos/regs-mixer.h|1 + drivers/gpu/drm/exynos/regs-scaler.h | 426 include/uapi/drm/exynos_drm.h | 240 + 22 files changed, 3450 insertions(+), 2150 deletions(-) create mode 100644 Documentation/devicetree/bindings/gpu/samsung-scaler.txt delete mode 100644 drivers/gpu/drm/exynos/exynos_drm_fimc.h delete mode 100644 drivers/gpu/drm/exynos/exynos_drm_gsc.h create mode 100644 drivers/gpu/drm/exynos/exynos_drm_ipp.c create mode 100644
[GIT PULL] exynos-drm-next
Hi Dave, Just removing lagacy IPP driver and several trivial cleanups. As discussed already, we are preparing a new version of IPP driver which will include rewritten code and API. Removing the lagacy IPP driver is a first step for use of the new driver. Please kindly let me know if there is any problem. Happy new year~ Thanks, Inki Dae The following changes since commit 350877626faba5d60cbb8cef2bdeb524212c780b: Merge tag 'drm-intel-next-2017-12-22' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2017-12-28 05:20:31 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v4.16 for you to fetch changes up to 8ded59413ccc58fe138ab4bf337d0d0b3131d46b: drm/exynos: ipp: Remove Exynos DRM IPP subsystem (2018-01-02 08:41:22 +0900) Remove lagacy IPP driver - This driver isn't used anymore so remove it. Marek is preparing new one which includes completely rewritten API so this driver will be replaced with the new version[1] later. And cleanups. [1] https://patches.linaro.org/cover/118386/ Fabio Estevam (1): drm/exynos: decon5433: Remove unnecessary platform_get_resource() error check Krzysztof Kozlowski (2): drm/exynos/decon: Move headers from global to local place drm/exynos/decon: Add include guard to the Exynos7 header Marek Szyprowski (1): drm/exynos: ipp: Remove Exynos DRM IPP subsystem drivers/gpu/drm/exynos/Kconfig | 11 +- drivers/gpu/drm/exynos/Makefile|1 - drivers/gpu/drm/exynos/exynos5433_drm_decon.c |8 +- drivers/gpu/drm/exynos/exynos7_drm_decon.c |2 +- drivers/gpu/drm/exynos/exynos_drm_drv.c| 12 - drivers/gpu/drm/exynos/exynos_drm_drv.h|2 - drivers/gpu/drm/exynos/exynos_drm_ipp.c| 1806 drivers/gpu/drm/exynos/exynos_drm_ipp.h| 252 --- .../gpu/drm/exynos/regs-decon5433.h|6 +- .../gpu/drm/exynos/regs-decon7.h |8 +- include/uapi/drm/exynos_drm.h | 192 +-- 11 files changed, 15 insertions(+), 2285 deletions(-) delete mode 100644 drivers/gpu/drm/exynos/exynos_drm_ipp.c delete mode 100644 drivers/gpu/drm/exynos/exynos_drm_ipp.h rename include/video/exynos5433_decon.h => drivers/gpu/drm/exynos/regs-decon5433.h (98%) rename include/video/exynos7_decon.h => drivers/gpu/drm/exynos/regs-decon7.h (99%) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
On Tue, Nov 28, 2017 at 02:45:49PM +0100, Marek Szyprowski wrote: > Hi Daniel, > > On 2017-11-20 08:33, Daniel Vetter wrote: > > On Wed, Nov 15, 2017 at 10:26:45AM +0900, Inki Dae wrote: > > > 2017년 11월 14일 13:22에 Dave Airlie 이(가) 쓴 글: > > > > On 26 October 2017 at 11:37, Inki Daewrote: > > > > > Improving Exynos DRM HDMI and Mixer drivers and also adding > > > > > HDMI audio support. > > > > > > > > > > Please kindly let me know if there is any problem. > > > > > > > > > > Ps. we are reviewing IPP v2 driver[1] which controls post > > > > > processor devices > > > > > such as FIMC, GScaler and Rotator of Exynos SoC. So I plan to > > > > > request > > > > > git pull one more time after review. > > > > I dropped the ball a bit here, I do think the second pull with IPP is > > > > probably a bit late, > > > > I think I'd like more assurance that the UAPI for IPP is to be used in > > > > some upstream > > > > shipping project (forks of mpv not withstanding, unless this fork > > > > ships in some distro > > > > or product). > > > I also commented same thing internally to author - Marek - of IPP v2 but > > > I thought existing one is really ugly thing so may be better to change it > > > as soon as possible before other users use this one. > > > Anyway, we will merge user space for IPP v2 to libdrm first, and then > > > Linux platform. I hope IPPv2 would be merged as soon as possible in next > > > turn. > > Beyond what Daniel said we unfortunately don't have time machines, so > > fixing bad uapi isn't really possible. The problem is that even if you > > create ippv2, then people can still use ippv1, and it needs to keep > > working (almost) forever. So once a bad uapi is in, it's in, and there's > > no good reason to add more uapi (since in 2 years you might again realize > > it's not a good idea) to "fix" that. You can't fix bad uapi. > > > > That's why we have all these rules to make sure as little bad uapi as > > possible lands, since the cost is so bad. > > > > So yeah unless you have new hw that needs it, or there's another clear > > need (performance, features), you're stuck with ippv1. "It's cleaner" is > > not a good reason to rev uapi, since our experience with all the uapi in > > drm clearly shows we can't predict the future :-) > > I generally agree that UAPI interface has to be stable and well designed. > > There are however some 'features' IPPv1 uapi that really allows us to > obsolete it: > > 1. IPP API can be optional in Exynos DRM, so userspace should not rely that > it is always available and should have a software fallback in case it is not > available. > > 2. The only mode which was initially semi-working was memory-to-memory. The > remaining modes (lcd-writeback and output) were never operational (both in > mainline and even vendor kernels). > > 3. IPP mainline uapi compatibility for memory-to-memory got broken very > early by commit 083500baefd5f4c215a5a93aef2492c1aa775828 ("drm: remove > DRM_FORMAT_NV12MT", which removed the support for tiled formats, the main > feature which made this api somehow useful on Exynos platforms (video codec > that time produced only tiled frames, to implement xvideo or any other > video overlay, one has to detile them for proper display). > > 4. Broken drivers. Especially once support for IOMMU has been added, it > revealed that drivers don't configure DMA operations properly and in many > cases operate outside the provided buffers trashing memory around. > > 5. Need for external patches. Although IPP uapi has been used in some > vendor kernels, but in such cases there were additional patches applied > (like reverting mentioned 083500baefd5 patch) what means that those > userspace apps which might use it, still won't work with the mainline > version. > > Right, as you already said we don't have time machines, so we cannot change > it, but IPP extension should never have been merged to mainline in that > form. > > We can however obsolete it now as it is really non-functional and frankly > speaking dead-code. If you agree with the above than at least the first > patch can be merged, which clearly marks that Exynos IPP is broken and > ever really functional. I bet no one will complain. Then we can continue > the discussion about IPPv2 uapi/patches. Ok, if what's currently is upstream is indeed entirely non-functional then I think we can make a case for ippv2. But imo we should then also first rip out ippv1. Which given that it's optional, and apparently your userspace can cope, should be doable without causing any big trouble. But now that you explained why ippv1 is a hopeless patient that won't make it, why is ippv2 better? Do we have solid testcases for this stuff now? Is the userspace production quality or still kinda just a tech demo? -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch ___ dri-devel mailing
Re: [GIT PULL] exynos-drm-next
Hi Daniel, 2017년 11월 20일 16:33에 Daniel Vetter 이(가) 쓴 글: > On Wed, Nov 15, 2017 at 10:26:45AM +0900, Inki Dae wrote: >> Hi Dave, >> >> 2017년 11월 14일 13:22에 Dave Airlie 이(가) 쓴 글: >>> On 26 October 2017 at 11:37, Inki Daewrote: Hi Dave, Improving Exynos DRM HDMI and Mixer drivers and also adding HDMI audio support. Please kindly let me know if there is any problem. Ps. we are reviewing IPP v2 driver[1] which controls post processor devices such as FIMC, GScaler and Rotator of Exynos SoC. So I plan to request git pull one more time after review. >>> >>> Hi Inki, >>> >>> I dropped the ball a bit here, I do think the second pull with IPP is >>> probably a bit late, >>> I think I'd like more assurance that the UAPI for IPP is to be used in >>> some upstream >>> shipping project (forks of mpv not withstanding, unless this fork >>> ships in some distro >>> or product). >> >> I also commented same thing internally to author - Marek - of IPP v2 but I >> thought existing one is really ugly thing so may be better to change it as >> soon as possible before other users use this one. >> Anyway, we will merge user space for IPP v2 to libdrm first, and then Linux >> platform. I hope IPPv2 would be merged as soon as possible in next turn. > > Beyond what Daniel said we unfortunately don't have time machines, so > fixing bad uapi isn't really possible. The problem is that even if you > create ippv2, then people can still use ippv1, and it needs to keep > working (almost) forever. So once a bad uapi is in, it's in, and there's I'd like to make sure one thing. Yes, there may be some users who still use ippv1 but we should consider them even they aren't 'real user'? I.e., some test applications used internally. As long as I know, only 'real user' who uses ippv1 would be me and my team. If we have to consider all users including in-house test applications then we may need to keep UAPI v1 and only change its implementation. Thanks, Inki Dae > no good reason to add more uapi (since in 2 years you might again realize > it's not a good idea) to "fix" that. You can't fix bad uapi. > > That's why we have all these rules to make sure as little bad uapi as > possible lands, since the cost is so bad. > > So yeah unless you have new hw that needs it, or there's another clear > need (performance, features), you're stuck with ippv1. "It's cleaner" is > not a good reason to rev uapi, since our experience with all the uapi in > drm clearly shows we can't predict the future :-) > -Daniel > ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
Hi Daniel, On 2017-11-20 08:33, Daniel Vetter wrote: On Wed, Nov 15, 2017 at 10:26:45AM +0900, Inki Dae wrote: 2017년 11월 14일 13:22에 Dave Airlie 이(가) 쓴 글: On 26 October 2017 at 11:37, Inki Daewrote: Improving Exynos DRM HDMI and Mixer drivers and also adding HDMI audio support. Please kindly let me know if there is any problem. Ps. we are reviewing IPP v2 driver[1] which controls post processor devices such as FIMC, GScaler and Rotator of Exynos SoC. So I plan to request git pull one more time after review. I dropped the ball a bit here, I do think the second pull with IPP is probably a bit late, I think I'd like more assurance that the UAPI for IPP is to be used in some upstream shipping project (forks of mpv not withstanding, unless this fork ships in some distro or product). I also commented same thing internally to author - Marek - of IPP v2 but I thought existing one is really ugly thing so may be better to change it as soon as possible before other users use this one. Anyway, we will merge user space for IPP v2 to libdrm first, and then Linux platform. I hope IPPv2 would be merged as soon as possible in next turn. Beyond what Daniel said we unfortunately don't have time machines, so fixing bad uapi isn't really possible. The problem is that even if you create ippv2, then people can still use ippv1, and it needs to keep working (almost) forever. So once a bad uapi is in, it's in, and there's no good reason to add more uapi (since in 2 years you might again realize it's not a good idea) to "fix" that. You can't fix bad uapi. That's why we have all these rules to make sure as little bad uapi as possible lands, since the cost is so bad. So yeah unless you have new hw that needs it, or there's another clear need (performance, features), you're stuck with ippv1. "It's cleaner" is not a good reason to rev uapi, since our experience with all the uapi in drm clearly shows we can't predict the future :-) I generally agree that UAPI interface has to be stable and well designed. There are however some 'features' IPPv1 uapi that really allows us to obsolete it: 1. IPP API can be optional in Exynos DRM, so userspace should not rely that it is always available and should have a software fallback in case it is not available. 2. The only mode which was initially semi-working was memory-to-memory. The remaining modes (lcd-writeback and output) were never operational (both in mainline and even vendor kernels). 3. IPP mainline uapi compatibility for memory-to-memory got broken very early by commit 083500baefd5f4c215a5a93aef2492c1aa775828 ("drm: remove DRM_FORMAT_NV12MT", which removed the support for tiled formats, the main feature which made this api somehow useful on Exynos platforms (video codec that time produced only tiled frames, to implement xvideo or any other video overlay, one has to detile them for proper display). 4. Broken drivers. Especially once support for IOMMU has been added, it revealed that drivers don't configure DMA operations properly and in many cases operate outside the provided buffers trashing memory around. 5. Need for external patches. Although IPP uapi has been used in some vendor kernels, but in such cases there were additional patches applied (like reverting mentioned 083500baefd5 patch) what means that those userspace apps which might use it, still won't work with the mainline version. Right, as you already said we don't have time machines, so we cannot change it, but IPP extension should never have been merged to mainline in that form. We can however obsolete it now as it is really non-functional and frankly speaking dead-code. If you agree with the above than at least the first patch can be merged, which clearly marks that Exynos IPP is broken and ever really functional. I bet no one will complain. Then we can continue the discussion about IPPv2 uapi/patches. Best regards -- Marek Szyprowski, PhD Samsung R Institute Poland ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
On Wed, Nov 15, 2017 at 10:26:45AM +0900, Inki Dae wrote: > Hi Dave, > > 2017년 11월 14일 13:22에 Dave Airlie 이(가) 쓴 글: > > On 26 October 2017 at 11:37, Inki Daewrote: > >> Hi Dave, > >> > >>Improving Exynos DRM HDMI and Mixer drivers and also adding > >>HDMI audio support. > >> > >>Please kindly let me know if there is any problem. > >> > >>Ps. we are reviewing IPP v2 driver[1] which controls post processor > >> devices > >>such as FIMC, GScaler and Rotator of Exynos SoC. So I plan to > >> request > >>git pull one more time after review. > > > > Hi Inki, > > > > I dropped the ball a bit here, I do think the second pull with IPP is > > probably a bit late, > > I think I'd like more assurance that the UAPI for IPP is to be used in > > some upstream > > shipping project (forks of mpv not withstanding, unless this fork > > ships in some distro > > or product). > > I also commented same thing internally to author - Marek - of IPP v2 but I > thought existing one is really ugly thing so may be better to change it as > soon as possible before other users use this one. > Anyway, we will merge user space for IPP v2 to libdrm first, and then Linux > platform. I hope IPPv2 would be merged as soon as possible in next turn. Beyond what Daniel said we unfortunately don't have time machines, so fixing bad uapi isn't really possible. The problem is that even if you create ippv2, then people can still use ippv1, and it needs to keep working (almost) forever. So once a bad uapi is in, it's in, and there's no good reason to add more uapi (since in 2 years you might again realize it's not a good idea) to "fix" that. You can't fix bad uapi. That's why we have all these rules to make sure as little bad uapi as possible lands, since the cost is so bad. So yeah unless you have new hw that needs it, or there's another clear need (performance, features), you're stuck with ippv1. "It's cleaner" is not a good reason to rev uapi, since our experience with all the uapi in drm clearly shows we can't predict the future :-) -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
Hi Daniel, 2017년 11월 15일 19:27에 Daniel Stone 이(가) 쓴 글: > Hi Inki, > > On 15 November 2017 at 01:26, Inki Daewrote: >> 2017년 11월 14일 13:22에 Dave Airlie 이(가) 쓴 글: >>> On 26 October 2017 at 11:37, Inki Dae wrote: Ps. we are reviewing IPP v2 driver[1] which controls post processor devices such as FIMC, GScaler and Rotator of Exynos SoC. So I plan to request git pull one more time after review. >>> >>> I dropped the ball a bit here, I do think the second pull with IPP is >>> probably a bit late, >>> I think I'd like more assurance that the UAPI for IPP is to be used in >>> some upstream >>> shipping project (forks of mpv not withstanding, unless this fork >>> ships in some distro >>> or product). >> >> I also commented same thing internally to author - Marek - of IPP v2 but I >> thought existing one is really ugly thing so may be better to change it as >> soon as possible before other users use this one. >> Anyway, we will merge user space for IPP v2 to libdrm first, and then Linux >> platform. I hope IPPv2 would be merged as soon as possible in next turn. > > This is putting the cart before the horse a little bit. This is the > process for merging new DRM API: > > Prepare the kernel and libdrm/etc patches exposing the new API, and > also develop a _real_ user for it. Using IPP as an example, an > acceptable userspace would be VLC, Kodi, Weston, Xorg, or similar. > libdrm sample clients are explicitly not enough for this. > > Once this is done, you should get review/ack for all of these. The > kernel code and API should have review for good API (see for example > Daniel Vetter's 'botching up ioctls' documentation) and code, and the > userspace (VLC/Kodi/...) should have review for both code correctness > as well as an explicit check from the userspace side that they feel it > is good API which works for them. If the work just exists in a fork > which has not got real upstream review, this is also not enough. > > When all parts have review, you can merge the new kernel API with a > pointer to the userspace review, explicitly stating that they feel it > is acceptable. Once the kernel code has landed in a non-rebasing tree > (one which Dave will be sending as a pull), libdrm code can be merged, > and then the userspace code can finally be merged. I know that. Before requesting git-pull I commented like below to the author, "I think other maintainer will require real user space - not thing like libdrm - which uses new ABI. The solution I think would be to apply the new ABI to tdm exynos backend of Tizen platform below, https://review.tizen.org/git/?p=platform/adaptation/samsung_exynos/libtdm-exynos.git;a=blob;f=src/tdm_exynos_pp.c;h=db20e6f226d313672d1d468e06d80526ea30121c;hb=refs/heads/tizen; Anyway, Linux platform I mentioned is _real_ user, Tizen[1], for it. Sorry about it. I didn't comment exactly what is the Linux platform. And thanks for explanation. [1] https://www.tizen.org/ Thanks, Inki Dae > > Cheers, > Daniel > -- > 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 > > > ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
Hi Inki, On 15 November 2017 at 01:26, Inki Daewrote: > 2017년 11월 14일 13:22에 Dave Airlie 이(가) 쓴 글: >> On 26 October 2017 at 11:37, Inki Dae wrote: >>>Ps. we are reviewing IPP v2 driver[1] which controls post processor >>> devices >>>such as FIMC, GScaler and Rotator of Exynos SoC. So I plan to request >>>git pull one more time after review. >> >> I dropped the ball a bit here, I do think the second pull with IPP is >> probably a bit late, >> I think I'd like more assurance that the UAPI for IPP is to be used in >> some upstream >> shipping project (forks of mpv not withstanding, unless this fork >> ships in some distro >> or product). > > I also commented same thing internally to author - Marek - of IPP v2 but I > thought existing one is really ugly thing so may be better to change it as > soon as possible before other users use this one. > Anyway, we will merge user space for IPP v2 to libdrm first, and then Linux > platform. I hope IPPv2 would be merged as soon as possible in next turn. This is putting the cart before the horse a little bit. This is the process for merging new DRM API: Prepare the kernel and libdrm/etc patches exposing the new API, and also develop a _real_ user for it. Using IPP as an example, an acceptable userspace would be VLC, Kodi, Weston, Xorg, or similar. libdrm sample clients are explicitly not enough for this. Once this is done, you should get review/ack for all of these. The kernel code and API should have review for good API (see for example Daniel Vetter's 'botching up ioctls' documentation) and code, and the userspace (VLC/Kodi/...) should have review for both code correctness as well as an explicit check from the userspace side that they feel it is good API which works for them. If the work just exists in a fork which has not got real upstream review, this is also not enough. When all parts have review, you can merge the new kernel API with a pointer to the userspace review, explicitly stating that they feel it is acceptable. Once the kernel code has landed in a non-rebasing tree (one which Dave will be sending as a pull), libdrm code can be merged, and then the userspace code can finally be merged. Cheers, Daniel ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
Hi Dave, 2017년 11월 14일 13:22에 Dave Airlie 이(가) 쓴 글: > On 26 October 2017 at 11:37, Inki Daewrote: >> Hi Dave, >> >>Improving Exynos DRM HDMI and Mixer drivers and also adding >>HDMI audio support. >> >>Please kindly let me know if there is any problem. >> >>Ps. we are reviewing IPP v2 driver[1] which controls post processor >> devices >>such as FIMC, GScaler and Rotator of Exynos SoC. So I plan to request >>git pull one more time after review. > > Hi Inki, > > I dropped the ball a bit here, I do think the second pull with IPP is > probably a bit late, > I think I'd like more assurance that the UAPI for IPP is to be used in > some upstream > shipping project (forks of mpv not withstanding, unless this fork > ships in some distro > or product). I also commented same thing internally to author - Marek - of IPP v2 but I thought existing one is really ugly thing so may be better to change it as soon as possible before other users use this one. Anyway, we will merge user space for IPP v2 to libdrm first, and then Linux platform. I hope IPPv2 would be merged as soon as possible in next turn. Thanks, Inki Dae > > I unfortunately forgot to pull this one, I've rectified that and it is > now in drm-next. > > Dave. > -- > 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 > > > ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
On 26 October 2017 at 11:37, Inki Daewrote: > Hi Dave, > >Improving Exynos DRM HDMI and Mixer drivers and also adding >HDMI audio support. > >Please kindly let me know if there is any problem. > >Ps. we are reviewing IPP v2 driver[1] which controls post processor devices >such as FIMC, GScaler and Rotator of Exynos SoC. So I plan to request >git pull one more time after review. Hi Inki, I dropped the ball a bit here, I do think the second pull with IPP is probably a bit late, I think I'd like more assurance that the UAPI for IPP is to be used in some upstream shipping project (forks of mpv not withstanding, unless this fork ships in some distro or product). I unfortunately forgot to pull this one, I've rectified that and it is now in drm-next. Dave. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next-v2
Hi Dave, Just added new IPP driver since previous pull request. We rewrited Exynos DRM IPP driver due to below limitations and issues, - Userspace API covers memory-2-memory picture operations together with CRTC writeback and duplicating features, which belongs to video plane. - Lack of support of the all required image formats (for example NV12 Samsung-tiled cannot be used due to lack of pixel format modifier support). - Userspace API designed only to mimic hardware behaviour, not easy to understand. - Lack of proper input validation in the core, drivers also didn't do that correctly, so it was possible to set incorrect parameters and easil trigger IOMMU fault or memory trash. - Drivers were partially disfunctional or supported only a subset of modes. There is no user who uses old API excepting Tizen platform[1] we are developing, and we will update the platform with new version. Sample applications for new version, https://www.spinics.net/lists/linux-samsung-soc/msg60498.html https://github.com/tobiasjakobi/libdrm/blob/ippv2/exynos/exynos_ipp.c Please kindly let me know if there is any problem. [1] https://www.tizen.org/ Thanks, Inki Dae The following changes since commit d65d31388a23b14df9494135ad6c6549a59a3caa: Merge tag 'drm-misc-next-fixes-2017-11-07' of git://anongit.freedesktop.org/drm/drm-misc into drm-next (2017-11-08 05:22:49 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v4.15-v2 for you to fetch changes up to e3e0028489c9eb3f0157f980a078c4197da8f9de: drm/exynos: Add driver for Exynos Scaler module (2017-11-09 19:59:22 +0900) - Improved HDMI and Mixer drivers . It moves mode setup and plane update code to commit like other CRTC drivers . It makes mode commit to be called in enable callback only one time . some cleanup and fixup to HDMI and Mixer drivers. . It adds 1024x768, 1280x1024 and 1366x768 modes support - Added HDMI audio interface driver . As of now, HDMI audio worked on boards with external audio codec connected in parallel with the HDMI audio transmitter's I2S interface. This patch is required to support HDMI audio properly. - Remove old version of Exynos DRM IPP driver and add new version. - Convert each post processing driver - Rotator, GScaler and FIMC - to new API. Andrzej Hajda (10): drm/exynos/mixer: abstract out output mode setup code drm/exynos/mixer: move mode commit to enable callback drm/exynos/mixer: move resolution configuration to single function drm/exynos/mixer: fix mode validation code drm/exynos/mixer: remove mixer_resources sub-structure drm/exynos/hdmi: remove redundant mode field drm/exynos: add mode_fixup callback to exynos_drm_crtc_ops drm/exynos/mixer: pass actual mode on MIXER to encoder drm/exynos/hdmi: quirk for support mode timings conversion drm/exynos/mixer: enable support for 1024x768 and 1280x1024 modes Andrzej Pietrasiewicz (1): drm/exynos: Add driver for Exynos Scaler module Daniel Drake (1): drm/exynos/hdmi: add 85.5MHz pixel clock for v14 HDMI PHY Marek Szyprowski (5): drm/exynos: ipp: Remove Exynos DRM IPP subsystem drm/exynos: ipp: Add IPP v2 framework drm/exynos: rotator: Convert driver to IPP v2 core API drm/exynos: gsc: Convert driver to IPP v2 core API drm/exynos: fimc: Convert driver to IPP v2 core API Sylwester Nawrocki (1): drm: exynos: Add driver for HDMI audio interface .../devicetree/bindings/gpu/samsung-scaler.txt | 27 + drivers/gpu/drm/exynos/Kconfig | 18 +- drivers/gpu/drm/exynos/Makefile|1 + drivers/gpu/drm/exynos/exynos_drm_crtc.c | 15 + drivers/gpu/drm/exynos/exynos_drm_drv.c| 28 +- drivers/gpu/drm/exynos/exynos_drm_drv.h| 15 +- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 1035 +++-- drivers/gpu/drm/exynos/exynos_drm_fimc.h | 23 - drivers/gpu/drm/exynos/exynos_drm_gsc.c| 1063 +++-- drivers/gpu/drm/exynos/exynos_drm_gsc.h| 24 - drivers/gpu/drm/exynos/exynos_drm_ipp.c| 2256 ++-- drivers/gpu/drm/exynos/exynos_drm_ipp.h| 337 ++- drivers/gpu/drm/exynos/exynos_drm_rotator.c| 758 ++- drivers/gpu/drm/exynos/exynos_drm_rotator.h| 19 - drivers/gpu/drm/exynos/exynos_drm_scaler.c | 694 ++ drivers/gpu/drm/exynos/exynos_hdmi.c | 310 ++- drivers/gpu/drm/exynos/exynos_mixer.c | 460 ++-- drivers/gpu/drm/exynos/regs-hdmi.h |8 +- drivers/gpu/drm/exynos/regs-scaler.h | 426 include/uapi/drm/exynos_drm.h
[GIT PULL] exynos-drm-next
Hi Dave, Improving Exynos DRM HDMI and Mixer drivers and also adding HDMI audio support. Please kindly let me know if there is any problem. Ps. we are reviewing IPP v2 driver[1] which controls post processor devices such as FIMC, GScaler and Rotator of Exynos SoC. So I plan to request git pull one more time after review. Thanks, Inki Dae [1] https://www.spinics.net/lists/linux-samsung-soc/msg60981.html This is a link to v3 patch set and now v4 has been posted. The following changes since commit 62884cd386b876638720ef88374b31a84ca7ee5f: drm: Add four ioctls for managing drm mode object leases [v7] (2017-10-25 16:31:30 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v4.15 for you to fetch changes up to 691da76f9c90fa618682b88f386b6a1ef304666e: drm: exynos: Add driver for HDMI audio interface (2017-10-26 09:06:34 +0900) - Improved HDMI and Mixer drivers . It moves mode setup and plane update code to commit like other CRTC drivers . It makes mode commit to be called in enable callback only one time . some cleanup and fixup to HDMI and Mixer drivers. . It adds 1024x768, 1280x1024 and 1366x768 modes support - Added HDMI audio interface driver . As of now, HDMI audio worked on boards with external audio codec connected in parallel with the HDMI audio transmitter's I2S interface. This patch is required to support HDMI audio properly. Andrzej Hajda (10): drm/exynos/mixer: abstract out output mode setup code drm/exynos/mixer: move mode commit to enable callback drm/exynos/mixer: move resolution configuration to single function drm/exynos/mixer: fix mode validation code drm/exynos/mixer: remove mixer_resources sub-structure drm/exynos/hdmi: remove redundant mode field drm/exynos: add mode_fixup callback to exynos_drm_crtc_ops drm/exynos/mixer: pass actual mode on MIXER to encoder drm/exynos/hdmi: quirk for support mode timings conversion drm/exynos/mixer: enable support for 1024x768 and 1280x1024 modes Daniel Drake (1): drm/exynos/hdmi: add 85.5MHz pixel clock for v14 HDMI PHY Sylwester Nawrocki (1): drm: exynos: Add driver for HDMI audio interface drivers/gpu/drm/exynos/Kconfig | 1 + drivers/gpu/drm/exynos/exynos_drm_crtc.c | 15 + drivers/gpu/drm/exynos/exynos_drm_drv.h | 3 + drivers/gpu/drm/exynos/exynos_hdmi.c | 310 +++-- drivers/gpu/drm/exynos/exynos_mixer.c| 460 --- drivers/gpu/drm/exynos/regs-hdmi.h | 8 +- 6 files changed, 476 insertions(+), 321 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Just refactoring to KMS drivers - NV12MT pixel format, possible_crtc, panel detection way and video/command mode supports. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 7c0059dd832cc686bf0febefdcf8295cdd93007f: Merge branch 'linux-4.14' of git://github.com/skeggsb/linux into drm-next (2017-08-23 05:32:26 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-v4.14 for you to fetch changes up to 5b7b1b7fa10145c014750b09ff4cf31ac4e1843a: drm/exynos: simplify set_pixfmt() in DECON and FIMD drivers (2017-08-25 14:30:27 +0900) Summary: - Provide NV12MT pixel format support of Mixer driver in generic way. - Refactor Exynos KMS drivers . Refactoring to panel detection way . Refactoring to setting up possible_crtcs . Refactoring to video and command mode support - Some cleanups Andrzej Hajda (10): drm/exynos/decon5433: use readl_poll_timeout helpers drm/exynos: use helper to set possible crtcs drm/exynos/dsi: refactor panel detection logic drm/exynos/dsi: propagate info about command mode from panel drm/exynos/mic: use mode info stored in CRTC to detect i80 mode drm/exynos/decon5433: refactor irq requesting code drm/exynos: add mode_valid callback to exynos_drm drm/exynos/decon5433: use mode info stored in CRTC to detect i80 mode dt-bindings: exynos5433-decon: remove i80-if-timings property arm64: dts: exynos: remove i80-if-timings nodes Tobias Jakobi (7): drm/exynos: mixer: fix chroma comment in vp_video_buffer() drm/exynos: mixer: enable NV12MT support for the video plane drm/exynos: mixer: simplify vp_video_buffer() drm/exynos: mixer: simplify mixer_graph_buffer() drm/exynos: mixer: remove src offset from mixer_graph_buffer() drm/exynos: consistent use of cpp drm/exynos: simplify set_pixfmt() in DECON and FIMD drivers .../bindings/display/exynos/exynos5433-decon.txt | 12 -- .../boot/dts/exynos/exynos5433-tm2-common.dtsi | 6 - drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 124 ++-- drivers/gpu/drm/exynos/exynos7_drm_decon.c | 13 +- drivers/gpu/drm/exynos/exynos_dp.c | 15 +- drivers/gpu/drm/exynos/exynos_drm_core.c | 1 + drivers/gpu/drm/exynos/exynos_drm_crtc.c | 33 +++- drivers/gpu/drm/exynos/exynos_drm_crtc.h | 10 +- drivers/gpu/drm/exynos/exynos_drm_dpi.c| 12 +- drivers/gpu/drm/exynos/exynos_drm_drv.h| 5 + drivers/gpu/drm/exynos/exynos_drm_dsi.c| 218 ++--- drivers/gpu/drm/exynos/exynos_drm_fb.c | 2 + drivers/gpu/drm/exynos/exynos_drm_fimd.c | 16 +- drivers/gpu/drm/exynos/exynos_drm_mic.c| 44 + drivers/gpu/drm/exynos/exynos_drm_plane.c | 27 +++ drivers/gpu/drm/exynos/exynos_drm_vidi.c | 15 +- drivers/gpu/drm/exynos/exynos_hdmi.c | 25 +-- drivers/gpu/drm/exynos/exynos_mixer.c | 48 ++--- 18 files changed, 299 insertions(+), 327 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next-for-v4.13
Hi Dave, Some cleanups and fixups to resolve race condition issue between interrupt handlers and timeout issue at wait-for-vblank. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 2a1720376adda5ecf8e636fbfb05339c7dad1c55: Backmerge tag 'v4.12-rc3' into drm-next (2017-05-30 15:54:15 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v4.13 for you to fetch changes up to ce42cf4b03e6ad1a6316b2a74a4ceae4b70adcac: drm/exynos/decon5433: remove useless check (2017-06-01 16:21:38 +0900) Summary: - Rework vblank handling . This patch series adds frame counter callback and removes unnecessary pipe relevnt fields and simplifies event handling. - clean up and fix up sw-trigger relevant code . This patch series moves TE relevant code from Panel and HDMI to DECON driver to fix a race between interrupt handlers and DECON disable, and to fix timeout issue at wait-for-vblank. . It removes unnecessary flags and check code specific to Exynos driver. Andrzej Hajda (21): drm/exynos: simplify completion event handling drm/exynos/decon5433: implement frame counter drm/exynos: kill exynos_drm_crtc::pipe drm/exynos: kill exynos_drm_private::pipe drm/exynos: set plane possible_crtcs in exynos_plane_init drm/exynos: kill pipe field from drivers contexts drm/exynos: kill mode_set_nofb callback drm/exynos/decon5433: kill DECON_UPDATE workaround drm/exynos/decon5433: kill BIT_IRQS_ENABLED drm/exynos/decon5433: simplify shadow protect code drm/exynos/hdmi: fix pipeline disable order drm/exynos/dsi: fix bridge_node DT parsing drm/exynos/decon5433: always do sw-trigger when vblanks enabled dt-bindings: exynos5433-decon: fix interrupts bindings dt-bindings: exynos5433-decon: add TE interrupt binding drm/exynos/decon5433: move TE handling to DECON drm/exynos/decon5433: kill BIT_IRQS_ENABLED flag drm/exynos/decon5433: kill BIT_CLKS_ENABLED flag drm/exynos/decon5433: kill BIT_WIN_UPDATED flag drm/exynos/decon5433: kill BIT_SUSPENDED flag drm/exynos/decon5433: remove useless check Daniel Vetter (1): drm/exynos: Merge pre/postclose hooks Hoegeun Kwon (2): drm/exynos: dsi: Fix the parse_dt function drm/exynos: dsi: Remove bridge node reference in removal Inki Dae (2): drm/exynos: clean up description of exynos_drm_crtc Merge tag 'exynos-drm-fixes-for-v4.12' of git://git.kernel.org/.../daeinki/drm-exynos into exynos-drm-next Tobias Jakobi (2): drm/exynos: mixer: simplify mixer_cfg_rgb_fmt() drm/exynos: mixer: document YCbCr magic numbers .../bindings/display/exynos/exynos5433-decon.txt | 13 +- drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 218 + drivers/gpu/drm/exynos/exynos7_drm_decon.c | 19 +- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 50 +++-- drivers/gpu/drm/exynos/exynos_drm_crtc.h | 1 - drivers/gpu/drm/exynos/exynos_drm_drv.h| 19 +- drivers/gpu/drm/exynos/exynos_drm_dsi.c| 28 +-- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 24 +-- drivers/gpu/drm/exynos/exynos_drm_plane.c | 5 +- drivers/gpu/drm/exynos/exynos_drm_plane.h | 1 - drivers/gpu/drm/exynos/exynos_drm_vidi.c | 22 +-- drivers/gpu/drm/exynos/exynos_hdmi.c | 13 +- drivers/gpu/drm/exynos/exynos_mixer.c | 76 --- drivers/gpu/drm/exynos/regs-mixer.h| 7 +- include/video/exynos5433_decon.h | 1 + 15 files changed, 195 insertions(+), 302 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
Hi Dave, 2017년 04월 19일 08:35에 Dave Airlie 이(가) 쓴 글: > On 18 April 2017 at 12:05, Inki Daewrote: >> Hi Dave, >> >>Some improvements, fixups and cleanups to Exynos DRM. >> >>Ps. this pull-reuqest includes a merge tag from Krzysztof Kozlowski >>who is a Exynos SoC maintainer, which includes dt patches because >>these should be merged together with below one, >> drm/exynos: dsi: Fix the parse_dt function >> >>Please kindly let me know if there is any problem. > > Hi Inki, > > We closed the merge window at -rc6 for this release, due to some push > back from Linus, > > It was mentioned in a few mails on dri-devel, so I'm going to have to > leave this pull req > until the next merge, unless there is something in here that will break badly. Sorry for late. I was in a hurry but some review had been delayed. There is one patch which should be merged with Krzysztof's tree. Without this patch dt binding of Exynos drm will be broken. Almost patches of exynos-drm-next branch are fixup and cleanup so I will request pull to -fixes, maybe v4.12-rc1 in proper time again. Thanks, Inki Dae > > Dave. > > > ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
On Tue, Apr 18, 2017 at 4:30 AM, Inki Daewrote: > > > 2017년 04월 18일 11:21에 Andi Shyti 이(가) 쓴 글: >> Hi Inki, >> >>> Andi Shyti (2): >>> arm64: dts: exynos: Enable ir-spi in the TM2 and TM2E boards >>> arm64: dts: exynos: Add stmfts touchscreen node for TM2 and TM2E >> >> weren't these patches taken already by Krzysztof? They are >> already in -next > > I know a merge tag would make one not to be merged if other is already merged. Yes, it is expected. They come from merging my branch as we requested. The commits are exactly the same as in my tree (same SHA) so everything will end up fine. The only thing here we missed here is merging the Hoegeun's patches for arm. But well... it happens. Best regards, Krzysztof ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
Hi Inki, > Andi Shyti (2): > arm64: dts: exynos: Enable ir-spi in the TM2 and TM2E boards > arm64: dts: exynos: Add stmfts touchscreen node for TM2 and TM2E weren't these patches taken already by Krzysztof? They are already in -next Andi ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
On 18 April 2017 at 12:05, Inki Daewrote: > Hi Dave, > >Some improvements, fixups and cleanups to Exynos DRM. > >Ps. this pull-reuqest includes a merge tag from Krzysztof Kozlowski >who is a Exynos SoC maintainer, which includes dt patches because >these should be merged together with below one, > drm/exynos: dsi: Fix the parse_dt function > >Please kindly let me know if there is any problem. Hi Inki, We closed the merge window at -rc6 for this release, due to some push back from Linus, It was mentioned in a few mails on dri-devel, so I'm going to have to leave this pull req until the next merge, unless there is something in here that will break badly. Dave. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
2017년 04월 18일 11:21에 Andi Shyti 이(가) 쓴 글: > Hi Inki, > >> Andi Shyti (2): >> arm64: dts: exynos: Enable ir-spi in the TM2 and TM2E boards >> arm64: dts: exynos: Add stmfts touchscreen node for TM2 and TM2E > > weren't these patches taken already by Krzysztof? They are > already in -next I know a merge tag would make one not to be merged if other is already merged. Thanks, Inki Dae > > Andi > -- > 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 > > > . > ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
2017년 04월 18일 11:05에 Inki Dae 이(가) 쓴 글: > Hi Dave, > >Some improvements, fixups and cleanups to Exynos DRM. > >Ps. this pull-reuqest includes a merge tag from Krzysztof Kozlowski >who is a Exynos SoC maintainer, which includes dt patches because >these should be merged together with below one, > drm/exynos: dsi: Fix the parse_dt function > >Please kindly let me know if there is any problem. > > Thanks, > Inki Dae > > The following changes since commit ab6eb211b07a42a6346e284056422fd9a8576a99: > > Merge tag 'drm/panel/for-4.12-rc1' of > git://anongit.freedesktop.org/tegra/linux into drm-next (2017-04-13 06:17:40 > +1000) I'm sorry. I missed to put a tag name here. Below is a merge tag. git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v4.12 Thanks, Inki Dae > > are available in the git repository at: > > > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos > exynos-drm-next > > for you to fetch changes up to ad1a14690ae7114e5230deba27cdbbe42c69a813: > > drm/exynos/decon5433: remove useless check (2017-04-18 10:28:50 +0900) > > > Summary: > - Fix dt binding of MIPI-DSI driver > - Rework vblank handling > . This patch series adds frame counter callback and removes > unnecessary pipe relevnt fields and simplifies event handling. > - Implement and fix sw-trigger relevant code > . This patch moves TE relevant code from Panel and HDMI to DECON driver > to fix a race between interrupt handlers and DECON disable, > and to fix timeout issue at wait-for-vblank. > . It removes unnecessary flags and check code specific to Exynos driver. > > > Andi Shyti (2): > arm64: dts: exynos: Enable ir-spi in the TM2 and TM2E boards > arm64: dts: exynos: Add stmfts touchscreen node for TM2 and TM2E > > Andrzej Hajda (21): > drm/exynos: simplify completion event handling > drm/exynos/decon5433: implement frame counter > drm/exynos: kill exynos_drm_crtc::pipe > drm/exynos: kill exynos_drm_private::pipe > drm/exynos: set plane possible_crtcs in exynos_plane_init > drm/exynos: kill pipe field from drivers contexts > drm/exynos: kill mode_set_nofb callback > drm/exynos/decon5433: kill DECON_UPDATE workaround > drm/exynos/decon5433: kill BIT_IRQS_ENABLED > drm/exynos/decon5433: simplify shadow protect code > drm/exynos/hdmi: fix pipeline disable order > drm/exynos/dsi: fix bridge_node DT parsing > drm/exynos/decon5433: always do sw-trigger when vblanks enabled > dt-bindings: exynos5433-decon: fix interrupts bindings > dt-bindings: exynos5433-decon: add TE interrupt binding > drm/exynos/decon5433: move TE handling to DECON > drm/exynos/decon5433: kill BIT_IRQS_ENABLED flag > drm/exynos/decon5433: kill BIT_CLKS_ENABLED flag > drm/exynos/decon5433: kill BIT_WIN_UPDATED flag > drm/exynos/decon5433: kill BIT_SUSPENDED flag > drm/exynos/decon5433: remove useless check > > Daniel Vetter (1): > drm/exynos: Merge pre/postclose hooks > > Hoegeun Kwon (2): > arm64: dts: exynos: Add the burst and esc clock frequency properties to > DSI node > drm/exynos: dsi: Fix the parse_dt function > > Hyungwon Hwang (1): > arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board > > Inki Dae (2): > Merge tag 'samsung-dt64-clock-dsi-property-4.12' of > gitolite.kernel.org:/.../krzk/linux into exynos-drm-next > drm/exynos: clean up description of exynos_drm_crtc > > Tobias Jakobi (2): > drm/exynos: mixer: simplify mixer_cfg_rgb_fmt() > drm/exynos: mixer: document YCbCr magic numbers > > .../bindings/display/exynos/exynos5433-decon.txt | 13 +- > .../boot/dts/exynos/exynos5433-tm2-common.dtsi | 43 +++- > arch/arm64/boot/dts/exynos/exynos5433-tm2.dts | 17 ++ > arch/arm64/boot/dts/exynos/exynos5433-tm2e.dts | 7 + > drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 218 > + > drivers/gpu/drm/exynos/exynos7_drm_decon.c | 19 +- > drivers/gpu/drm/exynos/exynos_drm_crtc.c | 50 +++-- > drivers/gpu/drm/exynos/exynos_drm_crtc.h | 1 - > drivers/gpu/drm/exynos/exynos_drm_drv.c| 8 +- > drivers/gpu/drm/exynos/exynos_drm_drv.h| 19 +- > drivers/gpu/drm/exynos/exynos_drm_dsi.c| 24 +-- > drivers/gpu/drm/exynos/exynos_drm_fimd.c | 24 +-- > drivers/gpu/drm/exynos/exynos_drm_plane.c | 5 +- > drivers/gpu/drm/exynos/exynos_drm_plane.h | 1 - > drivers/gpu/drm/exynos/exynos_drm_vidi.c | 22 +-- > drivers/gpu/drm/exynos/exynos_hdmi.c | 13 +- > drivers/gpu/drm/exynos/exynos_mixer.c | 76 --- > drivers/gpu/drm/exynos/regs-mixer.h
[GIT PULL] exynos-drm-next
Hi Dave, Some improvements, fixups and cleanups to Exynos DRM. Ps. this pull-reuqest includes a merge tag from Krzysztof Kozlowski who is a Exynos SoC maintainer, which includes dt patches because these should be merged together with below one, drm/exynos: dsi: Fix the parse_dt function Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit ab6eb211b07a42a6346e284056422fd9a8576a99: Merge tag 'drm/panel/for-4.12-rc1' of git://anongit.freedesktop.org/tegra/linux into drm-next (2017-04-13 06:17:40 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to ad1a14690ae7114e5230deba27cdbbe42c69a813: drm/exynos/decon5433: remove useless check (2017-04-18 10:28:50 +0900) Summary: - Fix dt binding of MIPI-DSI driver - Rework vblank handling . This patch series adds frame counter callback and removes unnecessary pipe relevnt fields and simplifies event handling. - Implement and fix sw-trigger relevant code . This patch moves TE relevant code from Panel and HDMI to DECON driver to fix a race between interrupt handlers and DECON disable, and to fix timeout issue at wait-for-vblank. . It removes unnecessary flags and check code specific to Exynos driver. Andi Shyti (2): arm64: dts: exynos: Enable ir-spi in the TM2 and TM2E boards arm64: dts: exynos: Add stmfts touchscreen node for TM2 and TM2E Andrzej Hajda (21): drm/exynos: simplify completion event handling drm/exynos/decon5433: implement frame counter drm/exynos: kill exynos_drm_crtc::pipe drm/exynos: kill exynos_drm_private::pipe drm/exynos: set plane possible_crtcs in exynos_plane_init drm/exynos: kill pipe field from drivers contexts drm/exynos: kill mode_set_nofb callback drm/exynos/decon5433: kill DECON_UPDATE workaround drm/exynos/decon5433: kill BIT_IRQS_ENABLED drm/exynos/decon5433: simplify shadow protect code drm/exynos/hdmi: fix pipeline disable order drm/exynos/dsi: fix bridge_node DT parsing drm/exynos/decon5433: always do sw-trigger when vblanks enabled dt-bindings: exynos5433-decon: fix interrupts bindings dt-bindings: exynos5433-decon: add TE interrupt binding drm/exynos/decon5433: move TE handling to DECON drm/exynos/decon5433: kill BIT_IRQS_ENABLED flag drm/exynos/decon5433: kill BIT_CLKS_ENABLED flag drm/exynos/decon5433: kill BIT_WIN_UPDATED flag drm/exynos/decon5433: kill BIT_SUSPENDED flag drm/exynos/decon5433: remove useless check Daniel Vetter (1): drm/exynos: Merge pre/postclose hooks Hoegeun Kwon (2): arm64: dts: exynos: Add the burst and esc clock frequency properties to DSI node drm/exynos: dsi: Fix the parse_dt function Hyungwon Hwang (1): arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board Inki Dae (2): Merge tag 'samsung-dt64-clock-dsi-property-4.12' of gitolite.kernel.org:/.../krzk/linux into exynos-drm-next drm/exynos: clean up description of exynos_drm_crtc Tobias Jakobi (2): drm/exynos: mixer: simplify mixer_cfg_rgb_fmt() drm/exynos: mixer: document YCbCr magic numbers .../bindings/display/exynos/exynos5433-decon.txt | 13 +- .../boot/dts/exynos/exynos5433-tm2-common.dtsi | 43 +++- arch/arm64/boot/dts/exynos/exynos5433-tm2.dts | 17 ++ arch/arm64/boot/dts/exynos/exynos5433-tm2e.dts | 7 + drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 218 + drivers/gpu/drm/exynos/exynos7_drm_decon.c | 19 +- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 50 +++-- drivers/gpu/drm/exynos/exynos_drm_crtc.h | 1 - drivers/gpu/drm/exynos/exynos_drm_drv.c| 8 +- drivers/gpu/drm/exynos/exynos_drm_drv.h| 19 +- drivers/gpu/drm/exynos/exynos_drm_dsi.c| 24 +-- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 24 +-- drivers/gpu/drm/exynos/exynos_drm_plane.c | 5 +- drivers/gpu/drm/exynos/exynos_drm_plane.h | 1 - drivers/gpu/drm/exynos/exynos_drm_vidi.c | 22 +-- drivers/gpu/drm/exynos/exynos_hdmi.c | 13 +- drivers/gpu/drm/exynos/exynos_mixer.c | 76 --- drivers/gpu/drm/exynos/regs-mixer.h| 7 +- include/video/exynos5433_decon.h | 1 + 19 files changed, 256 insertions(+), 312 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Summary: - Add UHD support on TM2/TM2E boards. . adding interlace mode support and 297MHz pixel clock support for UHD mode, setting sysreg register in case of HW trigger mode, and adding SiI8620 MHL bridge device support. - Fix trigger mode issue on Rinato board. . On Rinato board, HW trigger mode doesn't work so fix it. - Some fixup and cleanup. There is one patch series[1] being reviewed yet but seems more review is required. Please kindly let me know if there is any problem. [1] http://www.spinics.net/lists/devicetree/msg162681.html Thanks, Inki Dae. The following changes since commit 99743ae4c5f52f8f8ceb17783056fcc9b4f8b64c: Merge branch 'drm-etnaviv-next' of https://git.pengutronix.de/git/lst/linux into drm-next (2017-02-03 05:41:58 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to 7ff093d09f8f027c317282e18b566473df53e8a1: drm/exynos: fimd: Do not use HW trigger for exynos3250 (2017-02-07 13:54:01 +0900) Andrzej Hajda (7): drm/exynos/decon5433: configure sysreg in case of hardware trigger drm/exynos/hdmi: add 297MHz pixel clock support drm/exynos/hdmi: fix VSI infoframe registers drm/exynos/hdmi: fix PLL for 27MHz settings drm/exynos/decon5433: add support for interlace modes drm/exynos/decon5433: signal vblank only on odd fields drm/exynos/hdmi: add bridge support Hoegeun Kwon (1): drm/exynos: fimd: Do not use HW trigger for exynos3250 Tobias Jakobi (1): drm/exynos: g2d: change platform driver name to 'exynos-drm-g2d' drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 92 +-- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 2 - drivers/gpu/drm/exynos/exynos_drm_g2d.c | 2 +- drivers/gpu/drm/exynos/exynos_hdmi.c | 80 ++- include/video/exynos5433_decon.h | 2 + 5 files changed, 137 insertions(+), 41 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [GIT PULL] exynos-drm-next
Finally, Thierry gave comment and he wants the panel driver not to be merged yet. So removed the patch from exynos-drm-next tree. Thanks, Inki Dae 2017년 01월 31일 09:46에 Inki Dae 이(가) 쓴 글: > Hi Dave, > >adding runtime PM support to MIC driver, and including some >cleanups - especially using atomic helper functions >instead of specific ones - and fixups. > >In addition, it includes S6E3HA2 panel driver and its support. >The panel driver should go to mainline by Thierry. >However, there is no comment from him. Seems he is busy maybe. >I think we had review enough so I picked it up. > >And we have one patch series for UHD support which is under the review. >So I plan to have a pull request again as soon as finising the review. > >Please kindly let me know if there is any problem. > > Thanks, > Inki Dae > > The following changes since commit a5b2b6ebf34b20e70a2bdb5214c371744e7fa260: > > drm/sti: Fix compilation failure for drm_framebuffer.pixel_format > (2017-01-27 12:54:15 +1000) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git > exynos-drm-next > > for you to fetch changes up to 2473244a04edf5480770bd840c38546b800f839d: > > drm/panel: Add support for S6E3HA2 panel driver on TM2 board (2017-01-31 > 09:02:21 +0900) > > > Dan Carpenter (1): > drm/exynos: fix a timeout loop > > Daniel Vetter (1): > drm/exynos: Stop using drm_framebuffer_unregister_private > > Hoegeun Kwon (3): > drm/exynos: mic: Add mode_set callback function > drm/exynos: mic: Fix parse_dt function > drm/panel: Add support for S6E3HA2 panel driver on TM2 board > > Inki Dae (2): > drm/exynos: remove unnecessary codes > drm/exynos: use atomic helper commit > > Joonyoung Shim (1): > drm/exynos: g2d: prevent integer overflow in > > Marek Szyprowski (1): > drm/exynos: mic: Add runtime PM support > > drivers/gpu/drm/exynos/exynos_drm_crtc.c | 28 +- > drivers/gpu/drm/exynos/exynos_drm_crtc.h | 4 - > drivers/gpu/drm/exynos/exynos_drm_drv.c | 114 > drivers/gpu/drm/exynos/exynos_drm_fb.c| 32 +- > drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 4 +- > drivers/gpu/drm/exynos/exynos_drm_g2d.c | 17 +- > drivers/gpu/drm/exynos/exynos_drm_mic.c | 126 +++-- > drivers/gpu/drm/exynos/exynos_mixer.c | 2 +- > drivers/gpu/drm/panel/Kconfig | 6 + > drivers/gpu/drm/panel/Makefile| 1 + > drivers/gpu/drm/panel/panel-samsung-s6e3ha2.c | 754 > ++ > 11 files changed, 892 insertions(+), 196 deletions(-) > create mode 100644 drivers/gpu/drm/panel/panel-samsung-s6e3ha2.c > ___ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel > ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, adding runtime PM support to MIC driver, and including some cleanups - especially using atomic helper functions instead of specific ones - and fixups. In addition, it includes S6E3HA2 panel driver and its support. The panel driver should go to mainline by Thierry. However, there is no comment from him. Seems he is busy maybe. I think we had review enough so I picked it up. And we have one patch series for UHD support which is under the review. So I plan to have a pull request again as soon as finising the review. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit a5b2b6ebf34b20e70a2bdb5214c371744e7fa260: drm/sti: Fix compilation failure for drm_framebuffer.pixel_format (2017-01-27 12:54:15 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to 2473244a04edf5480770bd840c38546b800f839d: drm/panel: Add support for S6E3HA2 panel driver on TM2 board (2017-01-31 09:02:21 +0900) Dan Carpenter (1): drm/exynos: fix a timeout loop Daniel Vetter (1): drm/exynos: Stop using drm_framebuffer_unregister_private Hoegeun Kwon (3): drm/exynos: mic: Add mode_set callback function drm/exynos: mic: Fix parse_dt function drm/panel: Add support for S6E3HA2 panel driver on TM2 board Inki Dae (2): drm/exynos: remove unnecessary codes drm/exynos: use atomic helper commit Joonyoung Shim (1): drm/exynos: g2d: prevent integer overflow in Marek Szyprowski (1): drm/exynos: mic: Add runtime PM support drivers/gpu/drm/exynos/exynos_drm_crtc.c | 28 +- drivers/gpu/drm/exynos/exynos_drm_crtc.h | 4 - drivers/gpu/drm/exynos/exynos_drm_drv.c | 114 drivers/gpu/drm/exynos/exynos_drm_fb.c| 32 +- drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 4 +- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 17 +- drivers/gpu/drm/exynos/exynos_drm_mic.c | 126 +++-- drivers/gpu/drm/exynos/exynos_mixer.c | 2 +- drivers/gpu/drm/panel/Kconfig | 6 + drivers/gpu/drm/panel/Makefile| 1 + drivers/gpu/drm/panel/panel-samsung-s6e3ha2.c | 754 ++ 11 files changed, 892 insertions(+), 196 deletions(-) create mode 100644 drivers/gpu/drm/panel/panel-samsung-s6e3ha2.c ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[GIT PULL] exynos-drm-next
Hi Dave, Sorry for late. Just refactoring HDMI driver by using infoframe helper function, fixing GSC Kconfig dependency issue and including trivial cleanups. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit f03ee46be9401e3434f52bb15e92d1e640f76438: Backmerge tag 'v4.9-rc8' into drm-next (2016-12-05 17:11:48 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to 4e775249269213a2d8825d7f878e42e99a2b6080: drm/exynos: Use VIDEO_SAMSUNG_EXYNOS_GSC=n as GSC Kconfig dependency (2016-12-05 22:08:59 +0900) Andrzej Hajda (1): drm/exynos/hdmi: refactor infoframe code Colin Ian King (1): drm/exynos: gsc: fix spelling mistakes Javier Martinez Canillas (1): drm/exynos: Use VIDEO_SAMSUNG_EXYNOS_GSC=n as GSC Kconfig dependency Shuah Khan (1): exynos-drm: Fix error messages to print flags and size drivers/gpu/drm/exynos/Kconfig | 2 +- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 2 +- drivers/gpu/drm/exynos/exynos_drm_gem.c | 4 +- drivers/gpu/drm/exynos/exynos_drm_gsc.c | 2 +- drivers/gpu/drm/exynos/exynos_hdmi.c | 141 +-- drivers/gpu/drm/exynos/regs-hdmi.h | 2 + 6 files changed, 47 insertions(+), 106 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave, This pull request includes, - Code refactoring on HDMI DDC and PHY. - Regression fixup on deadlock issue with G2D pm integration. - Fixup on page fault issue with wait_for_vblank mechianism specific to Exynos drm. - And some cleanups. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 28a396545a2a5fbdffb2b661ed6c9b6820e28772: Merge branch 'drm-next-4.9' of git://people.freedesktop.org/~agd5f/linux into drm-next (2016-09-30 13:21:02 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to c0462796464219fed0fbc1e8b2b93eb6751769f5: drm/exynos: g2d: simplify g2d_free_runqueue_node() (2016-10-01 00:39:42 +0900) Andrzej Hajda (4): drm/exynos/vidi: use timer for vblanks instead of sleeping worker drm/exynos: fix pending update handling drm/exynos/fimd: add clock rate checking drm/exynos: use drm core to handle page-flip event Baoyou Xie (1): drm/exynos: mark exynos_dp_crtc_clock_enable() static Milo Kim (3): gpu: drm: exynos_hdmi: Move DDC logic into single function gpu: drm: exynos_hdmi: Move PHY logic into single function gpu: drm: exynos_hdmi: Remove duplicate initialization of regulator bulk consumer Tobias Jakobi (9): drm/exynos: mixer: convert booleans to flags in mixer context drm/exynos: mixer: simplify loop in vp_win_reset() drm/exynos: g2d: beautify probing message Revert "drm/exynos: g2d: fix system and runtime pm integration" drm/exynos: g2d: move PM management to runqueue worker drm/exynos: g2d: remove runqueue nodes in g2d_{close,remove}() drm/exynos: g2d: wait for engine to finish drm/exynos: g2d: use autosuspend mode for PM runtime drm/exynos: g2d: simplify g2d_free_runqueue_node() drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 11 -- drivers/gpu/drm/exynos/exynos7_drm_decon.c|9 - drivers/gpu/drm/exynos/exynos_dp.c|2 +- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 58 +++--- drivers/gpu/drm/exynos/exynos_drm_drv.c | 44 + drivers/gpu/drm/exynos/exynos_drm_drv.h |4 - drivers/gpu/drm/exynos/exynos_drm_fimd.c | 54 +++--- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 239 +++-- drivers/gpu/drm/exynos/exynos_drm_plane.c |1 - drivers/gpu/drm/exynos/exynos_drm_vidi.c | 76 +++- drivers/gpu/drm/exynos/exynos_hdmi.c | 112 ++-- drivers/gpu/drm/exynos/exynos_mixer.c | 68 --- 12 files changed, 352 insertions(+), 326 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave, This pull request adds to the rework patch series for IOMMU integration to support ARM64bit architecture with DMA-IOMMU glue code. With this patch series, Exynos DRM works well on Exynos5433 SoC with IOMMU enabled. Ps. current implementation has conditional codes in exynos_drm_iommu.h for ARM32/64 supports because these two architectures are not compatible yet so the conditional codes will be removed later with architectures unified. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 5dd0775e502b26b44e5bcb5f504a977a565f2f3e: Merge tag 'asoc-hdmi-codec-pdata' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into drm-next (2016-07-05 09:57:23 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to 197adf0b7e419247a6e54d05d0d334e07e9e4c33: drm/exynos: iommu: add support for ARM64 specific code for IOMMU glue (2016-07-13 23:06:07 +0900) Marek Szyprowski (5): drm/exynos: iommu: move dma_params configuration code to separate functions drm/exynos: iommu: add a check if all sub-devices have iommu controller drm/exynos: iommu: remove unused entries from exynos_drm_private strcuture drm/exynos: iommu: move ARM specific code to exynos_drm_iommu.h drm/exynos: iommu: add support for ARM64 specific code for IOMMU glue drivers/gpu/drm/exynos/Kconfig|2 +- drivers/gpu/drm/exynos/exynos_drm_drv.c |7 +-- drivers/gpu/drm/exynos/exynos_drm_drv.h |2 - drivers/gpu/drm/exynos/exynos_drm_iommu.c | 77 +++- drivers/gpu/drm/exynos/exynos_drm_iommu.h | 91 + 5 files changed, 126 insertions(+), 53 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave, This pull request includes some code refactoring, Exynos5433 and HW trigger mode supports. Summary: - Support for pipeline clock between KMS drivers. . Exynos SoC is required to control clocks across KMS drivers according to Exynos SoC version. So this patch refactos some relevant codes and provides generic solution for it. - Add Exynos5433 SoC support to HDMI parts - HDMI and DECON-TV. - Add HW trigger mode support to CRTC drivers. . In case of using i80 Panel, some Exynos SoC supports HW trigger mode so this patch makes trigger mode - HW or SW trigger - to be set according to SoC version properly. - And some cleanups and regression fixups. Please, kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit b89359bdf0f1e95a4c5f92300594ba9dde323fc4: Merge branch 'for-next' of http://git.agner.ch/git/linux-drm-fsl-dcu into drm-next (2016-04-29 14:57:51 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to b5bf0f1ea3658254bd72ef64abc97786e8a32255: drm/exynos: clean up register definions for fimd and decon (2016-04-30 11:34:14 +0900) Andrzej Hajda (23): drm/exynos: fix adjusted_mode pointer in exynos_plane_mode_set drm/exynos: build fbdev code conditionally drm/exynos/hdmi: clock code re-factoring drm/exynos/hdmi: constify global variables drm/exynos/hdmi: use array specifier for HDMI-PHY configurations drm/exynos/hdmi: code cleanup drm/exynos/hdmi: stop programming registers with default values dt-bindings: exynos_hdmi: add bindings for Exynos5433 variant drm/exynos/hdmi: add Exynos5433 support dt-bindings: video: add PCLK clock entry to exynos5433-decon dt-bindings: video: exynos5433-decon: add bindings for DECON-TV drm/exynos/hdmi: fix PHY configuration sequence drm/exynos/hdmi: add PHY power off signal handling drm/exynos/hdmi: add core reset code drm/exynos/hdmi: remove registry dump drm/exynos/decon5433: fix DECON standalone update drm/exynos/decon5433: reset decon on start drm/exynos/decon5433: do not protect window in plane disable drm/exynos: add helper to get crtc from pipe drm/exynos: add support for pipeline clock to the framework drm/exynos/decon5433: enable HDMI-PHY before configuring DECON drm/exynos/mixer: enable HDMI-PHY before configuring MIXER drm/exynos: convert clock_enable crtc callback to pipeline clock Arnd Bergmann (1): drm/exynos: fix error handling in exynos_drm_subdrv_open Dan Carpenter (2): drm/exynos: mic: fix an error code drm/exynos: fix a warning message Inki Dae (4): drm/exynos: clean up wait_for_vblank drm/exynos: fimd: add HW trigger support drm/exynos: decon: clean up interface type drm/exynos: clean up register definions for fimd and decon Javier Martinez Canillas (1): drm/exynos: Use VIDEO_SAMSUNG_S5P_G2D=n as G2D Kconfig dependency Marek Szyprowski (8): drm/exynos: fimd: fix broken dp_clock control drm/exynos: exynos5433_decon: use generic of_device_get_match_data helper drm/exynos: dsi: use generic of_device_get_match_data helper drm/exynos: fimd: use generic of_device_get_match_data helper drm/exynos: rotator: use generic of_device_get_match_data helper drm/exynos: hdmi: use generic of_device_get_match_data helper drm/exynos: mixer: remove support for non-dt platforms drm/exynos: mixer: use generic of_device_get_match_data helper .../bindings/display/exynos/exynos5433-decon.txt |5 +- .../bindings/display/exynos/exynos_hdmi.txt| 27 +- drivers/gpu/drm/exynos/Kconfig |2 +- drivers/gpu/drm/exynos/Makefile|6 +- drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 86 +-- drivers/gpu/drm/exynos/exynos7_drm_decon.c |1 - drivers/gpu/drm/exynos/exynos_dp.c |9 +- drivers/gpu/drm/exynos/exynos_drm_core.c |2 +- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 10 +- drivers/gpu/drm/exynos/exynos_drm_drv.h| 28 +- drivers/gpu/drm/exynos/exynos_drm_dsi.c| 27 +- drivers/gpu/drm/exynos/exynos_drm_fb.c | 11 - drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 11 + drivers/gpu/drm/exynos/exynos_drm_fbdev.h | 23 +- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 99 ++- drivers/gpu/drm/exynos/exynos_drm_mic.c|3 +- drivers/gpu/drm/exynos/exynos_drm_plane.c | 12 +- drivers/gpu/drm/exynos/exynos_drm_rotator.c| 11 +- drivers/gpu/drm/exynos/exynos_hdmi.c
[GIT PULL] exynos-drm-next for 4.6
Hi Dave, This pull request adds DRM_EXYNOS_GEM_MAP ioctl interface for the use of render node. This interface had been tried to mainline but tackled by Daniel Stone because there was no non-libdrm user, http://www.spinics.net/lists/dri-devel/msg93243.html We have already added the non-libdrm user support like below, https://review.tizen.org/git/?p=platform/adaptation/samsung_exynos/libtbm-exynos.git;a=commit;h=773b66e9f51db46745508c739c71b3f8a4e35a30 And that has been tested enough. For more information about libtbm, this module is a buffer manager for Tizen platform. All applications - who want to use dma buffer - use this module to allocate dma buffer through DRM GEM. Kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 550e3b23a53c88adfa46e64f9d442743e65d47da: Merge branch 'drm-next-4.6' of git://people.freedesktop.org/~agd5f/linux into drm-next (2016-03-08 10:51:51 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to 6564c65f3a2b75832957e53bcc3c6066d1d73487: drm/exynos: add DRM_EXYNOS_GEM_MAP ioctl (2016-03-13 14:54:03 +0900) Joonyoung Shim (1): drm/exynos: add DRM_EXYNOS_GEM_MAP ioctl drivers/gpu/drm/exynos/exynos_drm_drv.c |2 ++ drivers/gpu/drm/exynos/exynos_drm_gem.c |9 + drivers/gpu/drm/exynos/exynos_drm_gem.h |4 include/uapi/drm/exynos_drm.h | 17 - 4 files changed, 31 insertions(+), 1 deletion(-)
[GIT PULL] exynos-drm-next for 4.6
Hi Dave, This pull request includes Exynos5420/5422 SoC support, fixups and cleanups. Summary: - Add Exynos5420 SoC support to FIMD driver. . This patch makes MIC(Mobile Image Compressor) IP to be bypassed in default in case of Exynos5420 and later. The Display pipe line configuraion for Exynos DRM driver will be considered through of graph concept later. - Add Exynos5422 SoC support to MIPI-DSI driver. . Exynos5422 SoC is similar to Exynos5433 SoC but software reset is different each other so this patch consideres the difference. - Get more precise clock divider value of FIMD controller. . This patch changes DIV_ROUND_CLOSEST macro to be used instead of DIV_ROUND_UP. - Refactor Exynos DRM device and driver registeration. . This patch makes Exynos DRM driver to be easy-to-read and at the same time, cleans it up by removing #ifdef ~ #endif things. - Configure DMA-mapping address space common to Exynos DRM devices in more generic without any hacks. - some fixups and cleanups. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit efcebcf983abf70a15958b9fb5237b1c38060d95: Merge tag 'drm-intel-next-2016-02-14' of git://anongit.freedesktop.org/drm-intel into drm-next (2016-03-01 13:06:44 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to 6c81e96d4bd10617b856ce3cb5fa09337871bfdf: drm/exynos/dsi: use core helper to create DSI packet (2016-03-02 00:21:37 +0900) Andrzej Hajda (11): drm/exynos/decon: fix disable clocks order drm/exynos/dsi: replace registry access macros with functions drm/exynos/dsi: constify read only structures drm/exynos/hdmi: remove unused variable drm/exynos/decon: make irq handler static drm/exynos: remove incorrect ccflags from Makefile drm/exynos: remove struct exynos_drm_panel_info drm/exynos/fimc: remove unused camera interface polarization code drm/exynos: remove platform data structures and include/drm/exynos_drm.h drm/exynos: use arch independent types in uapi header drm/exynos/dsi: use core helper to create DSI packet Chanho Park (3): drm/exynos: support exynos5422 mipi-dsi drm/exynos: use DIV_ROUND_CLOSEST to find the closest div drm/exynos: add exynos5420 support for fimd Joonyoung Shim (1): drm/exynos: depend on ARCH_EXYNOS for DRM_EXYNOS Marek Szyprowski (11): drm/exynos: ipp: fix incorrect format specifiers in debug messages drm/exynos: fix types for compilation on 64bit architectures drm/exynos: mic: use devm_clk interface drm/exynos: mic: convert to component framework drm/exynos: mic: make all functions static drm/exynos: dsi: restore support for drm bridge drm/exynos: exynos5433_decon: fix wrong state assignment in decon_enable drm/exynos: exynos5433_decon: fix wrong state in decon_vblank_enable drm/exynos: fix incorrect cpu address for dma_mmap_attrs() drm/exynos: refactor driver and device registration code drm/exynos: use real device for DMA-mapping operations .../bindings/display/exynos/exynos_dsim.txt|1 + .../bindings/display/exynos/samsung-fimd.txt |3 +- drivers/gpu/drm/exynos/Kconfig |2 +- drivers/gpu/drm/exynos/Makefile|1 - drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 10 +- drivers/gpu/drm/exynos/exynos7_drm_decon.c |1 - drivers/gpu/drm/exynos/exynos_dp_core.c|7 +- drivers/gpu/drm/exynos/exynos_dp_core.h|4 +- drivers/gpu/drm/exynos/exynos_drm_drv.c| 265 +++- drivers/gpu/drm/exynos/exynos_drm_drv.h| 10 +- drivers/gpu/drm/exynos/exynos_drm_dsi.c| 235 + drivers/gpu/drm/exynos/exynos_drm_fbdev.c |2 +- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 30 +-- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 34 ++- drivers/gpu/drm/exynos/exynos_drm_g2d.c| 12 +- drivers/gpu/drm/exynos/exynos_drm_gem.c| 16 +- drivers/gpu/drm/exynos/exynos_drm_gsc.c|2 +- drivers/gpu/drm/exynos/exynos_drm_iommu.c | 39 +-- drivers/gpu/drm/exynos/exynos_drm_iommu.h |4 +- drivers/gpu/drm/exynos/exynos_drm_ipp.c| 32 +-- drivers/gpu/drm/exynos/exynos_drm_mic.c| 72 +++--- drivers/gpu/drm/exynos/exynos_drm_rotator.c|3 +- drivers/gpu/drm/exynos/exynos_drm_vidi.c |8 +- drivers/gpu/drm/exynos/exynos_hdmi.c |2 - include/drm/exynos_drm.h | 101 include/uapi/drm/exynos_drm.h | 26 +- 26
[GIT PULL] exynos-drm-next
Hi Dave, This pull request includes runtime pm support, of_graph based dt binding support for DP(Display Port) panel and cleanups for Exynos DRM IPP enhancement. Summary: - Support runtime pm . In case of most ARM SoC, each IP has each power domain which should be controlled by each IP driver using runtime pm interface. So this patch series makes each IP driver to control its own power domain when drm dpms is requested. - Support of_graph based dt binding for DP panel. . This patch series adds of_graph based dt binding for DP panel. And also it keeps backward compatibility. This includes dt binding patch so I got Acked-by from Krzysztof Kozlowski who is a Exynos SoC maintainer and from Rob Herring who is a device tree maintainer. - Cleanup for Exynos DRM IPP enhancement. . This patch series is a first step for enhancing existing IPP framework which will integrate existing IPP functions with DRM KMS part so that these can be transparent to userspace. For other portion of the patch series, we will have more times for the review. Plese, kindly let know if there is any problem. Thanks, Inki Dae The following changes since commit 663a233eef643b38f36c05535cb5c9a4972edcc1: Merge branch 'drm-header-fixes' of https://github.com/GabrielL/linux into drm-next (2015-12-11 13:46:05 +1000) are available in the git repository at: gitolite.kernel.org:/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to 9bac40cf28c9318f0b3eb6c81ce35f32581ef7b4: drm/exynos: gem: remove old unused prototypes (2015-12-13 22:22:59 +0900) Andrzej Hajda (1): drm/exynos: simplify sleep PM ops Gustavo Padovan (7): drm/exynos: do not start enabling DP at bind() phase drm/exynos: add pm_runtime to DP drm/exynos: add pm_runtime to HDMI drm/exynos: add pm_runtime to Mixer drm/exynos: add pm_runtime to FIMD drm/exynos: add pm_runtime to DECON 5433 drm/exynos: add pm_runtime to DECON 7 Inki Dae (5): drm/exynos: dsi: add runtime pm support drm/exynos: dsi: modify a error type when getting a node failed drm/exynos: decon: remove unused variables drm/exynos: dp: add of_graph dt binding support for panel dt-bindings: exynos-dp: update ports node binding for panel Javier Martinez Canillas (1): ARM: dts: Use OF graph for DP to panel connection in exynos5800-peach-pi Marek Szyprowski (12): drm/exynos: rotator: convert to common clock framework drm/exynos: exynos7-decon: remove excessive check drm/exynos: move dma_addr attribute from exynos plane to exynos fb drm/exynos: introduce exynos_drm_plane_state structure drm/exynos: mixer: use crtc->state->adjusted_mode instead of crtc->mode drm/exynos: mixer: enable video overlay plane only when VP is available drm/exynos: introduce exynos_drm_plane_config structure drm/exynos: add generic check for plane state drm/exynos: mixer: use ratio precalculated in exynos_state drm/exynos: fix clipping when scaling is enabled drm/exynos: fimd: fix dma burst size setting for small plane size drm/exynos: gem: remove old unused prototypes Seung-Woo Kim (3): drm/exynos: gsc: prepare and unprepare gsc clock drm/exynos: gsc: fix wrong pm_runtime state drm/exynos: gsc: add device tree support and remove usage of static mappings .../bindings/display/exynos/exynos_dp.txt | 41 +++- .../devicetree/bindings/media/exynos5-gsc.txt | 4 + arch/arm/boot/dts/exynos5800-peach-pi.dts | 15 +- drivers/gpu/drm/exynos/Kconfig | 2 +- drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 104 ++--- drivers/gpu/drm/exynos/exynos7_drm_decon.c | 161 +++--- drivers/gpu/drm/exynos/exynos_dp_core.c| 179 --- drivers/gpu/drm/exynos/exynos_dp_core.h| 1 + drivers/gpu/drm/exynos/exynos_drm_drv.c| 76 +++ drivers/gpu/drm/exynos/exynos_drm_drv.h| 81 --- drivers/gpu/drm/exynos/exynos_drm_dsi.c| 151 +++-- drivers/gpu/drm/exynos/exynos_drm_fb.c | 16 +- drivers/gpu/drm/exynos/exynos_drm_fb.h | 3 +- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 142 +++- drivers/gpu/drm/exynos/exynos_drm_gem.h| 28 --- drivers/gpu/drm/exynos/exynos_drm_gsc.c| 35 ++- drivers/gpu/drm/exynos/exynos_drm_plane.c | 215 +++--- drivers/gpu/drm/exynos/exynos_drm_plane.h | 7 +- drivers/gpu/drm/exynos/exynos_drm_rotator.c| 4 +- drivers/gpu/drm/exynos/exynos_drm_vidi.c | 31 ++- drivers/gpu/drm/exynos/exynos_hdmi.c | 49 - drivers/gpu/drm/exynos/exynos_mixer.c | 239 +++--
[GIT PULL] exynos-drm-next
Hi Inki, On 3 November 2015 at 04:36, Inki Dae wrote: > 2015ë 10ì 28ì¼ 21:37ì Inki Dae ì´(ê°) ì´ ê¸: >> 2015ë 10ì 28ì¼ 20:52ì Daniel Stone ì´(ê°) ì´ ê¸: >>> Anyway, regardless of that, as far as I can tell, the Xorg driver uses >>> TBM to do buffer mapping, and the TBM backend uses DUMB_MAP rather >>> than the new call here. Is there something I'm missing? >> >> You are right. I found that the patch applied to the backend exists in local >> branch. >> I thought the patch exists already in tizen.org because we had already test. >> Anyway, the patch will be merged soon. > > We have merged the exynos specific map interface to real user like below, > > https://review.tizen.org/git/?p=platform/adaptation/samsung_exynos/libtbm-exynos4412.git;a=commit;h=32c862bf69d602a13bac127f3e15bc8ea15e4315 > > So please, feel free to review. I'd be happy for your reivew. :) > > Anyway, in Exynos case, we will use Tizen platform as a real user. > This means that all interfaces to be added or modified to -next will be > verified on Tizen platform. Thanks a lot for the patch. The note below still stands, but I have now have no objection to merging the patch. >>> (In any case, having separate-from-Tizen userspace graphics stack >>> repositories would be very welcome, I think: there are a huge number >>> of repositories for Tizen - something like six copies of libtbm alone >>> - and it is unclear how to build them on a generic userspace / if they >>> will actually build at all / if they will run on mainline kernels. >>> Having a separate tree will make it very clear to people how to get >>> things working on top of a mainline/staged-for-next kernel.) >> >> One libtbm is common library used by Tizen platform, which has Tizen >> standard API and >> the interfaces of the libtbm will never changed. Others are all backend >> libraries. >> In fact, Tizen supports various boards based on various SoC such as >> snapdragon, allwinner, >> spreadtrum and Exynos. Among them, only Exynos will run on mainline kernels >> as of now. Oh, sure - I just meant an easy way to get them to run on an existing userspace, without having to build a completely different distro from scratch; it seems quite involved to get the test system running. Cheers, Daniel
[GIT PULL] exynos-drm-next
Hi Daniel, 2015ë 10ì 28ì¼ 21:37ì Inki Dae ì´(ê°) ì´ ê¸: > Hi Daniel, > > 2015ë 10ì 28ì¼ 20:52ì Daniel Stone ì´(ê°) ì´ ê¸: >> Hi Inki, >> >> On 28 October 2015 at 11:16, Inki Dae wrote: >>> 2015ë 10ì 28ì¼ 20:00ì Daniel Stone ì´(ê°) ì´ ê¸: On 28 October 2015 at 10:58, Daniel Stone wrote: > Is there any open user we can review? For clarity, what I meant by these parts was: is there somewhere we can take TBM + Xorg/Wayland for Exynos hardware? Even better if it's able to run on commercially-available parts such as 5422/5800 (Chromebook 2, ODROID-XU3). As you know, it is quite >>> >>> Yes, you could get TBM + Xorg/Wayland for Exynos hardware - ODROID-XU3 >>> through below link, >>> https://review.tizen.org/git/ >>> >>> And below is Linux 4.0 kernel for ODROID-XU3/XU4. >>> >>> https://review.tizen.org/git/?p=platform/kernel/linux-exynos.git;a=shortlog;h=refs/heads/tizen >> >> Thanks very much for the pointer. I managed to find the exynos Xorg >> driver in use, but unfortunately the only tbm backend I could find is >> labelled for exynos4412. Is this backend also usable on 5xxx/XU3, or >> is that backend really only for Trats2, and the 5xxx backend is >> private? > > Prefix name may be strange but below libtbm backend is used for Trats2 and > Odoid-XU3/4. > Actually, changing the backend name to 'exynos' instead of 'exynos' would > be more reasonable. > > https://review.tizen.org/git/?p=platform/adaptation/samsung_exynos/libtbm-exynos4412.git;a=summary > >> >> Anyway, regardless of that, as far as I can tell, the Xorg driver uses >> TBM to do buffer mapping, and the TBM backend uses DUMB_MAP rather >> than the new call here. Is there something I'm missing? > > You are right. I found that the patch applied to the backend exists in local > branch. > I thought the patch exists already in tizen.org because we had already test. > Anyway, the patch will be merged soon. We have merged the exynos specific map interface to real user like below, https://review.tizen.org/git/?p=platform/adaptation/samsung_exynos/libtbm-exynos4412.git;a=commit;h=32c862bf69d602a13bac127f3e15bc8ea15e4315 So please, feel free to review. I'd be happy for your reivew. :) Anyway, in Exynos case, we will use Tizen platform as a real user. This means that all interfaces to be added or modified to -next will be verified on Tizen platform. Thanks, Inki Dae > >> >> (In any case, having separate-from-Tizen userspace graphics stack >> repositories would be very welcome, I think: there are a huge number >> of repositories for Tizen - something like six copies of libtbm alone >> - and it is unclear how to build them on a generic userspace / if they >> will actually build at all / if they will run on mainline kernels. >> Having a separate tree will make it very clear to people how to get >> things working on top of a mainline/staged-for-next kernel.) > > One libtbm is common library used by Tizen platform, which has Tizen standard > API and > the interfaces of the libtbm will never changed. Others are all backend > libraries. > In fact, Tizen supports various boards based on various SoC such as > snapdragon, allwinner, > spreadtrum and Exynos. Among them, only Exynos will run on mainline kernels > as of now. > > Thanks, > Inki Dae > >> >> Thanks very much for your help finding this! >> >> Cheers, >> Daniel >>
[GIT PULL] exynos-drm-next
On 3 November 2015 at 12:11, Inki Dae wrote: > Hi Dave, > > 2015ë 11ì 03ì¼ 08:10ì Dave Airlie ì´(ê°) ì´ ê¸: >> On 28 October 2015 at 22:37, Inki Dae wrote: >>> Hi Daniel, >>> >>> 2015ë 10ì 28ì¼ 20:52ì Daniel Stone ì´(ê°) ì´ ê¸: Hi Inki, On 28 October 2015 at 11:16, Inki Dae wrote: > 2015ë 10ì 28ì¼ 20:00ì Daniel Stone ì´(ê°) ì´ ê¸: >> On 28 October 2015 at 10:58, Daniel Stone >> wrote: >>> Is there any open user we can review? >> >> For clarity, what I meant by these parts was: is there somewhere we >> can take TBM + Xorg/Wayland for Exynos hardware? Even better if it's >> able to run on commercially-available parts such as 5422/5800 >> (Chromebook 2, ODROID-XU3). As you know, it is quite > > Yes, you could get TBM + Xorg/Wayland for Exynos hardware - ODROID-XU3 > through below link, > https://review.tizen.org/git/ > > And below is Linux 4.0 kernel for ODROID-XU3/XU4. > > https://review.tizen.org/git/?p=platform/kernel/linux-exynos.git;a=shortlog;h=refs/heads/tizen Thanks very much for the pointer. I managed to find the exynos Xorg driver in use, but unfortunately the only tbm backend I could find is labelled for exynos4412. Is this backend also usable on 5xxx/XU3, or is that backend really only for Trats2, and the 5xxx backend is private? >>> >>> Prefix name may be strange but below libtbm backend is used for Trats2 and >>> Odoid-XU3/4. >>> Actually, changing the backend name to 'exynos' instead of 'exynos' >>> would be more reasonable. >>> >>> https://review.tizen.org/git/?p=platform/adaptation/samsung_exynos/libtbm-exynos4412.git;a=summary >>> Anyway, regardless of that, as far as I can tell, the Xorg driver uses TBM to do buffer mapping, and the TBM backend uses DUMB_MAP rather than the new call here. Is there something I'm missing? >>> >>> You are right. I found that the patch applied to the backend exists in >>> local branch. >>> I thought the patch exists already in tizen.org because we had already test. >>> Anyway, the patch will be merged soon. >>> (In any case, having separate-from-Tizen userspace graphics stack repositories would be very welcome, I think: there are a huge number of repositories for Tizen - something like six copies of libtbm alone - and it is unclear how to build them on a generic userspace / if they will actually build at all / if they will run on mainline kernels. Having a separate tree will make it very clear to people how to get things working on top of a mainline/staged-for-next kernel.) >>> >>> One libtbm is common library used by Tizen platform, which has Tizen >>> standard API and >>> the interfaces of the libtbm will never changed. Others are all backend >>> libraries. >>> In fact, Tizen supports various boards based on various SoC such as >>> snapdragon, allwinner, >>> spreadtrum and Exynos. Among them, only Exynos will run on mainline kernels >>> as of now. >>> >>> Thanks, >>> Inki Dae >>> >> >> Daniel, >> >> Is there still an issue here, >> >> Inki can you send me a pull request without the problematic patch so >> we can at least merge >> all the other works you've lined up. We can add this on top once >> people are happy. > > Ok, I will request pull again excepting the patch and rebasing on top of > drm-next. > It's not necessary to rebase I don't think, whatever base you are on now is fine. Dave.
[RESEND][GIT PULL] exynos-drm-next
Hi Dave, This pull request includes comprehensive cleanups to HDMI part and several fixups. In addition, this pull request includes also a defconfig patch which enables mixer driver as default. For this, I got already Acked-by from Krzysztof Kozlowski who is a Exynos SoC maintainer. In previous pull-request[1], there was Exynos specific userspace interface, DRM_EXYNOS_GEM_MAP ioctl. However, there was no real user actually using the interface yet. So removed it from this pull request. We have a real user[2] for it called Tizen platform, and the Graphics stack of the Tizen consists of Wayland or Xorg, libtbm and its backend specific to Hardware. The libtbm backend uses libdrm. So we are wait for the libtbm backend uses DRM_EXYNOS_GEM_MAP interface. Please kindly let me know if there is any problem. Thanks, Inki Dae [1] http://www.spinics.net/lists/dri-devel/msg93217.html [2] http://www.spinics.net/lists/dri-devel/msg93248.html The following changes since commit d7e1bc3f5e70c5a106606e33cfa4d413459611ba: Merge branch 'msm-next' of git://people.freedesktop.org/~robclark/linux into drm-next (2015-10-23 11:54:03 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to df547bf7735a623500eedff9cc6716ac1d82b95d: drm/exynos/gem: remove DMA-mapping hacks used for constructing page array (2015-11-03 11:46:39 +0900) Andrzej Hajda (27): drm/exynos/hdmi: remove support for deprecated compatible drm/exynos/hdmi: use mappings for registers with IP dependent address drm/exynos/hdmi: move PLL stabilization check code to separate function drm/exynos/hdmi: simplify HDMI-PHY power sequence drm/exynos/hdmi: replace all writeb with writel drm/exynos/hdmi: fix removal order drm/exynos/hdmi: use optional regulator_get for hdmi-en drm/exynos/hdmi: use constant size array for regulators drm/exynos/hdmi: simplify clock re-parenting drm/exynos/hdmi: convert to gpiod API drm/exynos/hdmi: remove deprecated hdmi_resources structure drm/exynos/hdmi: convert container_of macro to inline function drm/exynos/hdmi: improve HDMI/ACR related code drm/exynos/hdmi: remove unused field drm/exynos/decon5433: add PCLK clock drm/exynos/decon5433: fix timing registers writes drm/exynos/decon5433: add function to set particular register bits drm/exynos/decon5433: merge different flag fields drm/exynos/decon5433: remove duplicated initialization drm/exynos/decon5433: add support for DECON-TV drm/exynos: add atomic_check callback to exynos_crtc drm/exynos/mixer: replace direct cross-driver call with drm mode validation drm/exynos: separate Mixer and HDMI drivers drm/exynos: abstract out common dependency drm/exynos: re-arrange Kconfig entries drm/exynos: simplify Kconfig component names ARM: exynos_defconfig: enable Exynos DRM Mixer driver Gustavo Padovan (2): drm/exynos: add global macro for the default primary plane drm/exynos: add cursor plane support Ingi Kim (1): drm/exynos: fix spelling errors Joonyoung Shim (2): drm/exynos: fix to detach device of iommu drm/exynos: cleanup name of gem object for exynos_drm Marek Szyprowski (1): drm/exynos/gem: remove DMA-mapping hacks used for constructing page array Tomasz Stanislawski (1): drm: exynos: mixer: fix using usleep() in atomic context arch/arm/configs/exynos_defconfig | 1 + drivers/gpu/drm/exynos/Kconfig| 75 ++-- drivers/gpu/drm/exynos/Makefile | 3 +- drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 324 + drivers/gpu/drm/exynos/exynos7_drm_decon.c| 7 +- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 12 + drivers/gpu/drm/exynos/exynos_drm_drv.c | 4 +- drivers/gpu/drm/exynos/exynos_drm_drv.h | 5 + drivers/gpu/drm/exynos/exynos_drm_fb.c| 45 ++- drivers/gpu/drm/exynos/exynos_drm_fb.h| 5 +- drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 53 +-- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 16 +- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 7 +- drivers/gpu/drm/exynos/exynos_drm_gem.c | 275 +++--- drivers/gpu/drm/exynos/exynos_drm_gem.h | 15 +- drivers/gpu/drm/exynos/exynos_drm_gsc.c | 12 +- drivers/gpu/drm/exynos/exynos_drm_iommu.c | 3 +- drivers/gpu/drm/exynos/exynos_drm_plane.c | 20 +- drivers/gpu/drm/exynos/exynos_drm_plane.h | 2 + drivers/gpu/drm/exynos/exynos_drm_vidi.c | 8 +- drivers/gpu/drm/exynos/exynos_hdmi.c | 496 +- drivers/gpu/drm/exynos/exynos_mixer.c | 17 +- drivers/gpu/drm/exynos/exynos_mixer.h | 20 --
[GIT PULL] exynos-drm-next
Hi Dave, 2015ë 11ì 03ì¼ 08:10ì Dave Airlie ì´(ê°) ì´ ê¸: > On 28 October 2015 at 22:37, Inki Dae wrote: >> Hi Daniel, >> >> 2015ë 10ì 28ì¼ 20:52ì Daniel Stone ì´(ê°) ì´ ê¸: >>> Hi Inki, >>> >>> On 28 October 2015 at 11:16, Inki Dae wrote: 2015ë 10ì 28ì¼ 20:00ì Daniel Stone ì´(ê°) ì´ ê¸: > On 28 October 2015 at 10:58, Daniel Stone wrote: >> Is there any open user we can review? > > For clarity, what I meant by these parts was: is there somewhere we > can take TBM + Xorg/Wayland for Exynos hardware? Even better if it's > able to run on commercially-available parts such as 5422/5800 > (Chromebook 2, ODROID-XU3). As you know, it is quite Yes, you could get TBM + Xorg/Wayland for Exynos hardware - ODROID-XU3 through below link, https://review.tizen.org/git/ And below is Linux 4.0 kernel for ODROID-XU3/XU4. https://review.tizen.org/git/?p=platform/kernel/linux-exynos.git;a=shortlog;h=refs/heads/tizen >>> >>> Thanks very much for the pointer. I managed to find the exynos Xorg >>> driver in use, but unfortunately the only tbm backend I could find is >>> labelled for exynos4412. Is this backend also usable on 5xxx/XU3, or >>> is that backend really only for Trats2, and the 5xxx backend is >>> private? >> >> Prefix name may be strange but below libtbm backend is used for Trats2 and >> Odoid-XU3/4. >> Actually, changing the backend name to 'exynos' instead of 'exynos' >> would be more reasonable. >> >> https://review.tizen.org/git/?p=platform/adaptation/samsung_exynos/libtbm-exynos4412.git;a=summary >> >>> >>> Anyway, regardless of that, as far as I can tell, the Xorg driver uses >>> TBM to do buffer mapping, and the TBM backend uses DUMB_MAP rather >>> than the new call here. Is there something I'm missing? >> >> You are right. I found that the patch applied to the backend exists in local >> branch. >> I thought the patch exists already in tizen.org because we had already test. >> Anyway, the patch will be merged soon. >> >>> >>> (In any case, having separate-from-Tizen userspace graphics stack >>> repositories would be very welcome, I think: there are a huge number >>> of repositories for Tizen - something like six copies of libtbm alone >>> - and it is unclear how to build them on a generic userspace / if they >>> will actually build at all / if they will run on mainline kernels. >>> Having a separate tree will make it very clear to people how to get >>> things working on top of a mainline/staged-for-next kernel.) >> >> One libtbm is common library used by Tizen platform, which has Tizen >> standard API and >> the interfaces of the libtbm will never changed. Others are all backend >> libraries. >> In fact, Tizen supports various boards based on various SoC such as >> snapdragon, allwinner, >> spreadtrum and Exynos. Among them, only Exynos will run on mainline kernels >> as of now. >> >> Thanks, >> Inki Dae >> > > Daniel, > > Is there still an issue here, > > Inki can you send me a pull request without the problematic patch so > we can at least merge > all the other works you've lined up. We can add this on top once > people are happy. Ok, I will request pull again excepting the patch and rebasing on top of drm-next. The patch, Exynos specific MAP, hasn't been merged yet to libtbm backend even through already tested. So I think it seems reasonable for us to wait for the merged real user, which would be Daniel's answer. Thanks, Inki Dae > > Dave. >
[GIT PULL] exynos-drm-next
On 28 October 2015 at 22:37, Inki Dae wrote: > Hi Daniel, > > 2015ë 10ì 28ì¼ 20:52ì Daniel Stone ì´(ê°) ì´ ê¸: >> Hi Inki, >> >> On 28 October 2015 at 11:16, Inki Dae wrote: >>> 2015ë 10ì 28ì¼ 20:00ì Daniel Stone ì´(ê°) ì´ ê¸: On 28 October 2015 at 10:58, Daniel Stone wrote: > Is there any open user we can review? For clarity, what I meant by these parts was: is there somewhere we can take TBM + Xorg/Wayland for Exynos hardware? Even better if it's able to run on commercially-available parts such as 5422/5800 (Chromebook 2, ODROID-XU3). As you know, it is quite >>> >>> Yes, you could get TBM + Xorg/Wayland for Exynos hardware - ODROID-XU3 >>> through below link, >>> https://review.tizen.org/git/ >>> >>> And below is Linux 4.0 kernel for ODROID-XU3/XU4. >>> >>> https://review.tizen.org/git/?p=platform/kernel/linux-exynos.git;a=shortlog;h=refs/heads/tizen >> >> Thanks very much for the pointer. I managed to find the exynos Xorg >> driver in use, but unfortunately the only tbm backend I could find is >> labelled for exynos4412. Is this backend also usable on 5xxx/XU3, or >> is that backend really only for Trats2, and the 5xxx backend is >> private? > > Prefix name may be strange but below libtbm backend is used for Trats2 and > Odoid-XU3/4. > Actually, changing the backend name to 'exynos' instead of 'exynos' would > be more reasonable. > > https://review.tizen.org/git/?p=platform/adaptation/samsung_exynos/libtbm-exynos4412.git;a=summary > >> >> Anyway, regardless of that, as far as I can tell, the Xorg driver uses >> TBM to do buffer mapping, and the TBM backend uses DUMB_MAP rather >> than the new call here. Is there something I'm missing? > > You are right. I found that the patch applied to the backend exists in local > branch. > I thought the patch exists already in tizen.org because we had already test. > Anyway, the patch will be merged soon. > >> >> (In any case, having separate-from-Tizen userspace graphics stack >> repositories would be very welcome, I think: there are a huge number >> of repositories for Tizen - something like six copies of libtbm alone >> - and it is unclear how to build them on a generic userspace / if they >> will actually build at all / if they will run on mainline kernels. >> Having a separate tree will make it very clear to people how to get >> things working on top of a mainline/staged-for-next kernel.) > > One libtbm is common library used by Tizen platform, which has Tizen standard > API and > the interfaces of the libtbm will never changed. Others are all backend > libraries. > In fact, Tizen supports various boards based on various SoC such as > snapdragon, allwinner, > spreadtrum and Exynos. Among them, only Exynos will run on mainline kernels > as of now. > > Thanks, > Inki Dae > Daniel, Is there still an issue here, Inki can you send me a pull request without the problematic patch so we can at least merge all the other works you've lined up. We can add this on top once people are happy. Dave.
[GIT PULL] exynos-drm-next
Hi Daniel, 2015ë 10ì 28ì¼ 20:52ì Daniel Stone ì´(ê°) ì´ ê¸: > Hi Inki, > > On 28 October 2015 at 11:16, Inki Dae wrote: >> 2015ë 10ì 28ì¼ 20:00ì Daniel Stone ì´(ê°) ì´ ê¸: >>> On 28 October 2015 at 10:58, Daniel Stone wrote: Is there any open user we can review? >>> >>> For clarity, what I meant by these parts was: is there somewhere we >>> can take TBM + Xorg/Wayland for Exynos hardware? Even better if it's >>> able to run on commercially-available parts such as 5422/5800 >>> (Chromebook 2, ODROID-XU3). As you know, it is quite >> >> Yes, you could get TBM + Xorg/Wayland for Exynos hardware - ODROID-XU3 >> through below link, >> https://review.tizen.org/git/ >> >> And below is Linux 4.0 kernel for ODROID-XU3/XU4. >> >> https://review.tizen.org/git/?p=platform/kernel/linux-exynos.git;a=shortlog;h=refs/heads/tizen > > Thanks very much for the pointer. I managed to find the exynos Xorg > driver in use, but unfortunately the only tbm backend I could find is > labelled for exynos4412. Is this backend also usable on 5xxx/XU3, or > is that backend really only for Trats2, and the 5xxx backend is > private? Prefix name may be strange but below libtbm backend is used for Trats2 and Odoid-XU3/4. Actually, changing the backend name to 'exynos' instead of 'exynos' would be more reasonable. https://review.tizen.org/git/?p=platform/adaptation/samsung_exynos/libtbm-exynos4412.git;a=summary > > Anyway, regardless of that, as far as I can tell, the Xorg driver uses > TBM to do buffer mapping, and the TBM backend uses DUMB_MAP rather > than the new call here. Is there something I'm missing? You are right. I found that the patch applied to the backend exists in local branch. I thought the patch exists already in tizen.org because we had already test. Anyway, the patch will be merged soon. > > (In any case, having separate-from-Tizen userspace graphics stack > repositories would be very welcome, I think: there are a huge number > of repositories for Tizen - something like six copies of libtbm alone > - and it is unclear how to build them on a generic userspace / if they > will actually build at all / if they will run on mainline kernels. > Having a separate tree will make it very clear to people how to get > things working on top of a mainline/staged-for-next kernel.) One libtbm is common library used by Tizen platform, which has Tizen standard API and the interfaces of the libtbm will never changed. Others are all backend libraries. In fact, Tizen supports various boards based on various SoC such as snapdragon, allwinner, spreadtrum and Exynos. Among them, only Exynos will run on mainline kernels as of now. Thanks, Inki Dae > > Thanks very much for your help finding this! > > Cheers, > Daniel >
[GIT PULL] exynos-drm-next
Hi Daniel, 2015ë 10ì 28ì¼ 20:00ì Daniel Stone ì´(ê°) ì´ ê¸: > Hi, > > On 28 October 2015 at 10:58, Daniel Stone wrote: >> On 28 October 2015 at 10:48, Inki Dae wrote: >>> In Tizen platform, there is a buffer manager called TBM(Tizem Buffer >>> Manager), and >>> this manager uses this new interface of libdrm. >>> >>> Tizen platform can use window systems - wayland or X server - according to >>> version. >>> And the native systems use the TBM interfaces to manage gem buffer. >> >> Is there any open user we can review? > > For clarity, what I meant by these parts was: is there somewhere we > can take TBM + Xorg/Wayland for Exynos hardware? Even better if it's > able to run on commercially-available parts such as 5422/5800 > (Chromebook 2, ODROID-XU3). As you know, it is quite Yes, you could get TBM + Xorg/Wayland for Exynos hardware - ODROID-XU3 through below link, https://review.tizen.org/git/ And below is Linux 4.0 kernel for ODROID-XU3/XU4. https://review.tizen.org/git/?p=platform/kernel/linux-exynos.git;a=shortlog;h=refs/heads/tizen I think below guide would be very useful to you, https://source.tizen.org/release/tizen-3.0-milestones And, we have gerrit review system and you could use it also if you sign up at below link, http://review.tizen.org/gerrit/ Thanks, Inki Dae > difficult/impossible to get access to a generic userspace on the parts > you usually test on such as Trats2/5433/7xxx. > > Cheers, > Daniel >
[GIT PULL] exynos-drm-next
Hi Daniel, 2015ë 10ì 28ì¼ 19:15ì Daniel Stone ì´(ê°) ì´ ê¸: > Hi Inki, > > On 28 October 2015 at 06:55, Inki Dae wrote: >>and revive a Exynos specific interface which was used >>to get fake offset, which is required for application using render node >>to access a gem memory. For userspace codes for the use of this interface, >>you can refer to below link, >> >> https://github.com/dofmind/libdrm/commit/5cc58d765c61b37a26372de9701f3ffe3a1bef70 >> >>We will post a patch for libdrm after this patch is merged to mainline. > > Is there any real (non-libdrm) userspace for this? See Daniel Vetter's > reply to the series here: > 'In general we wait with merging new userspace ABI until that's really > ready, since very often there's some corner cases that you just didn't > think about in your toy demo compared to the real thing. Like how to > manage buffer caches/reuse for apps that essentially run forever (like X > server or a compositor).' Below link is a libdrm codes used by Tizen platform. https://review.tizen.org/git/?p=platform/upstream/libdrm.git;a=commit;h=6e97f25af63a9511ddd3b195a0b844671b8d1a5d In Tizen platform, there is a buffer manager called TBM(Tizem Buffer Manager), and this manager uses this new interface of libdrm. Tizen platform can use window systems - wayland or X server - according to version. And the native systems use the TBM interfaces to manage gem buffer. > > Probably my biggest concern is how well this operates with the > proposed PREP/FINI patches. I would really love to see a real > userspace which exercises both MAP and PREP/FINI: if that shows Hmm... Daniel, seems there was your mislead. I will never merge such PREP/FINI interfaces for cache operation until these will be reviewed enough through real user. So this pull request doesn't include them. We are just planning to apply these interfaces to Tizen platform for more test. Thanks, Inki Dae > problems with this interface, then it means we have to carry this > interface forever, _as well as_ a new cleaned-up one. > > Cheers, > Daniel >
[GIT PULL] exynos-drm-next
Hi Dave, There was one patch I missed. Sorry about this. Below patch removes the hack codes used to build page array and uses more generic way instead. drm/exynos/gem: remove DMA-mapping hacks used for constructing page array I have merged this patch to exynos-drm-next just before. Thanks, Inki Dae 2015ë 10ì 28ì¼ 15:55ì Inki Dae ì´(ê°) ì´ ê¸: > Hi Dave, > >This pull request includes comprehensive cleanups to HDMI part and >several fixups, and revive a Exynos specific interface which was used >to get fake offset, which is required for application using render node >to access a gem memory. For userspace codes for the use of this interface, >you can refer to below link, > > https://github.com/dofmind/libdrm/commit/5cc58d765c61b37a26372de9701f3ffe3a1bef70 > >We will post a patch for libdrm after this patch is merged to mainline. > >In addition, this pull request includes also a defconfig patch which > enables >mixer driver as default. For this, I got already Acked-by from Krzysztof >Kozlowski who is a Exynos SoC maintainer. > >Please kindly let me know if there is any problem. > > Thanks, > Inki Dae > > The following changes since commit d7e1bc3f5e70c5a106606e33cfa4d413459611ba: > > Merge branch 'msm-next' of git://people.freedesktop.org/~robclark/linux > into drm-next (2015-10-23 11:54:03 +1000) > > are available in the git repository at: > > > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos > exynos-drm-next > > for you to fetch changes up to 01bdaac3d7febed08e1b257a9cbb07e04ba8ce4c: > > ARM: exynos_defconfig: enable Exynos DRM Mixer driver (2015-10-28 15:18:31 > +0900) > > > Andrzej Hajda (27): > drm/exynos/hdmi: remove support for deprecated compatible > drm/exynos/hdmi: use mappings for registers with IP dependent address > drm/exynos/hdmi: move PLL stabilization check code to separate function > drm/exynos/hdmi: simplify HDMI-PHY power sequence > drm/exynos/hdmi: replace all writeb with writel > drm/exynos/hdmi: fix removal order > drm/exynos/hdmi: use optional regulator_get for hdmi-en > drm/exynos/hdmi: use constant size array for regulators > drm/exynos/hdmi: simplify clock re-parenting > drm/exynos/hdmi: convert to gpiod API > drm/exynos/hdmi: remove deprecated hdmi_resources structure > drm/exynos/hdmi: convert container_of macro to inline function > drm/exynos/hdmi: improve HDMI/ACR related code > drm/exynos/hdmi: remove unused field > drm/exynos/decon5433: add PCLK clock > drm/exynos/decon5433: fix timing registers writes > drm/exynos/decon5433: add function to set particular register bits > drm/exynos/decon5433: merge different flag fields > drm/exynos/decon5433: remove duplicated initialization > drm/exynos/decon5433: add support for DECON-TV > drm/exynos: add atomic_check callback to exynos_crtc > drm/exynos/mixer: replace direct cross-driver call with drm mode > validation > drm/exynos: separate Mixer and HDMI drivers > drm/exynos: abstract out common dependency > drm/exynos: re-arrange Kconfig entries > drm/exynos: simplify Kconfig component names > ARM: exynos_defconfig: enable Exynos DRM Mixer driver > > Gustavo Padovan (2): > drm/exynos: add global macro for the default primary plane > drm/exynos: add cursor plane support > > Ingi Kim (1): > drm/exynos: fix spelling errors > > Joonyoung Shim (3): > drm/exynos: fix to detach device of iommu > drm/exynos: cleanup name of gem object for exynos_drm > drm/exynos: add DRM_EXYNOS_GEM_MAP ioctl > > Tomasz Stanislawski (1): > drm: exynos: mixer: fix using usleep() in atomic context > > arch/arm/configs/exynos_defconfig | 1 + > drivers/gpu/drm/exynos/Kconfig| 75 ++-- > drivers/gpu/drm/exynos/Makefile | 3 +- > drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 324 + > drivers/gpu/drm/exynos/exynos7_drm_decon.c| 7 +- > drivers/gpu/drm/exynos/exynos_drm_crtc.c | 12 + > drivers/gpu/drm/exynos/exynos_drm_drv.c | 6 +- > drivers/gpu/drm/exynos/exynos_drm_drv.h | 5 + > drivers/gpu/drm/exynos/exynos_drm_fb.c| 45 ++- > drivers/gpu/drm/exynos/exynos_drm_fb.h| 5 +- > drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 53 +-- > drivers/gpu/drm/exynos/exynos_drm_fimc.c | 16 +- > drivers/gpu/drm/exynos/exynos_drm_fimd.c | 7 +- > drivers/gpu/drm/exynos/exynos_drm_gem.c | 248 +++-- > drivers/gpu/drm/exynos/exynos_drm_gem.h | 19 +- > drivers/gpu/drm/exynos/exynos_drm_gsc.c | 12 +- > drivers/gpu/drm/exynos/exynos_drm_iommu.c | 3 +- > drivers/gpu/drm/exynos/exynos_drm_plane.c | 20 +- >
[GIT PULL] exynos-drm-next
Hi Dave, This pull request includes comprehensive cleanups to HDMI part and several fixups, and revive a Exynos specific interface which was used to get fake offset, which is required for application using render node to access a gem memory. For userspace codes for the use of this interface, you can refer to below link, https://github.com/dofmind/libdrm/commit/5cc58d765c61b37a26372de9701f3ffe3a1bef70 We will post a patch for libdrm after this patch is merged to mainline. In addition, this pull request includes also a defconfig patch which enables mixer driver as default. For this, I got already Acked-by from Krzysztof Kozlowski who is a Exynos SoC maintainer. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit d7e1bc3f5e70c5a106606e33cfa4d413459611ba: Merge branch 'msm-next' of git://people.freedesktop.org/~robclark/linux into drm-next (2015-10-23 11:54:03 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to 01bdaac3d7febed08e1b257a9cbb07e04ba8ce4c: ARM: exynos_defconfig: enable Exynos DRM Mixer driver (2015-10-28 15:18:31 +0900) Andrzej Hajda (27): drm/exynos/hdmi: remove support for deprecated compatible drm/exynos/hdmi: use mappings for registers with IP dependent address drm/exynos/hdmi: move PLL stabilization check code to separate function drm/exynos/hdmi: simplify HDMI-PHY power sequence drm/exynos/hdmi: replace all writeb with writel drm/exynos/hdmi: fix removal order drm/exynos/hdmi: use optional regulator_get for hdmi-en drm/exynos/hdmi: use constant size array for regulators drm/exynos/hdmi: simplify clock re-parenting drm/exynos/hdmi: convert to gpiod API drm/exynos/hdmi: remove deprecated hdmi_resources structure drm/exynos/hdmi: convert container_of macro to inline function drm/exynos/hdmi: improve HDMI/ACR related code drm/exynos/hdmi: remove unused field drm/exynos/decon5433: add PCLK clock drm/exynos/decon5433: fix timing registers writes drm/exynos/decon5433: add function to set particular register bits drm/exynos/decon5433: merge different flag fields drm/exynos/decon5433: remove duplicated initialization drm/exynos/decon5433: add support for DECON-TV drm/exynos: add atomic_check callback to exynos_crtc drm/exynos/mixer: replace direct cross-driver call with drm mode validation drm/exynos: separate Mixer and HDMI drivers drm/exynos: abstract out common dependency drm/exynos: re-arrange Kconfig entries drm/exynos: simplify Kconfig component names ARM: exynos_defconfig: enable Exynos DRM Mixer driver Gustavo Padovan (2): drm/exynos: add global macro for the default primary plane drm/exynos: add cursor plane support Ingi Kim (1): drm/exynos: fix spelling errors Joonyoung Shim (3): drm/exynos: fix to detach device of iommu drm/exynos: cleanup name of gem object for exynos_drm drm/exynos: add DRM_EXYNOS_GEM_MAP ioctl Tomasz Stanislawski (1): drm: exynos: mixer: fix using usleep() in atomic context arch/arm/configs/exynos_defconfig | 1 + drivers/gpu/drm/exynos/Kconfig| 75 ++-- drivers/gpu/drm/exynos/Makefile | 3 +- drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 324 + drivers/gpu/drm/exynos/exynos7_drm_decon.c| 7 +- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 12 + drivers/gpu/drm/exynos/exynos_drm_drv.c | 6 +- drivers/gpu/drm/exynos/exynos_drm_drv.h | 5 + drivers/gpu/drm/exynos/exynos_drm_fb.c| 45 ++- drivers/gpu/drm/exynos/exynos_drm_fb.h| 5 +- drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 53 +-- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 16 +- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 7 +- drivers/gpu/drm/exynos/exynos_drm_gem.c | 248 +++-- drivers/gpu/drm/exynos/exynos_drm_gem.h | 19 +- drivers/gpu/drm/exynos/exynos_drm_gsc.c | 12 +- drivers/gpu/drm/exynos/exynos_drm_iommu.c | 3 +- drivers/gpu/drm/exynos/exynos_drm_plane.c | 20 +- drivers/gpu/drm/exynos/exynos_drm_plane.h | 2 + drivers/gpu/drm/exynos/exynos_drm_vidi.c | 8 +- drivers/gpu/drm/exynos/exynos_hdmi.c | 496 +- drivers/gpu/drm/exynos/exynos_mixer.c | 17 +- drivers/gpu/drm/exynos/exynos_mixer.h | 20 -- drivers/gpu/drm/exynos/regs-hdmi.h| 33 +- include/uapi/drm/exynos_drm.h | 17 +- include/video/exynos5433_decon.h | 29 ++ 26 files changed, 703 insertions(+), 780 deletions(-) delete mode 100644 drivers/gpu/drm/exynos/exynos_mixer.h
[GIT PULL] exynos-drm-next
Hi Inki, On 28 October 2015 at 11:16, Inki Dae wrote: > 2015ë 10ì 28ì¼ 20:00ì Daniel Stone ì´(ê°) ì´ ê¸: >> On 28 October 2015 at 10:58, Daniel Stone wrote: >>> Is there any open user we can review? >> >> For clarity, what I meant by these parts was: is there somewhere we >> can take TBM + Xorg/Wayland for Exynos hardware? Even better if it's >> able to run on commercially-available parts such as 5422/5800 >> (Chromebook 2, ODROID-XU3). As you know, it is quite > > Yes, you could get TBM + Xorg/Wayland for Exynos hardware - ODROID-XU3 > through below link, > https://review.tizen.org/git/ > > And below is Linux 4.0 kernel for ODROID-XU3/XU4. > > https://review.tizen.org/git/?p=platform/kernel/linux-exynos.git;a=shortlog;h=refs/heads/tizen Thanks very much for the pointer. I managed to find the exynos Xorg driver in use, but unfortunately the only tbm backend I could find is labelled for exynos4412. Is this backend also usable on 5xxx/XU3, or is that backend really only for Trats2, and the 5xxx backend is private? Anyway, regardless of that, as far as I can tell, the Xorg driver uses TBM to do buffer mapping, and the TBM backend uses DUMB_MAP rather than the new call here. Is there something I'm missing? (In any case, having separate-from-Tizen userspace graphics stack repositories would be very welcome, I think: there are a huge number of repositories for Tizen - something like six copies of libtbm alone - and it is unclear how to build them on a generic userspace / if they will actually build at all / if they will run on mainline kernels. Having a separate tree will make it very clear to people how to get things working on top of a mainline/staged-for-next kernel.) Thanks very much for your help finding this! Cheers, Daniel
[GIT PULL] exynos-drm-next
Hi, On 28 October 2015 at 10:58, Daniel Stone wrote: > On 28 October 2015 at 10:48, Inki Dae wrote: >> In Tizen platform, there is a buffer manager called TBM(Tizem Buffer >> Manager), and >> this manager uses this new interface of libdrm. >> >> Tizen platform can use window systems - wayland or X server - according to >> version. >> And the native systems use the TBM interfaces to manage gem buffer. > > Is there any open user we can review? For clarity, what I meant by these parts was: is there somewhere we can take TBM + Xorg/Wayland for Exynos hardware? Even better if it's able to run on commercially-available parts such as 5422/5800 (Chromebook 2, ODROID-XU3). As you know, it is quite difficult/impossible to get access to a generic userspace on the parts you usually test on such as Trats2/5433/7xxx. Cheers, Daniel
[GIT PULL] exynos-drm-next
Hi Inki, On 28 October 2015 at 10:48, Inki Dae wrote: > 2015ë 10ì 28ì¼ 19:15ì Daniel Stone ì´(ê°) ì´ ê¸: >> On 28 October 2015 at 06:55, Inki Dae wrote: >>>and revive a Exynos specific interface which was used >>>to get fake offset, which is required for application using render node >>>to access a gem memory. For userspace codes for the use of this >>> interface, >>>you can refer to below link, >>> >>> https://github.com/dofmind/libdrm/commit/5cc58d765c61b37a26372de9701f3ffe3a1bef70 >>> >>>We will post a patch for libdrm after this patch is merged to mainline. >> >> Is there any real (non-libdrm) userspace for this? See Daniel Vetter's >> reply to the series here: >> 'In general we wait with merging new userspace ABI until that's really >> ready, since very often there's some corner cases that you just didn't >> think about in your toy demo compared to the real thing. Like how to >> manage buffer caches/reuse for apps that essentially run forever (like X >> server or a compositor).' > > Below link is a libdrm codes used by Tizen platform. > https://review.tizen.org/git/?p=platform/upstream/libdrm.git;a=commit;h=6e97f25af63a9511ddd3b195a0b844671b8d1a5d Thanks for the link, but I meant something like this: > In Tizen platform, there is a buffer manager called TBM(Tizem Buffer > Manager), and > this manager uses this new interface of libdrm. > > Tizen platform can use window systems - wayland or X server - according to > version. > And the native systems use the TBM interfaces to manage gem buffer. Is there any open user we can review? Daniel V's quote above explains the policy: having a userspace patch which simply exposes the same interface and then runs one or two trivial operations is usually not enough to get new interfaces merged. Not only does having an open, reviewable, userspace prove that the interface is suitable and does what it's supposed to be, but it also acts as a benchmark for future changes. Anyone working in future can then review the userspace to make sure they don't break it as an existing user of the interface. Without the userspace, establishing the semantics of new interfaces is really quite difficult, and you end up with quite a lot of breakage ... >> Probably my biggest concern is how well this operates with the >> proposed PREP/FINI patches. I would really love to see a real >> userspace which exercises both MAP and PREP/FINI: if that shows > > Hmm... Daniel, seems there was your mislead. I will never merge such > PREP/FINI interfaces > for cache operation until these will be reviewed enough through real user. > So this pull request doesn't include them. We are just planning to apply > these interfaces > to Tizen platform for more test. Fair enough. It would be great to see a real user for them emerge. My main concern was that there would be an interaction between the map/prep/fini patches which meant that in order for prep/fini to work correctly, effectively a map2 would be required. Cheers, Daniel
[GIT PULL] exynos-drm-next
Hi Inki, On 28 October 2015 at 06:55, Inki Dae wrote: >and revive a Exynos specific interface which was used >to get fake offset, which is required for application using render node >to access a gem memory. For userspace codes for the use of this interface, >you can refer to below link, > > https://github.com/dofmind/libdrm/commit/5cc58d765c61b37a26372de9701f3ffe3a1bef70 > >We will post a patch for libdrm after this patch is merged to mainline. Is there any real (non-libdrm) userspace for this? See Daniel Vetter's reply to the series here: 'In general we wait with merging new userspace ABI until that's really ready, since very often there's some corner cases that you just didn't think about in your toy demo compared to the real thing. Like how to manage buffer caches/reuse for apps that essentially run forever (like X server or a compositor).' Probably my biggest concern is how well this operates with the proposed PREP/FINI patches. I would really love to see a real userspace which exercises both MAP and PREP/FINI: if that shows problems with this interface, then it means we have to carry this interface forever, _as well as_ a new cleaned-up one. Cheers, Daniel
[GIT PULL] exynos-drm-next
Hi Dave, This is a last pull request, which includes two g2d patches I missed, and more cleanup series of Exynos drm driver. The cleanup series makes Exynos drm driver more simple, and removes unnecessary codes, and considers multiple plane format of framebuffer. I hope this not to be late. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 879a37d00f1882b1e56a66e626af4194d592d257: Merge branch 'exynos-drm-next' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-next (2015-08-31 10:25:45 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to c3058579a2882bb4bb6bf1ab0fe65f5ed070e530: drm/exynos: remove buf_cnt from struct exynos_drm_fb (2015-09-02 23:10:34 +0900) Joonyoung Shim (9): drm/exynos: remove exynos_drm_fb_set_buf_cnt() drm/exynos: s/exynos_gem_obj/obj in exynos_drm_fbdev.c drm/exynos: cleanup exynos_drm_fbdev_update() drm/exynos: update fb_info via only one function drm/exynos: cleanup to get gem object for fb drm/exynos: update exynos_drm_framebuffer_init() for multiple buffers drm/exynos: cleanup exynos_user_fb_create() drm/exynos: remove exynos_drm_fb_get_buf_cnt() drm/exynos: remove buf_cnt from struct exynos_drm_fb Tobias Jakobi (2): drm/exynos: fix size check in g2d_check_buf_desc_is_valid() drm/exynos: remove superfluous checks in g2d_check_reg_offset() drivers/gpu/drm/exynos/exynos_drm_fb.c| 115 + drivers/gpu/drm/exynos/exynos_drm_fb.h| 12 +-- drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 78 --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 59 ++- drivers/gpu/drm/exynos/exynos_drm_plane.c |2 +- 5 files changed, 110 insertions(+), 156 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave, This is a second pull-request which adds last part of atomic modeset/pageflip support, render node support, clean-up, and fix-up. Please, kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 92cffd56b21c825579f3b37bc7803e4c37073076: drm/nouveau/dispnv04: fix build on powerpc (2015-08-28 20:33:58 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to 50002d4c2176da6b2ed5a2529a2367c05f0fd73b: drm/exynos: fix build warning to exynos_drm_gem.c (2015-08-31 01:12:36 +0900) Gustavo Padovan (12): drm/exynos: don't track enabled state at exynos_crtc drm/exynos: fimd: unify call to exynos_drm_crtc_finish_pageflip() drm/exynos: add prepare and cleanup phases for planes drm/exynos: fimd: move window protect code to prepare/cleanup_plane drm/exynos: check for pending fb before finish update drm/exynos: add macro to get the address of START_S reg drm/exynos: fimd: only finish update if START == START_S drm/exynos: add atomic asynchronous commit drm/exynos: wait all planes updates to finish drm/exynos: remove wait queue for pending page flip drm/exynos: Enable atomic modesetting feature drm/exynos: remove legacy ->suspend()/resume() Hyungwon Hwang (1): drm/exynos: implement atomic_{begin/flush} of DECON Inki Dae (1): drm/exynos: fix build warning to exynos_drm_gem.c Joonyoung Shim (1): drm/exynos: add render node support Marek Szyprowski (1): drm/exynos: Properly report supported formats for each device drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 54 +-- drivers/gpu/drm/exynos/exynos7_drm_decon.c| 55 ++- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 69 - drivers/gpu/drm/exynos/exynos_drm_crtc.h |4 +- drivers/gpu/drm/exynos/exynos_drm_drv.c | 196 ++--- drivers/gpu/drm/exynos/exynos_drm_drv.h | 24 ++- drivers/gpu/drm/exynos/exynos_drm_fb.c| 35 - drivers/gpu/drm/exynos/exynos_drm_fimd.c | 92 drivers/gpu/drm/exynos/exynos_drm_gem.c |2 +- drivers/gpu/drm/exynos/exynos_drm_plane.c | 13 +- drivers/gpu/drm/exynos/exynos_drm_plane.h |1 + drivers/gpu/drm/exynos/exynos_drm_vidi.c | 19 ++- drivers/gpu/drm/exynos/exynos_mixer.c | 40 - include/video/samsung_fimd.h |1 + 14 files changed, 452 insertions(+), 153 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave, This pull request includes big cleanup and some fixups. Summary: - Clean up HDMI and MIXER parts - Clean up legacy structures specific to Exynos DRM . This patch series removes existing exyons_drm_display and exynos_drm_encoder structures specific to Exynos DRM, and makes them to replace with common drm_encoder structure. With cleanup patch, we removes exynos_drm_encoder module. - Clean up gem, dmabuf and buffer modules . This patch series replaces existing Exynos DRM dmabuf codes with common drm prime ones, and embeds all codes of exynos_drm_buf into exynos_drm_gem module. With cleanup patch, we removes exynos_drm_buf and exynos_drm_dmabuf modules. - And some fixups. There is one patch series[1] which is bening reviewed yet, which improves atomic modeset feature. So I will plan to have a pull request for it once more if the patch series has no problem. [1] http://www.spinics.net/lists/dri-devel/msg88269.html Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 8f9cb50789e76f3e224e8861adf650e55c747af4: Merge tag 'drm-amdkfd-next-fixes-2015-08-05' of git://people.freedesktop.org/~gabbayo/linux into drm-next (2015-08-14 10:15:24 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to 2a8cb48945408984cd04c850b293f467b32ec5af: drm/exynos: merge exynos_drm_buf.c to exynos_drm_gem.c (2015-08-16 14:39:32 +0900) Andrzej Hajda (13): drm/exynos/hdmi: fix edid memory leak drm/exynos/mixer: fix interrupt clearing drm/exynos/mixer: correct vsync configuration sequence drm/exynos/mixer: always update INT_EN cache drm/exynos/hdmi: remove old platform data code drm/exynos/hdmi: Simplify HPD gpio handling drm/exynos/hdmi: remove private lock code drm/exynos/hdmi: add driver data pointer to private context drm/exynos/hdmi: remove redundant configuration fields drm/exynos/hdmi: remove hdmi_v13_conf struct drm/exynos/hdmi: remove hdmi_v14_conf struct drm/exynos/mixer: simplify poweron flag drm/exynos/mixer: replace MXR_INT_EN register cache with flag Gustavo Padovan (20): drm/exynos: pass the correct pipe number drm/exynos: use KMS version of DRM vblanks functions drm/exynos: remove duplicated check for suspend drm/exynos: rename win_commit/disable to atomic-like names drm/exynos: pass struct exynos_drm_plane in update/enable drm/exynos: use drm atomic state directly drm/exynos: remove unused fields from struct exynos_drm_plane drm/exynos: unify exynos_drm_plane names with drm core drm/exynos: return return value of exynos_crtc->enable_vblank drm/exynos: split display's .dpms() into .enable() and .disable() drm/exynos: remove wrappers for phy_power_{on,off} drm/exynos: remove unused .remove() and .check_mode() ops from display drm/exynos: simplify calculation of possible CRTCs drm/exynos: remove struct exynos_drm_display drm/exynos: remove extra call to hdmi_commit() drm/exynos: remove extra call to exynos_dp_commit() drm/exynos: remove exynos_encoder's .commit() op drm/exynos: remove exynos_drm_create_enc_conn() drm/exynos: fold encoder setup into exynos_drm_load() drm/exynos: remove struct exynos_drm_encoder layer Hyungwon Hwang (2): drm/exynos: gsc: fix wrong bitwise operation for swap detection drm/exynos: gsc: Handles the combination of rotation and flip Joonyoung Shim (17): drm/exynos: remove to use ifdef CONFIG_ARM_DMA_USE_IOMMU drm/exynos: remove unnecessary checking to support iommu drm/exynos: move order to register vidi kms driver drm/exynos: remove drm_iommu_attach_device_if_possible drm/exynos: clear channels only when iommu is enabled drm/exynos: stop using sgtable in page fault handler drm/exynos: remove function convert_to_vm_err_msg drm/exynos: remove mutex locking in pagefault handler drm/exynos: remove function exynos_drm_gem_map_buf drm/exynos: stop copying sg table drm/exynos: remove unused fields of struct exynos_drm_gem_buf drm/exynos: use ERR_PTR instead of NULL in exynos_drm_gem_init drm/exynos: remove function check_gem_flags drm/exynos: remove function update_vm_cache_attr drm/exynos: remove function roundup_gem_size drm/exynos: use prime helpers drm/exynos: merge exynos_drm_buf.c to exynos_drm_gem.c Marek Szyprowski (1): drm/exynos/fimc: fix runtime pm support drivers/gpu/drm/exynos/Makefile |7 +- drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 65 +- drivers/gpu/drm/exynos/exynos7_drm_decon.c| 94 ++- drivers/gpu/drm/exynos/exynos_dp_core.c | 123 +--
[GIT PULL] exynos-drm-next
Hi Dave, With this pull request, Exynos drm also supports atomic feature. However, this doesn't guarantee atomic operation yet so we will more enhance it later. Besides, it includes new drivers, MIC and DECON for Exynos5433 SoC, and iommu support and consolidation to driver initialization. Ps. this pull request also contains device tree relevant patches. For this, I got the Acked-by from maintainers - Rob Herring who is a device tree maintainer and Krzysztof Kozlowski who is a Exynos SoC maintainer - for each patch so there is no problem that these patches go to mainline though drm-next. Summary: . Add atomic feature support - Exynos also now supports atomic feature. However, it doesn't guarantee atomic operation yet, and is required for more cleanups. This time we just modified for Exynos drm driver to use atomic interfaces instead of legacy ones. Next time, we will enhance Exynos drm driver to support the atomic operation. . Add iommu support - This is a patch series according to below Exynos iommu integration work with DT and dma-mapping subsystem, http://lwn.net/Articles/607626/ . Consolidate Exynos drm driver initialization. - This patch sereis resolves the issue that only the first compoments was bound when happened deferred probing for other pipelines and also makes the driver to be more cleanned up by moving the dispered codes for registering kms drivers to one place. . Add new MIC, DECON drivers, and MIPI-DSI support for Exynos5433. - Add MIC(Mobile image compressor) driver. MIC is a new IP for Exynos5433 and later, which is used to transfer frame data to MIPI-DSI controller compressing the data to reduce memory bandwidth. - Add DECON driver for Exynos5433 SoC. This IP is a dislay controller similar to Exynos7's one but this controller has much different registers from Exynos7's ones so this driver has been implemented separately. We will implement a helper modules for FIMD and two DECON controllers to remove duplicated codes later. - Add Exynos5433 SoC support to MIPI-DSI driver, and device tree relevant patches. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 0dc499aff57f5e787214d5085dd1c391e0f93710: Merge branch 'virtio-gpu-drm-next' of git://git.kraxel.org/linux into drm-next (2015-06-18 13:01:04 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to 4f01e65037187581971f8b1068d4e1b1300a6562: ARM: dts: rename the clock of MIPI DSI 'pll_clk' to 'sclk_mipi' (2015-06-22 21:40:13 +0900) Andrzej Hajda (3): drm/exynos: consolidate driver/device initialization code drm/exynos: fix broken component binding in case of multiple pipelines drm/exynos: remove SoC checking code Gustavo Padovan (16): drm/exynos: atomic phase 1: use drm_plane_helper_update() drm/exynos: atomic phase 1: use drm_plane_helper_disable() drm/exynos: atomic phase 1: add .mode_set_nofb() callback drm/exynos: atomic phase 2: wire up state reset(), duplicate() and destroy() drm/exynos: atomic phase 2: keep track of framebuffer pointer drm/exynos: atomic phase 3: atomic updates of planes drm/exynos: atomic phase 3: use atomic .set_config helper drm/exynos: atomic phase 3: convert page flips drm/exynos: remove exported functions from exynos_drm_plane drm/exynos: don't disable unused functions at init drm/exynos: move exynos_drm_crtc_disable() drm/exynos: add exynos specific .atomic_commit() drm/exynos: atomic dpms support drm/exynos: remove unnecessary calls to disable_plane() drm/exynos: split exynos_crtc->dpms in enable() and disable() drm/exynos: add error messages if clks failed to get enabled Hyungwon Hwang (17): drm/exynos: dsi: check whether dsi is enabled before sending data drm/exynos: ipp: fix wrong index referencing a config element drm/exynos: ipp: validate a GEM handle with multiple planes drm/exynos: remove the dependency of DP driver for ARCH_EXYNOS drm/exynos: Add the dependency for DRM_EXYNOS to DPI/DSI/DP drm/exynos: add drm_iommu_attach_device_if_possible() drm/exynos: fix the input prompt of Exynos7 DECON of: add helper for getting endpoint node of specific identifiers drm/exynos: mic: add MIC driver drm/exynos: dsi: rename pll_clk to sclk_clk drm/exynos: dsi: add macros for register access drm/exynos: dsi: make use of driver data for static values drm/exynos: dsi: make use of array for clock access drm/exynos: dsi: add support for Exynos5433 drm/exynos: dsi: add support for MIC driver as a bridge drm/exynos: dsi: do not set TE GPIO
[GIT PULL] exynos-drm-next
Hi Dave, This pull request contains just cleanup for atomic pageflip/modeset support, and some fixeups. We wanted to merge atomic pageflip/modeset feature support, new drivers - MIC and DECON for exynos5433 SoC - and relevant patches this time. However, I'd found that these features are not only safe enough but also aren't tested yet. So for them, I'd like to have enough times for the reviews. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 1d8ac08d498d579aae36221a80b4b724b2f52f39: Merge tag 'v4.0-rc7' into drm-next (2015-04-09 07:48:27 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to 68a2913407d8defac36f381e4877507a06e57c8e: drm/exynos: Fix FIMD buffer size calculation (2015-04-13 11:48:20 +0900) Beata Michalska (1): drm/exynos/ipp: Validate buffer enqueue requests Daniel Stone (1): drm/exynos: Fix FIMD buffer size calculation Gustavo Padovan (7): drm/exynos: fimd: fix alpha setting for XR24 pixel format drm/exynos: remove unused exynos_crtc->win_enable() callback drm/exynos: remove struct *_win_data abstraction on planes drm/exynos: preset zpos value for overlay planes drm/exynos: make zpos property immutable drm/exynos: remove exynos_plane_destroy() drm/exynos: remove leftover functions declarations Hyungwon Hwang (2): drm/exynos: dsi: remove the empty mode_valid callback drm/exynos: fimd: check whether exynos_drm_crtc_create succeed or not Joonyoung Shim (2): drm/exynos: use src_x and src_y instead of fb_x and fb_y drm/exynos: add ratio calculation Krzysztof Kozlowski (1): drm/exynos: Enable DP clock to fix display on Exynos5250 and other Mandeep Singh Baines (1): drm/exynos: track vblank events on a per crtc basis Tobias Jakobi (3): drm/exynos: fix typos in hdmi and mixer drm/exynos: remove superfluous error messages drm/exynos: mixer: add 2x scaling to mixer_graph_buffer drivers/gpu/drm/exynos/exynos7_drm_decon.c | 178 +++ drivers/gpu/drm/exynos/exynos_dp_core.c| 10 ++ drivers/gpu/drm/exynos/exynos_drm_crtc.c | 101 +-- drivers/gpu/drm/exynos/exynos_drm_crtc.h |7 +- drivers/gpu/drm/exynos/exynos_drm_drv.c| 27 --- drivers/gpu/drm/exynos/exynos_drm_drv.h| 40 ++--- drivers/gpu/drm/exynos/exynos_drm_dsi.c|7 - drivers/gpu/drm/exynos/exynos_drm_fb.c | 10 +- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 251 --- drivers/gpu/drm/exynos/exynos_drm_fimd.h | 15 ++ drivers/gpu/drm/exynos/exynos_drm_ipp.c| 44 + drivers/gpu/drm/exynos/exynos_drm_plane.c | 78 +++-- drivers/gpu/drm/exynos/exynos_drm_plane.h |7 +- drivers/gpu/drm/exynos/exynos_drm_vidi.c | 136 --- drivers/gpu/drm/exynos/exynos_hdmi.c |2 +- drivers/gpu/drm/exynos/exynos_mixer.c | 260 drivers/gpu/drm/exynos/regs-mixer.h|2 +- include/video/samsung_fimd.h | 11 ++ 18 files changed, 495 insertions(+), 691 deletions(-) create mode 100644 drivers/gpu/drm/exynos/exynos_drm_fimd.h
[GIT PULL] exynos-drm-next for 3.20
Hi Dave, Sorry for late. This pull request was delayed by a review and a test to atomic pageflip/modeset patch series. As a result, this time we woudn't merge the patch series because they are not safe and have several bugs. Summary: - Add code cleanups and bug fixups. - Add a new display controller dirver, DECON which is a new display controller of Exynos7 SoC. This device is much different from FIMD of Exynos4 and Exynos4 SoC series. Kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 2f8997902e64951228385ca1cebb0d2f16f99a23: Merge tag 'drm-amdkfd-next-fixes-2015-02-03' of git://people.freedesktop.org/~gabbayo/linux into drm-next (2015-02-05 10:40:10 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to 96976c3d9aff4e1387c30f6356ac01fa6f72ef46: drm/exynos: Add DECON driver (2015-02-11 20:27:08 +0900) Ajay Kumar (1): drm/exynos: Add DECON driver Alban Browaeys (1): drm/exynos: fix no hdmi output Carlo Caione (1): drm/exynos: fix DMA_ATTR_NO_KERNEL_MAPPING usage Gustavo Padovan (1): drm/exynos: Remove exynos_plane_dpms() call with no effect Joonyoung Shim (7): drm/exynos: remove DRM_EXYNOS_DMABUF config drm/exynos: remove to use unnecessary MODULE_xxx macro drm/exynos: fix wrong pipe calculation for crtc drm/exynos: use driver internal struct drm/exynos: remove mode property of exynos crtc drm/exynos: remove exynos_plane_dpms drm/exynos: fix NULL pointer reference Marek Szyprowski (2): drm/exynos: add support for 'hdmi' clock drm/exynos: IOMMU support should not be selectable by user Seung-Woo Kim (1): drm/exynos: hdmi: replace fb size with mode size from win commit .../devicetree/bindings/video/exynos7-decon.txt| 68 ++ .../devicetree/bindings/video/exynos_mixer.txt |1 + drivers/gpu/drm/exynos/Kconfig | 24 +- drivers/gpu/drm/exynos/Makefile|4 +- drivers/gpu/drm/exynos/exynos7_drm_decon.c | 990 drivers/gpu/drm/exynos/exynos_dp_core.c| 14 +- drivers/gpu/drm/exynos/exynos_drm_buf.c|6 +- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 62 -- drivers/gpu/drm/exynos/exynos_drm_dmabuf.c |4 - drivers/gpu/drm/exynos/exynos_drm_dmabuf.h |5 - drivers/gpu/drm/exynos/exynos_drm_drv.c|4 + drivers/gpu/drm/exynos/exynos_drm_drv.h|9 +- drivers/gpu/drm/exynos/exynos_drm_encoder.c|2 +- drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 29 +- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 56 +- drivers/gpu/drm/exynos/exynos_drm_gem.h|2 + drivers/gpu/drm/exynos/exynos_drm_plane.c | 33 +- drivers/gpu/drm/exynos/exynos_drm_plane.h |1 - drivers/gpu/drm/exynos/exynos_drm_vidi.c | 23 +- drivers/gpu/drm/exynos/exynos_hdmi.c | 12 +- drivers/gpu/drm/exynos/exynos_mixer.c | 48 +- include/video/exynos7_decon.h | 349 +++ 22 files changed, 1520 insertions(+), 226 deletions(-) create mode 100644 Documentation/devicetree/bindings/video/exynos7-decon.txt create mode 100644 drivers/gpu/drm/exynos/exynos7_drm_decon.c create mode 100644 include/video/exynos7_decon.h
[GIT PULL] exynos-drm-next
Hi Dave, This pull request includes some code refactoring which removes Exynos specific structure names and uses generic structure names instead, and makes all plane updating to be done by only exynos_update_plane function. And also it includes some cleanup and fixup patches. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 281d1bbd34b734e4f22b30b6f3b673dda46a7470: Merge remote-tracking branch 'origin/master' into drm-next (2015-01-22 10:44:41 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to efa75bcdad59fc796152a4c73bb65ae2ab7ce035: drm/exynos: fimd: check error status for drm_iommu_attach_device (2015-01-25 21:28:09 +0900) Ajay Kumar (1): drm/exynos: fimd: check error status for drm_iommu_attach_device Gustavo Padovan (21): drm/exynos: move to_exynos_crtc() macro to main header drm/exynos: expose struct exynos_drm_crtc drm/exynos: remove exynos_drm_crtc_plane_* wrappers drm/exynos: remove struct exynos_drm_overlay drm/exynos/fimd: don't initialize 'ret' variable in fimd_probe() drm/exynos/vidi: remove useless ops->commit() drm/exynos: Don't touch DPMS when updating overlay planes drm/exynos: don't do any DPMS operation while updating planes drm/exynos: remove exynos_plane_commit() wrapper drm/exynos: unify plane update on exynos_update_plane() drm/exynos: call exynos_update_plane() directly on page flips drm/exynos: remove exynos_drm_crtc_mode_set_commit() drm/exynos: rename base object of struct exynos_drm_crtc to 'base' drm/exynos: add pipe param to exynos_drm_crtc_create() drm/exynos: remove pipe member of struct exynos_drm_manager drm/exynos: move 'type' from manager to crtc struct drm/exynos: remove drm_dev from struct exynos_drm_manager drm/exynos: remove struct exynos_drm_manager drm/exynos: don't duplicate drm_display_mode in fimd context drm/exynos: remove mode_set() ops from exynos_crtc drm/exynos: create exynos_check_plane() drivers/gpu/drm/exynos/exynos_drm_crtc.c | 185 +-- drivers/gpu/drm/exynos/exynos_drm_crtc.h |8 +- drivers/gpu/drm/exynos/exynos_drm_drv.h | 83 +++- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 196 ++--- drivers/gpu/drm/exynos/exynos_drm_plane.c | 138 ++-- drivers/gpu/drm/exynos/exynos_drm_plane.h | 17 ++- drivers/gpu/drm/exynos/exynos_drm_vidi.c | 135 +--- drivers/gpu/drm/exynos/exynos_mixer.c | 159 --- 8 files changed, 426 insertions(+), 495 deletions(-)
[GIT PULL] exynos-drm-next
Hi Dave, Add Exynos4415 SoC support, some fixups and cleanups. Summary: - Resolve kernel lockup issue incurred by probe request in probe context. . For this, it moves all register codes of sub drivers into init function and adds component binding support for vidi driver. - Add Exynos4415 SoC support. - Make each manager and display object to be embedded in each driver context. - Fix and clean up FIMD and MIPI-DSI drivers. - Clean up unnecesary or wrong descriptions. - And trivial cleanups. Please kindly let me know if there is my missing point. Thanks, Inki Dae The following changes since commit ed1e8777a56f3523712506d608a29f57ed37b613: Merge branch 'drm-next-3.19' of git://people.freedesktop.org/~agd5f/linux into drm-next (2014-11-21 12:17:43 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to 5baf5d44fbcde002d7f3f8148e69305f520770dd: drm/exynos: avoid leak if exynos_dpi_probe() fails (2014-11-25 11:58:43 +0900) Andrzej Hajda (19): drm/exynos: remove ifdeferry from initialization code drm/exynos: dsi: remove global variable exynos_dsi_display drm/exynos: dsi: simplify device pointer evaluation drm/exynos: dsi: remove redundant encoder field drm/exynos: dsi: stop using display->ctx pointer drm/exynos/mixer: embed manager into private context drm/exynos/mixer: stop using manager->ctx pointer drm/exynos/vidi: embed manager into private context drm/exynos/vidi: stop using manager->ctx pointer drm/exynos/fimd: embed manager into private context drm/exynos/fimd: stop using manager->ctx pointer drm/exynos/hdmi: embed display into private context drm/exynos/hdmi: stop using display->ctx pointer drm/exynos/vidi: embed display into private context drm/exynos/vidi: stop using display->ctx pointer drm/exynos/dp: embed display into private context drm/exynos/dp: stop using display->ctx pointer drm/exynos/dpi: embed display into private context drm/exynos/dpi: stop using display->ctx pointer Gustavo Padovan (13): drm/exynos: remove uneeded declaration of struct dma_iommu_mapping drm/exynos: remove extra declaration of struct exynos_drm_manager drm/exynos: remove extra declaration of struct exynos_overlay drm/exynos: Replace repeated declaration by include drm/exynos: Replace repeated declarations by #include "exynos_drm_drv.h" drm/exynos: remove unused wait_for macro drm/exynos: Save up space using bool var as bitfields drm/exynos: update documentation to reflect code changes drm/exynos: remove leftover hdmi function declarations Revert "drm/exynos: fix null pointer dereference issue" drm/exynos: move Exynos platform drivers registration to init drm/exynos: Fix exynos_dpi_remove() parameter drm/exynos: avoid leak if exynos_dpi_probe() fails Inki Dae (8): drm/exynos: resolve infinite loop issue on multi-platform drm/exynos: resolve infinite loop issue on non multi-platform drm/exynos: g2d: fix null pointer dereference drm/exynos: fix possible infinite loop issue drm/exynos: fix null pointer dereference issue drm/exynos: clean up machine compatible string check drm/exynos: fix exynos_drm_component_del drm/exynos: vidi: add component support Joonyoung Shim (3): drm/exynos: add has_vtsel flag drm/exynos: move triggering checking drm/exynos: use irq_flags instead of triggering Julia Lawall (1): drm/exynos/ipp: fix error return code Krzysztof Kozlowski (1): drm/exynos: Fix DSI resuming fail because power domain being off Vivek Gautam (1): drm/exynos: dp: Remove support for unused dptx-phy YoungJun Cho (12): drm/exynos: dsi: support Exynos4415 SoC drm/exynos: fimd: support Exynos4415 SoC drm/exynos: fimd: remove unnecessary waiting vblank routine drm/exynos: fimd: move handle vblank position in TE handler drm/exynos: dsi: move DSIM_STATE_ENABLED set position drm/exynos: fimd: move shadow unprotection position drm/exynos: fimd: add fimd_enable_video_output() to cleanup drm/exynos: fimd: add fimd_enable_shadow_channel_path() to cleanup drm/exynos: fimd: modify I80 i/f irq relevant routine drm/exynos: fimd: add triggering unset routine in fimd_trigger() drm/exynos: dsi: move TE irq handler registration position drm/exynos: dsi: set TE GPIO IRQ status as IRQ_NOAUTOEN .../devicetree/bindings/video/exynos_dsim.txt |1 + .../devicetree/bindings/video/samsung-fimd.txt |1 + drivers/gpu/drm/exynos/exynos_dp_core.c| 132 -- drivers/gpu/drm/exynos/exynos_dp_core.h|5 +-
[GIT PULL] exynos-drm-next
Hi Dave, This pull request includes i80 interface support, module auto-loading ipp consolidation, and trivail fixups and cleanups. Summary: - Add i80 interface support. For this, we added some features to Exynos drm framework, which don't affect any other SoC and common framework because they are specific to Exynos drm. - Add module auto-loading support. For this, sub drivers of Exynos drm exports their of match tables to userspace. This allows modules to be loaded automatically based on devicetree information - Consolidate ipp driver. This patch just just includes cleanups and a littl bit refactoring codes. If there is any problem, please kindly let me know. Thanks, Inki Dae The following changes since commit 08d645c181e9b9482c249e82a061c279a986db15: agp: remove read/write stubs (2014-08-02 06:43:51 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to ef7ce055a9e00f6376416466b996515a27b7cb31: drm/exynos: g2d: let exynos_g2d_get_ver_ioctl fail (2014-08-04 13:39:28 +0900) Alban Browaeys (1): drm/exynos: g2d: add exynos4212 as a compatible device. Andrzej Hajda (12): drm/exynos/ipp: remove type casting drm/exynos/ipp: remove unused field from exynos_drm_ipp_private drm/exynos/ipp: remove struct exynos_drm_ipp_private drm/exynos/ipp: correct address type drm/exynos/ipp: remove temporary variable drm/exynos/ipp: remove incorrect checks of list_first_entry result drm/exynos/ipp: simplify memory check function drm/exynos/ipp: remove useless registration checks drm/exynos/ipp: simplify ipp_find_obj drm/exynos/ipp: remove redundant messages drm/exynos/ipp: simplify ipp_create_id drm/exynos/ipp: simplify ipp_find_driver Jingoo Han (1): drm/exynos: dp: Use correct module license Joonyoung Shim (1): drm/exynos: control blending of mixer graphic layer 0 Krzysztof Kozlowski (1): drm/exynos: Fix NULL pointer exception when suspending without components Marek Szyprowski (2): drm/exynos: hdmi: make 'hdmi-en' regulator optional and keep it enabled drm/exynos: hdmi: enable exynos 4210 and 4x12 soc support Sachin Kamat (2): drm/exynos: Remove unused variable from exynos_hdmi.c drm/exynos: Remove unused variable in exynos_drm_gem.c Seung-Woo Kim (1): drm/exynos: hdmi: add null check for hdmiphy_port Sjoerd Simons (3): Subject: Revert "drm/exynos: fix module build error" Subject: Revert "drm/exynos: remove MODULE_DEVICE_TABLE definitions" drm/exynos: Add MODULE_DEVICE_TABLE entries for various components Tobias Jakobi (2): drm/exynos: g2d: make ioctls more robust drm/exynos: g2d: let exynos_g2d_get_ver_ioctl fail YoungJun Cho (12): drm/exynos: dsi: move the EoT packets configuration point drm/exynos: use wait_event_timeout() for safety usage ARM: dts: samsung-fimd: add LCD I80 interface specific properties drm/exynos: add TE handler to support LCD I80 interface drm/exynos: dsi: add TE interrupt handler to support LCD I80 interface drm/exynos: fimd: support LCD I80 interface ARM: dts: exynos_dsim: add exynos5410 compatible to DT bindings drm/exynos: dsi: add driver data to support Exynos5410/5420/5440 SoCs ARM: dts: exynos4: add system register property ARM: dts: exynos5: add system register property ARM: dts: exynos5420: add mipi-phy node ARM: dts: exynos5420: add dsi node .../devicetree/bindings/video/exynos_dsim.txt |4 +- .../devicetree/bindings/video/exynos_mixer.txt |5 +- .../devicetree/bindings/video/samsung-fimd.txt | 28 ++ arch/arm/boot/dts/exynos4.dtsi |1 + arch/arm/boot/dts/exynos5.dtsi |1 + arch/arm/boot/dts/exynos5420.dtsi | 20 ++ drivers/gpu/drm/exynos/Kconfig |1 + drivers/gpu/drm/exynos/exynos_dp_core.c|3 +- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 15 +- drivers/gpu/drm/exynos/exynos_drm_crtc.h |7 + drivers/gpu/drm/exynos/exynos_drm_drv.c|4 +- drivers/gpu/drm/exynos/exynos_drm_drv.h| 10 +- drivers/gpu/drm/exynos/exynos_drm_dsi.c| 270 +-- drivers/gpu/drm/exynos/exynos_drm_fimc.c |1 + drivers/gpu/drm/exynos/exynos_drm_fimd.c | 277 drivers/gpu/drm/exynos/exynos_drm_g2d.c| 29 +- drivers/gpu/drm/exynos/exynos_drm_gem.c|3 - drivers/gpu/drm/exynos/exynos_drm_ipp.c| 259 +- drivers/gpu/drm/exynos/exynos_drm_ipp.h|4 +- drivers/gpu/drm/exynos/exynos_drm_rotator.c|1 + drivers/gpu/drm/exynos/exynos_hdmi.c | 36
[GIT PULL] exynos-drm-next
Hi Dave, This pull request resolves hdmi dt broken issue, probe order and deferred probe issues, and consolidates hdmi and ipp drivers, and also includes fixups and cleanups. Summary: - Resolve probe order and deferred probe issue with component framework support. - Resolve hdmi dt broken issue. . HDMI DT support, which was broken since CCF (common clock framework) support, and considring legacy dt binding. - Consolidate HDMI part. . APB based phy support for Exynos5420 and later, and fixups related to power on/off sequence. - Consolidate IPP part. . Mostly bug fixups and code cleanups. - Trivial fixups and code cleanups. And we are now reviewing i80 LCD interface support (v3) for Exynos drm. So we may have pull-request one more time if the review could be completed within merge-window. If there is any problem, please kindly let me know. Thanks, Inki Dae The following changes since commit 182407a6ed5333fc37dd980a8de91a8f826a94f6: drm: add DP MST encoder type (2014-05-30 11:59:51 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to df5225bc9a87f1589a17797ee8e193608e4f3a9e: drm/exynos: consider deferred probe case (2014-06-02 14:29:39 +0900) Akshu Agrawal (1): drm/exynos: fimd: clear channel before enabling iommu Andrew Bresticker (1): drm/exynos: dp: support hotplug detection via GPIO Andrzej Hajda (13): drm/exynos: separate dpi from fimd drm/exynos/ipp: fix get_property IOCTL drm/exynos/ipp: correct ipp_id field initialization drm/exynos/ipp: simplify property list allocation drm/exynos/fimc: simplify pre-scaler ratio calculation drm/exynos/fimc: simplify irq masking function drm/exynos/fimc: replace hw access macros with functions drm/exynos/fimc: replace mutex by spinlock drm/exynos/fimc: simplify and rename fimc_dst_get_buf_seq drm/exynos: remove redundant mutex_unlock drm/exynos: add fimd dependency to fimd related encoders drm/exynos: ipp: remove description of non-existing field drm/exynos/fimd: allow multiplatform configuration Daniel Kurtz (3): drm/exynos/fbdev: don't set fix.smem/mmio_{start,len} drm/exynos/fbdev: don't set mode_config.fb_base drm/exynos: hdmi: remove unnecessary memset Inki Dae (8): drm/exynos: modify goto labels to meaningful names drm/exynos: add component framework support drm/exynos: dpi: fix hotplug fail issue drm/exynos: fix comment to exynos_drm_device_subdrv_prove call drm/exynos: remove unnecessary runtime pm interfaces drm/exynos: dsi: remove unnecessary pm interfaces drm/exynos: hdmi: consider legacy dt binding drm/exynos: consider deferred probe case Jean Delvare (1): drm/exynos: Fix PTN3460 dependency Jingoo Han (6): drm/exynos: fb: make local symbol static drm/exynos: hdmi: make local symbols static drm/exynos: dp: remove unnecessary OOM messages drm/exynos: rotator: add missing braces drm/exynos: dp: Use DPCD defines of drm_dp_helper.h drm/exynos: remove unnecessary exynos_hdmi.h file Joonyoung Shim (1): drm/exynos: remove DRIVER_HAVE_IRQ feature Paul Taysom (1): drm/exynos: check for null pointers in error handling Rahul Sharma (8): drm/exynos: replace hdmi reset with hdmi disable drm/exynos: remove unnecessary read for phy configuration values drm/exynos: add support for apb mapped phys in hdmi driver drm/exynos: enable support for exynos5420 hdmi device drm/exynos: allocate non-contigous buffers when iommu is enabled drm/exynos: use regmap interface to set hdmiphy control bit in pmu drm/exynos: use 4WORD dma burst length for small fbs drm/exynos: remove hardware overlays disable from fimd probe Sachin Kamat (5): drm/exynos: Staticize exynos_dpi_of_find_panel_node drm/exynos: Remove duplicate inclusion of i2c.h drm/exynos: Staticize local symbols in exynos_hdmi.c drm/exynos: Fix checkpatch warning in exynos_dp_reg.c drm/exynos: Use PTR_ERR_OR_ZERO in exynos_dp_core.c Sean Paul (3): drm/exynos: Don't reset hdmiphy on hdmi off drm/exynos: Debounce HDMI hotplug interrupts drm/exynos: Read hpd gpio in is_connected callback Seung-Woo Kim (1): drm/exynos: hdmi: remove unnecessary dedicated i2c drivers Shirish S (3): drm/exynos: update phy settings for RB resolutions drm/exynos: restore core HDMI settings drm/exynos: add hdmiphy power on/off sequence Takashi Iwai (1): drm/exynos: Fix double locks at PM resume YoungJun Cho (8): drm/exynos: ipp: remove usless list_empty() functions drm/exynos: ipp: remove duplicated setting drm/exynos: ipp: rename cmd_lock to lock drm/exynos: ipp: add
[GIT PULL] exynos-drm-next
2014-04-04 17:05 GMT+09:00, Tomasz Figa : > On 04.04.2014 09:48, Inki Dae wrote: >> >> >>> -Original Message- >>> From: Tomasz Figa [mailto:t.figa at samsung.com] >>> Sent: Friday, April 04, 2014 4:29 PM >>> To: Inki Dae; 'Tomasz Figa'; airlied at linux.ie; dri- >>> devel at lists.freedesktop.org; 'Marek Szyprowski'; >>> devicetree at vger.kernel.org; Grant Likely; Rob Herring >>> Subject: Re: [GIT PULL] exynos-drm-next >>> >>> On 04.04.2014 07:34, Inki Dae wrote: >>>> Hi Tomasz, >>>> >>>>> -Original Message- >>>>> From: Tomasz Figa [mailto:tomasz.figa at gmail.com] >>>>> Sent: Friday, April 04, 2014 2:00 PM >>>>> To: inki.dae at samsung.com; airlied at linux.ie; dri- >>>>> devel at lists.freedesktop.org >>>>> Subject: Re: [GIT PULL] exynos-drm-next >>>>> >>>>> Hi Inki, >>>>> >>>>> On 03.04.2014 19:34, inki.dae at samsung.com wrote: >>>>>> Hi Dave, >>>>>> Sorry for late. >>>>>> This pull request includes MIPI-DSI driver, two panel drivers, >>>>>> super device support, and relevant dt bindings. >>>>>> >>>>>> Summaries: >>>>>> - Add MIPI-DSI Driver, and dt bindigs >>>>>> - Add S6E8AA0 MIPI-DSI based panel drivers, and dt bindings >>>>>> - Add LD9040 parallel panel driver >>>>>> . this driver is placed in drivers/gpu/drm/panel, and it seems >>>>>>to be used for exynos drm as of now, >>>>>> - Add super device support, and dt bindings >>>>>> . this patch resolves the probe order issue to sub drivers >>>>>>without specific lists >>>>> >>>>> I don't think the DT bindings have been Acked by DT maintainers, >>>>> which is necessary to merge them. >>>>> >>>>> Also I believe more discussion is needed on this, but I didn't have >>>>> time to comment on this series yet. Please hold off with merging the >>>>> supernode series yet. >>>> >>>> I sent a email about review request to you but I didn't get any answer >>>> from you. >>> >>> It's been just three days ago and I just didn't find time yet to review >> >> No, the email was just ping. My original RFC patch series had been posted >> March 3, about 1 month ago, And for my official patch series, eight days >> ago. >> So the email I sent three days ago was just a ping that I requested for >> you >> to review the patch series. > > As I said, it was not even posted to samsung-soc, the central ML for > Samsung SoC related patches, as mandated by MAINTAINERS file. I learned > about its presence just after your ping. > >>> them. I would like to be able to review all the patches straight after >>> them being posted, but unfortunately that's not the only thing I have to >>> do. >>> >> >> So I think there was no any comments from you for a long time. >> >>> Anyway, a common practice in open source world is to let the patches >>> wait >>> on the mailing lists for two weeks for people to find some time to >>> review >>> them and only then apply. There might be people that don't work full >>> time >>> on this area, but still would be interested to do a review in some free >>> time. >>> >>> Also, neither version of this series have been posted to >>> linux-samsung-soc >>> mailing list, which is also a key to have a broader review. Note that >>> this >>> ML is listed in MAINTAINERS file for all kernel files with "exynos" in >>> name. >>> >>> ARM/S5P EXYNOS ARM ARCHITECTURES >>> M: Kukjin Kim >>> L: linux-arm-kernel at lists.infradead.org (moderated for >> non-subscribers) >>> L: linux-samsung-soc at vger.kernel.org (moderated for >>> non-subscribers) >>> S: Maintained >>> F: arch/arm/mach-s5p*/ >>> F: arch/arm/mach-exynos*/ >>> N: exynos >>> >>> >>>> And I think super node concept was already accepted, and relevant >>>> codes, component framework, has already been merged to mainline. And >>>> Linux staging next has already such dt bindings. Please see imx dts >>> files. >>> >>> Yes, they a
[GIT PULL] exynos-drm-next
> -Original Message- > From: Tomasz Figa [mailto:t.figa at samsung.com] > Sent: Friday, April 04, 2014 4:29 PM > To: Inki Dae; 'Tomasz Figa'; airlied at linux.ie; dri- > devel at lists.freedesktop.org; 'Marek Szyprowski'; > devicetree at vger.kernel.org; Grant Likely; Rob Herring > Subject: Re: [GIT PULL] exynos-drm-next > > On 04.04.2014 07:34, Inki Dae wrote: > > Hi Tomasz, > > > >> -Original Message- > >> From: Tomasz Figa [mailto:tomasz.figa at gmail.com] > >> Sent: Friday, April 04, 2014 2:00 PM > >> To: inki.dae at samsung.com; airlied at linux.ie; dri- > >> devel at lists.freedesktop.org > >> Subject: Re: [GIT PULL] exynos-drm-next > >> > >> Hi Inki, > >> > >> On 03.04.2014 19:34, inki.dae at samsung.com wrote: > >>> Hi Dave, > >>> Sorry for late. > >>> This pull request includes MIPI-DSI driver, two panel drivers, > >>> super device support, and relevant dt bindings. > >>> > >>> Summaries: > >>> - Add MIPI-DSI Driver, and dt bindigs > >>> - Add S6E8AA0 MIPI-DSI based panel drivers, and dt bindings > >>> - Add LD9040 parallel panel driver > >>> . this driver is placed in drivers/gpu/drm/panel, and it seems > >>> to be used for exynos drm as of now, > >>> - Add super device support, and dt bindings > >>> . this patch resolves the probe order issue to sub drivers > >>> without specific lists > >> > >> I don't think the DT bindings have been Acked by DT maintainers, > >> which is necessary to merge them. > >> > >> Also I believe more discussion is needed on this, but I didn't have > >> time to comment on this series yet. Please hold off with merging the > >> supernode series yet. > > > > I sent a email about review request to you but I didn't get any answer > > from you. > > It's been just three days ago and I just didn't find time yet to review No, the email was just ping. My original RFC patch series had been posted March 3, about 1 month ago, And for my official patch series, eight days ago. So the email I sent three days ago was just a ping that I requested for you to review the patch series. > them. I would like to be able to review all the patches straight after > them being posted, but unfortunately that's not the only thing I have to > do. > So I think there was no any comments from you for a long time. > Anyway, a common practice in open source world is to let the patches wait > on the mailing lists for two weeks for people to find some time to review > them and only then apply. There might be people that don't work full time > on this area, but still would be interested to do a review in some free > time. > > Also, neither version of this series have been posted to linux-samsung-soc > mailing list, which is also a key to have a broader review. Note that this > ML is listed in MAINTAINERS file for all kernel files with "exynos" in > name. > > ARM/S5P EXYNOS ARM ARCHITECTURES > M: Kukjin Kim > L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers) > L: linux-samsung-soc at vger.kernel.org (moderated for non-subscribers) > S: Maintained > F: arch/arm/mach-s5p*/ > F: arch/arm/mach-exynos*/ > N: exynos > > > > And I think super node concept was already accepted, and relevant > > codes, component framework, has already been merged to mainline. And > > Linux staging next has already such dt bindings. Please see imx dts > files. > > Yes, they are, but for other platforms not this particular instance. > > Any new DT bindings introduced are needed to have an ACK from one of DT > maintainers to be merged, unless you can't get any reply from any of them > for a longer time, usually 3 weeks from posting the series to be applied. So should I wait for more times? > > Of course standard pinging rules apply, so you should ping DT maintainers > first before applying such series. The email I sent to you three days ago was that. Thanks, Inki Dae > > > > > I hope this time this series would be merged to mainline so that we > > could go to next step, integrating drm_panel and drm_bridge framework > > to one integrated drm_bridge. So Can you hurry up to review it a bit? > > I'll wait for your ack. > > I don't think there is any need to hurry up with this particular series > for this release. I'd recommend sending a pull request with remaining > patches separately, as the supernode is not required to make anything work, > rather than being just a refactor. > > Best regards, > Tomasz
[GIT PULL] exynos-drm-next
Hi Tomasz, > -Original Message- > From: Tomasz Figa [mailto:tomasz.figa at gmail.com] > Sent: Friday, April 04, 2014 2:00 PM > To: inki.dae at samsung.com; airlied at linux.ie; dri- > devel at lists.freedesktop.org > Subject: Re: [GIT PULL] exynos-drm-next > > Hi Inki, > > On 03.04.2014 19:34, inki.dae at samsung.com wrote: > > Hi Dave, > > Sorry for late. > > This pull request includes MIPI-DSI driver, two panel drivers, > > super device support, and relevant dt bindings. > > > > Summaries: > > - Add MIPI-DSI Driver, and dt bindigs > > - Add S6E8AA0 MIPI-DSI based panel drivers, and dt bindings > > - Add LD9040 parallel panel driver > >. this driver is placed in drivers/gpu/drm/panel, and it seems > > to be used for exynos drm as of now, > > - Add super device support, and dt bindings > >. this patch resolves the probe order issue to sub drivers > > without specific lists > > I don't think the DT bindings have been Acked by DT maintainers, which is > necessary to merge them. > > Also I believe more discussion is needed on this, but I didn't have time > to comment on this series yet. Please hold off with merging the supernode > series yet. I sent a email about review request to you but I didn't get any answer from you. And I think super node concept was already accepted, and relevant codes, component framework, has already been merged to mainline. And Linux staging next has already such dt bindings. Please see imx dts files. I hope this time this series would be merged to mainline so that we could go to next step, integrating drm_panel and drm_bridge framework to one integrated drm_bridge. So Can you hurry up to review it a bit? I'll wait for your ack. Thanks, Inki Dae > > Best regards, > Tomasz
[RESEND][GIT PULL] exynos-drm-next
Hi Dave, I am re-sending git-pull request with fixing module build errors. For this, I reverted one patch, and added two patches below, - Revert 'drm/exynos: register platform driver at each kms sub drivers' . Exynos drm should be built as single module, so platform_driver_register of each sub driver should be called at exynos_drm_drv module. - Remove MODULE_DEVICE_TABLE definition of DP and MIPI-DSI drivers. - Export ptn3460_init function so that other modules can call this funtion. If there is any problem, please kindly let me know, Thanks, Inki Dae The following changes since commit 2844ea3f252331cc0ecf3ae74f6226db2f580f8a: Merge branch 'primary-plane' of git://people.freedesktop.org/~robclark/linux into drm-next (2014-04-02 12:09:09 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to 0c64ef98ac2c49452d4e269132c0474871a1fd93: drm/bridge: export ptn3460_init function (2014-04-04 12:14:51 +0900) Andrzej Hajda (16): drm/mipi_dsi: add flags to DSI messages drm/mipi_dsi: create dsi devices only for nodes with reg property drm/exynos: disallow fbdev initialization if no device is connected exynos/dsim: add DT bindings drm/exynos: add DSIM driver panel/s6e8aa0: add DT bindings panel/ld9040: add DT bindings drm/panel: add ld9040 driver ARM: dts: exynos4210-universal_c210: add proper panel node drm/panel: add S6E8AA0 driver ARM: dts: exynos4: add MIPI DSI Master node ARM: dts: exynos4210-trats: add panel node ARM: dts: exynos4412-trats2: add panel node ARM: dts: exynos4210-trats: enable exynos/fimd node ARM: dts: exynos4412-trats2: enable exynos/fimd node drm/exynos: separate dpi from fimd Inki Dae (8): drm/exynos: add super device support drm/exynos: dpi: fix hotplug fail issue ARM: dts: exynos4210-universal: add super device node for exynos drm ARM: dts: exynos4210-trats: add super device node for exynos drm ARM: dts: exynos4412-trats2: add super device node for exynos drm exynos/drm: add DT bindings drm/exynos: remove MODULE_DEVICE_TABLE definitions drm/bridge: export ptn3460_init function .../bindings/drm/exynos/samsung-exynos-drm.txt | 32 + .../devicetree/bindings/panel/samsung,ld9040.txt | 66 + .../devicetree/bindings/panel/samsung,s6e8aa0.txt | 56 + .../devicetree/bindings/video/exynos_dsim.txt | 80 + arch/arm/boot/dts/exynos4.dtsi | 14 + arch/arm/boot/dts/exynos4210-trats.dts | 66 + arch/arm/boot/dts/exynos4210-universal_c210.dts| 76 +- arch/arm/boot/dts/exynos4412-trats2.dts| 75 + drivers/gpu/drm/bridge/ptn3460.c |1 + drivers/gpu/drm/drm_mipi_dsi.c |6 +- drivers/gpu/drm/exynos/Kconfig |9 + drivers/gpu/drm/exynos/Makefile|1 + drivers/gpu/drm/exynos/exynos_dp_core.c| 46 +- drivers/gpu/drm/exynos/exynos_drm_core.c | 216 +-- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 17 + drivers/gpu/drm/exynos/exynos_drm_crtc.h |4 + drivers/gpu/drm/exynos/exynos_drm_dpi.c| 51 +- drivers/gpu/drm/exynos/exynos_drm_drv.c| 217 +-- drivers/gpu/drm/exynos/exynos_drm_drv.h| 65 +- drivers/gpu/drm/exynos/exynos_drm_dsi.c| 1556 drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 21 + drivers/gpu/drm/exynos/exynos_drm_fimd.c | 74 +- drivers/gpu/drm/exynos/exynos_drm_vidi.c | 61 +- drivers/gpu/drm/exynos/exynos_hdmi.c | 59 +- drivers/gpu/drm/exynos/exynos_mixer.c | 54 +- drivers/gpu/drm/panel/Kconfig | 14 + drivers/gpu/drm/panel/Makefile |2 + drivers/gpu/drm/panel/panel-ld9040.c | 376 + drivers/gpu/drm/panel/panel-s6e8aa0.c | 1069 ++ include/drm/drm_mipi_dsi.h |6 + 30 files changed, 3944 insertions(+), 446 deletions(-) create mode 100644 Documentation/devicetree/bindings/drm/exynos/samsung-exynos-drm.txt create mode 100644 Documentation/devicetree/bindings/panel/samsung,ld9040.txt create mode 100644 Documentation/devicetree/bindings/panel/samsung,s6e8aa0.txt create mode 100644 Documentation/devicetree/bindings/video/exynos_dsim.txt create mode 100644 drivers/gpu/drm/exynos/exynos_drm_dsi.c create mode 100644 drivers/gpu/drm/panel/panel-ld9040.c create mode 100644 drivers/gpu/drm/panel/panel-s6e8aa0.c
[GIT PULL] exynos-drm-next
On 04.04.2014 09:48, Inki Dae wrote: > > >> -Original Message- >> From: Tomasz Figa [mailto:t.figa at samsung.com] >> Sent: Friday, April 04, 2014 4:29 PM >> To: Inki Dae; 'Tomasz Figa'; airlied at linux.ie; dri- >> devel at lists.freedesktop.org; 'Marek Szyprowski'; >> devicetree at vger.kernel.org; Grant Likely; Rob Herring >> Subject: Re: [GIT PULL] exynos-drm-next >> >> On 04.04.2014 07:34, Inki Dae wrote: >>> Hi Tomasz, >>> >>>> -Original Message- >>>> From: Tomasz Figa [mailto:tomasz.figa at gmail.com] >>>> Sent: Friday, April 04, 2014 2:00 PM >>>> To: inki.dae at samsung.com; airlied at linux.ie; dri- >>>> devel at lists.freedesktop.org >>>> Subject: Re: [GIT PULL] exynos-drm-next >>>> >>>> Hi Inki, >>>> >>>> On 03.04.2014 19:34, inki.dae at samsung.com wrote: >>>>> Hi Dave, >>>>> Sorry for late. >>>>> This pull request includes MIPI-DSI driver, two panel drivers, >>>>> super device support, and relevant dt bindings. >>>>> >>>>> Summaries: >>>>> - Add MIPI-DSI Driver, and dt bindigs >>>>> - Add S6E8AA0 MIPI-DSI based panel drivers, and dt bindings >>>>> - Add LD9040 parallel panel driver >>>>> . this driver is placed in drivers/gpu/drm/panel, and it seems >>>>>to be used for exynos drm as of now, >>>>> - Add super device support, and dt bindings >>>>> . this patch resolves the probe order issue to sub drivers >>>>>without specific lists >>>> >>>> I don't think the DT bindings have been Acked by DT maintainers, >>>> which is necessary to merge them. >>>> >>>> Also I believe more discussion is needed on this, but I didn't have >>>> time to comment on this series yet. Please hold off with merging the >>>> supernode series yet. >>> >>> I sent a email about review request to you but I didn't get any answer >>> from you. >> >> It's been just three days ago and I just didn't find time yet to review > > No, the email was just ping. My original RFC patch series had been posted > March 3, about 1 month ago, And for my official patch series, eight days > ago. > So the email I sent three days ago was just a ping that I requested for you > to review the patch series. As I said, it was not even posted to samsung-soc, the central ML for Samsung SoC related patches, as mandated by MAINTAINERS file. I learned about its presence just after your ping. >> them. I would like to be able to review all the patches straight after >> them being posted, but unfortunately that's not the only thing I have to >> do. >> > > So I think there was no any comments from you for a long time. > >> Anyway, a common practice in open source world is to let the patches wait >> on the mailing lists for two weeks for people to find some time to review >> them and only then apply. There might be people that don't work full time >> on this area, but still would be interested to do a review in some free >> time. >> >> Also, neither version of this series have been posted to linux-samsung-soc >> mailing list, which is also a key to have a broader review. Note that this >> ML is listed in MAINTAINERS file for all kernel files with "exynos" in >> name. >> >> ARM/S5P EXYNOS ARM ARCHITECTURES >> M: Kukjin Kim >> L: linux-arm-kernel at lists.infradead.org (moderated for > non-subscribers) >> L: linux-samsung-soc at vger.kernel.org (moderated for non-subscribers) >> S: Maintained >> F: arch/arm/mach-s5p*/ >> F: arch/arm/mach-exynos*/ >> N: exynos >> >> >>> And I think super node concept was already accepted, and relevant >>> codes, component framework, has already been merged to mainline. And >>> Linux staging next has already such dt bindings. Please see imx dts >> files. >> >> Yes, they are, but for other platforms not this particular instance. >> >> Any new DT bindings introduced are needed to have an ACK from one of DT >> maintainers to be merged, unless you can't get any reply from any of them >> for a longer time, usually 3 weeks from posting the series to be applied. > > So should I wait for more times? > Since this series is not a dependency for any other patches queued for this release and it doesn't add any new functionality, I don't think there is any need to hurry with it. >> >> Of course standard pinging rules apply, so you should ping DT maintainers >> first before applying such series. > > > The email I sent to you three days ago was that. Unfortunately I'm not a DT maintainer, so I don't qualify here. You can see list of DT maintainers in MAINTAINERS file: OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS M: Rob Herring <robh+dt at kernel.org> M: Pawel Moll M: Mark Rutland M: Ian Campbell <ijc+devicetree at hellion.org.uk> M: Kumar Gala L: devicetree at vger.kernel.org S: Maintained F: Documentation/devicetree/ F: arch/*/boot/dts/ F: include/dt-bindings/ Best regards, Tomasz
[GIT PULL] exynos-drm-next
On 04.04.2014 07:34, Inki Dae wrote: > Hi Tomasz, > >> -Original Message- >> From: Tomasz Figa [mailto:tomasz.figa at gmail.com] >> Sent: Friday, April 04, 2014 2:00 PM >> To: inki.dae at samsung.com; airlied at linux.ie; dri- >> devel at lists.freedesktop.org >> Subject: Re: [GIT PULL] exynos-drm-next >> >> Hi Inki, >> >> On 03.04.2014 19:34, inki.dae at samsung.com wrote: >>> Hi Dave, >>> Sorry for late. >>> This pull request includes MIPI-DSI driver, two panel drivers, >>> super device support, and relevant dt bindings. >>> >>> Summaries: >>> - Add MIPI-DSI Driver, and dt bindigs >>> - Add S6E8AA0 MIPI-DSI based panel drivers, and dt bindings >>> - Add LD9040 parallel panel driver >>> . this driver is placed in drivers/gpu/drm/panel, and it seems >>> to be used for exynos drm as of now, >>> - Add super device support, and dt bindings >>> . this patch resolves the probe order issue to sub drivers >>> without specific lists >> >> I don't think the DT bindings have been Acked by DT maintainers, which is >> necessary to merge them. >> >> Also I believe more discussion is needed on this, but I didn't have time >> to comment on this series yet. Please hold off with merging the supernode >> series yet. > > I sent a email about review request to you but I didn't get any answer from > you. It's been just three days ago and I just didn't find time yet to review them. I would like to be able to review all the patches straight after them being posted, but unfortunately that's not the only thing I have to do. Anyway, a common practice in open source world is to let the patches wait on the mailing lists for two weeks for people to find some time to review them and only then apply. There might be people that don't work full time on this area, but still would be interested to do a review in some free time. Also, neither version of this series have been posted to linux-samsung-soc mailing list, which is also a key to have a broader review. Note that this ML is listed in MAINTAINERS file for all kernel files with "exynos" in name. ARM/S5P EXYNOS ARM ARCHITECTURES M: Kukjin Kim L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers) L: linux-samsung-soc at vger.kernel.org (moderated for non-subscribers) S: Maintained F: arch/arm/mach-s5p*/ F: arch/arm/mach-exynos*/ N: exynos > And I think super node concept was already accepted, and relevant > codes, component framework, has already been merged to mainline. And Linux > staging next has already such dt bindings. Please see imx dts files. Yes, they are, but for other platforms not this particular instance. Any new DT bindings introduced are needed to have an ACK from one of DT maintainers to be merged, unless you can't get any reply from any of them for a longer time, usually 3 weeks from posting the series to be applied. Of course standard pinging rules apply, so you should ping DT maintainers first before applying such series. > > I hope this time this series would be merged to mainline so that we could go > to next step, integrating drm_panel and drm_bridge framework to one > integrated drm_bridge. So Can you hurry up to review it a bit? I'll wait for > your ack. I don't think there is any need to hurry up with this particular series for this release. I'd recommend sending a pull request with remaining patches separately, as the supernode is not required to make anything work, rather than being just a refactor. Best regards, Tomasz
[GIT PULL] exynos-drm-next
Hi Inki, On 03.04.2014 19:34, inki.dae at samsung.com wrote: > Hi Dave, > Sorry for late. > This pull request includes MIPI-DSI driver, two panel drivers, > super device support, and relevant dt bindings. > > Summaries: > - Add MIPI-DSI Driver, and dt bindigs > - Add S6E8AA0 MIPI-DSI based panel drivers, and dt bindings > - Add LD9040 parallel panel driver >. this driver is placed in drivers/gpu/drm/panel, and it seems > to be used for exynos drm as of now, > - Add super device support, and dt bindings >. this patch resolves the probe order issue to sub drivers > without specific lists I don't think the DT bindings have been Acked by DT maintainers, which is necessary to merge them. Also I believe more discussion is needed on this, but I didn't have time to comment on this series yet. Please hold off with merging the supernode series yet. Best regards, Tomasz
[GIT PULL] exynos-drm-next
Hi Dave, Sorry for late. This pull request includes MIPI-DSI driver, two panel drivers, super device support, and relevant dt bindings. Summaries: - Add MIPI-DSI Driver, and dt bindigs - Add S6E8AA0 MIPI-DSI based panel drivers, and dt bindings - Add LD9040 parallel panel driver . this driver is placed in drivers/gpu/drm/panel, and it seems to be used for exynos drm as of now, - Add super device support, and dt bindings . this patch resolves the probe order issue to sub drivers without specific lists - Some fixups If there is any problem, please kindly let me know. Thanks, Inki Dae The following changes since commit 2844ea3f252331cc0ecf3ae74f6226db2f580f8a: Merge branch 'primary-plane' of git://people.freedesktop.org/~robclark/linux into drm-next (2014-04-02 12:09:09 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next for you to fetch changes up to a4521cbc01a711e78e22155885f991bcb96496de: drm/exynos: separate dpi from fimd (2014-04-04 02:22:16 +0900) Andrzej Hajda (16): drm/mipi_dsi: add flags to DSI messages drm/mipi_dsi: create dsi devices only for nodes with reg property drm/exynos: disallow fbdev initialization if no device is connected exynos/dsim: add DT bindings drm/exynos: add DSIM driver panel/s6e8aa0: add DT bindings panel/ld9040: add DT bindings drm/panel: add ld9040 driver ARM: dts: exynos4210-universal_c210: add proper panel node drm/panel: add S6E8AA0 driver ARM: dts: exynos4: add MIPI DSI Master node ARM: dts: exynos4210-trats: add panel node ARM: dts: exynos4412-trats2: add panel node ARM: dts: exynos4210-trats: enable exynos/fimd node ARM: dts: exynos4412-trats2: enable exynos/fimd node drm/exynos: separate dpi from fimd Inki Dae (7): drm/exynos: add super device support drm/exynos: dpi: fix hotplug fail issue drm/exynos: register platform driver at each kms sub drivers ARM: dts: exynos4210-universal: add super device node for exynos drm ARM: dts: exynos4210-trats: add super device node for exynos drm ARM: dts: exynos4412-trats2: add super device node for exynos drm exynos/drm: add DT bindings .../bindings/drm/exynos/samsung-exynos-drm.txt | 32 + .../devicetree/bindings/panel/samsung,ld9040.txt | 66 + .../devicetree/bindings/panel/samsung,s6e8aa0.txt | 56 + .../devicetree/bindings/video/exynos_dsim.txt | 80 + arch/arm/boot/dts/exynos4.dtsi | 14 + arch/arm/boot/dts/exynos4210-trats.dts | 66 + arch/arm/boot/dts/exynos4210-universal_c210.dts| 76 +- arch/arm/boot/dts/exynos4412-trats2.dts| 75 + drivers/gpu/drm/drm_mipi_dsi.c |6 +- drivers/gpu/drm/exynos/Kconfig |9 + drivers/gpu/drm/exynos/Makefile|1 + drivers/gpu/drm/exynos/exynos_dp_core.c| 46 +- drivers/gpu/drm/exynos/exynos_drm_core.c | 216 +-- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 17 + drivers/gpu/drm/exynos/exynos_drm_crtc.h |4 + drivers/gpu/drm/exynos/exynos_drm_dpi.c| 51 +- drivers/gpu/drm/exynos/exynos_drm_drv.c| 243 ++- drivers/gpu/drm/exynos/exynos_drm_drv.h| 69 +- drivers/gpu/drm/exynos/exynos_drm_dsi.c| 1558 drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 21 + drivers/gpu/drm/exynos/exynos_drm_fimd.c | 75 +- drivers/gpu/drm/exynos/exynos_drm_vidi.c | 61 +- drivers/gpu/drm/exynos/exynos_hdmi.c | 60 +- drivers/gpu/drm/exynos/exynos_mixer.c | 55 +- drivers/gpu/drm/panel/Kconfig | 14 + drivers/gpu/drm/panel/Makefile |2 + drivers/gpu/drm/panel/panel-ld9040.c | 376 + drivers/gpu/drm/panel/panel-s6e8aa0.c | 1069 ++ include/drm/drm_mipi_dsi.h |6 + 29 files changed, 3929 insertions(+), 495 deletions(-) create mode 100644 Documentation/devicetree/bindings/drm/exynos/samsung-exynos-drm.txt create mode 100644 Documentation/devicetree/bindings/panel/samsung,ld9040.txt create mode 100644 Documentation/devicetree/bindings/panel/samsung,s6e8aa0.txt create mode 100644 Documentation/devicetree/bindings/video/exynos_dsim.txt create mode 100644 drivers/gpu/drm/exynos/exynos_drm_dsi.c create mode 100644 drivers/gpu/drm/panel/panel-ld9040.c create mode 100644 drivers/gpu/drm/panel/panel-s6e8aa0.c
[GIT PULL] exynos-drm-next
Hi Dave, This pull request includes some features and big changes for 3.15. Highlights -- Re-factoring works over the exynos drm framework. - drm_crtc, drm_encoder/drm_connector are implemented by sub drivers directly. - Removing pm interfaces from each sub driver, and implementing them at top level of exynos drm. Add DisplayPort Transmitter driver. - Just moving existing driver from drivers/vides/exynos into drivers/gpu/drm/exynos. Add new LVDS bridge driver, PTN3460. - Placed in drivers/gpu/drm/bridge, and this device is used to transfer image signal from DP(DisplayPort) to LVDS Panel. So this driver will be used with DP driver moved into exynos drm. Add parallel panel support - With the re-factoring patch series, existing parallel panel support was broken by moving exynos_drm_display ops into each real connector driver, DP. So this patch series adds a new parallel panel module, exynos_drm_dpi, for supporting parallel panel, and also adds relevant bindings. Some fixups and cleanups. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit e84c20aff1ce7493bce26b75f1db363bb3f05979: drm/radeon/kms: merge conflicted badly (2014-03-20 11:09:10 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to ec6f53d3115258a4af6b7f4f07173a8336bad785: drm/exynos: fimd: remove unused variable (2014-03-21 15:12:10 +0900) Andrzej Hajda (7): drm/exynos: delay fbdev initialization until an output is connected drm/exynos: init kms poll after creation of connectors drm/exynos: correct timing porch conversion exynos/fimd: add parallel output related bindings drm/exynos: restore parallel output interface support ARM: dts: exynos4210-universal: add exynos/fimd node drm/exynos: fimd: remove unused variable Daniel Kurtz (2): drm/exynos: Fix (more) freeing issues in exynos_drm_drv.c drm/exynos: hdmi: remove the i2c drivers and use Inki Dae (3): drm/exynos: hdmi: consider APB PHY drm/exynos: hdmi: use i2c_adapter instead of i2c_client drm/exynos: fix unnecessary resource cleanup Sean Paul (30): drm/exynos: Merge overlay_ops into manager_ops drm/exynos: Add an initialize function to manager and display drm/exynos: Use manager_op initialize in fimd drm/exynos: hdmi: Implement initialize op for hdmi drm/exynos: Pass exynos_drm_manager in manager ops instead of dev drm/exynos: Remove apply manager callback drm/exynos: Remove dpms link between encoder/connector drm/exynos: Rename display_op power_on to dpms drm/exynos: Don't keep dpms state in encoder drm/exynos: Use unsigned long for possible_crtcs drm/exynos: Split manager/display/subdrv drm/exynos: Remove exynos_drm_hdmi shim drm/exynos: Use drm_mode_copy to copy modes drm/exynos: Disable unused crtc planes from crtc drm/exynos: Add mode_set manager operation drm/exynos: Implement mode_fixup manager operation drm/exynos: Use mode_set to configure fimd drm/exynos: Remove unused/useless fimd_context members drm/exynos: Move dp driver from video/ to drm/ drm/exynos: Move display implementation into dp drm/exynos: Implement dpms display callback in DP drm/exynos: Clean up FIMD power on/off routines drm/exynos: Consolidate suspend/resume in drm_drv drm/exynos: Add create_connector callback drm/exynos: Implement drm_connector in hdmi directly drm/exynos: Implement drm_connector directly in dp driver drm/exynos: Implement drm_connector directly in vidi driver drm/bridge: Add PTN3460 bridge driver drm/exynos: Implement lvds bridge discovery to DP driver drm/exynos: Remove the exynos_drm_connector shim Shirish S (2): drm/exynos: add phy settings for RB resolutions drm/exynos: set the active aspect ratio as per mode Stephane Marchesin (1): drm/exynos: Remove useless slab.h include .../devicetree/bindings/drm/bridge/ptn3460.txt | 27 + .../devicetree/bindings/video/exynos_dp.txt| 17 + .../devicetree/bindings/video/exynos_hdmi.txt |5 + .../devicetree/bindings/video/samsung-fimd.txt | 17 + MAINTAINERS|6 - arch/arm/boot/dts/exynos4210-universal_c210.dts| 27 + drivers/gpu/drm/Kconfig|2 + drivers/gpu/drm/Makefile |1 + drivers/gpu/drm/bridge/Kconfig |4 + drivers/gpu/drm/bridge/Makefile|3 + drivers/gpu/drm/bridge/ptn3460.c | 349 ++ drivers/gpu/drm/exynos/Kconfig | 15 +
[GIT PULL] exynos-drm-next for 3.13
Hi Dave, This pull request adds an anon file for exynos specific mmaper to resolve potential a dead lock issue pointed out by Al Viro, and fixes build break of drm-next. For this, I had already reported it to you. Please see below link, http://www.spinics.net/lists/dri-devel/msg50922.html In addition, we have a big refactoring patch series being reviewed in exynos-drm-next-todo branch yet, and we are wait for next version of the patch series. So I will request git-pull one more time if posted at a good time. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit fe3c703c3d80bd4c2da0d47a7d56930926af7cbc: drm/dp: Clarify automated test constant and add constant for FAUX test pattern (2013-12-18 11:47:43 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-next for you to fetch changes up to 8dd9ad5d3bf4759399e0c716dd065e7d90eee102: drm/exynos: fix build error caused by removed drm core macros (2014-01-07 16:53:25 +0900) Inki Dae (1): drm/exynos: use a new anon file for exynos gem mmaper Seung-Woo Kim (1): drm/exynos: fix build error caused by removed drm core macros drivers/gpu/drm/exynos/exynos_drm_drv.c | 21 + drivers/gpu/drm/exynos/exynos_drm_drv.h |1 + drivers/gpu/drm/exynos/exynos_drm_fimd.c |4 +- drivers/gpu/drm/exynos/exynos_drm_gem.c | 74 ++ drivers/gpu/drm/exynos/exynos_drm_gem.h |3 ++ 5 files changed, 40 insertions(+), 63 deletions(-)