dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 110659] pageflipping seems to cause jittering on mouse input when running Hitman 2 in Wine/DXVK with amdgpu.dc=1
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=110659 --- Comment #84 from Andrew Eikum <aeikum(a)codeweavers.com> --- If one call every five seconds is causing a problem, surely it's not Wine's bug, right? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[PATCH 0/4] drm/bridge: dw-hdmi: Add support for HDR metadata
by Jonas Karlman 18 Sep '19

18 Sep '19

Add support for HDR metadata using the hdr_output_metadata connector property, configure Dynamic Range and Mastering InfoFrame accordingly. A drm_infoframe flag is added to dw_hdmi_plat_data that platform drivers can use to signal when Dynamic Range and Mastering infoframes is supported. This flag is needed because Amlogic GXBB and GXL report same DW-HDMI version, and only GXL support DRM InfoFrame. The first patch add functionality to configure DRM InfoFrame based on the hdr_output_metadata connector property. The remaining patches sets the drm_infoframe flag on some SoCs supporting Dynamic Range and Mastering InfoFrame. Note that this was based on top of drm-misc-next and Neil Armstrong's "drm/meson: Add support for HDMI2.0 YUV420 4k60" series at [1] [1] https://patchwork.freedesktop.org/series/58725/#rev2 Jonas Karlman (4): drm/bridge: dw-hdmi: Add Dynamic Range and Mastering InfoFrame support drm/rockchip: Enable DRM InfoFrame support on RK3328 and RK3399 drm/meson: Enable DRM InfoFrame support on GXL, GXM and G12A drm/sun4i: Enable DRM InfoFrame support on H6 drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 109 ++++++++++++++++++++ drivers/gpu/drm/bridge/synopsys/dw-hdmi.h | 37 +++++++ drivers/gpu/drm/meson/meson_dw_hdmi.c | 5 + drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 2 + drivers/gpu/drm/sun4i/sun8i_dw_hdmi.c | 2 + drivers/gpu/drm/sun4i/sun8i_dw_hdmi.h | 1 + include/drm/bridge/dw_hdmi.h | 1 + 7 files changed, 157 insertions(+) -- 2.17.1

8 28

[radeon-alex:amd-mainline-dkms-5.0 3697/3724] drivers/gpu/drm/ttm/ttm_bo_util.c:274:48: error: too many arguments to function 'kmap_atomic_prot'
by kbuild test robot 18 Sep '19

18 Sep '19

tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.0 head: a51a5ad4b8daf0dd0a437d51a19c2baa98953675 commit: f460c248a3f0bca3a875602cf40693de672485c4 [3697/3724] drm/amd/autoconf: refactor dma_fence header check config: i386-allmodconfig (attached as .config) compiler: gcc-7 (Debian 7.4.0-13) 7.4.0 reproduce: git checkout f460c248a3f0bca3a875602cf40693de672485c4 # save the attached .config to linux build tree make ARCH=i386 If you fix the issue, kindly add following tag Reported-by: kbuild test robot <lkp(a)intel.com> All errors (new ones prefixed by >>): from include/drm/drmP.h:37, from include/kcl/kcl_drm.h:6, from drivers/gpu/drm/ttm/backport/backport.h:6, from <command-line>:0: include/linux/mm.h:610:21: note: previous definition of 'kvzalloc' was here static inline void *kvzalloc(size_t size, gfp_t flags) ^~~~~~~~ In file included from drivers/gpu/drm/ttm/backport/backport.h:12:0, from <command-line>:0: include/kcl/kcl_mm.h:74:20: error: static declaration of 'kvfree' follows non-static declaration static inline void kvfree(const void *addr) ^~~~~~ In file included from include/linux/scatterlist.h:8:0, from include/linux/dma-mapping.h:11, from include/drm/drmP.h:37, from include/kcl/kcl_drm.h:6, from drivers/gpu/drm/ttm/backport/backport.h:6, from <command-line>:0: include/linux/mm.h:630:13: note: previous declaration of 'kvfree' was here extern void kvfree(const void *addr); ^~~~~~ In file included from drivers/gpu/drm/ttm/backport/backport.h:12:0, from <command-line>:0: include/kcl/kcl_mm.h:94:21: error: redefinition of 'kvmalloc_array' static inline void *kvmalloc_array(size_t n, size_t size, gfp_t flags) ^~~~~~~~~~~~~~ In file included from include/linux/scatterlist.h:8:0, from include/linux/dma-mapping.h:11, from include/drm/drmP.h:37, from include/kcl/kcl_drm.h:6, from drivers/gpu/drm/ttm/backport/backport.h:6, from <command-line>:0: include/linux/mm.h:615:21: note: previous definition of 'kvmalloc_array' was here static inline void *kvmalloc_array(size_t n, size_t size, gfp_t flags) ^~~~~~~~~~~~~~ In file included from drivers/gpu/drm/ttm/backport/backport.h:12:0, from <command-line>:0: include/kcl/kcl_mm.h:107:21: error: redefinition of 'kvcalloc' static inline void *kvcalloc(size_t n, size_t size, gfp_t flags) ^~~~~~~~ In file included from include/linux/scatterlist.h:8:0, from include/linux/dma-mapping.h:11, from include/drm/drmP.h:37, from include/kcl/kcl_drm.h:6, from drivers/gpu/drm/ttm/backport/backport.h:6, from <command-line>:0: include/linux/mm.h:625:21: note: previous definition of 'kvcalloc' was here static inline void *kvcalloc(size_t n, size_t size, gfp_t flags) ^~~~~~~~ In file included from drivers/gpu/drm/ttm/backport/backport.h:12:0, from <command-line>:0: include/kcl/kcl_mm.h:114:20: error: redefinition of 'mmgrab' static inline void mmgrab(struct mm_struct *mm) ^~~~~~ In file included from include/kcl/kcl_mm.h:6:0, from drivers/gpu/drm/ttm/backport/backport.h:12, from <command-line>:0: include/linux/sched/mm.h:34:20: note: previous definition of 'mmgrab' was here static inline void mmgrab(struct mm_struct *mm) ^~~~~~ In file included from drivers/gpu/drm/ttm/backport/backport.h:13:0, from <command-line>:0: include/kcl/kcl_list.h:6:20: error: redefinition of 'list_bulk_move_tail' static inline void list_bulk_move_tail(struct list_head *head, ^~~~~~~~~~~~~~~~~~~ In file included from include/linux/wait.h:7:0, from include/linux/dma-fence.h:25, from include/kcl/kcl_fence.h:9, from drivers/gpu/drm/ttm/backport/backport.h:5, from <command-line>:0: include/linux/list.h:195:20: note: previous definition of 'list_bulk_move_tail' was here static inline void list_bulk_move_tail(struct list_head *head, ^~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/ttm/ttm_bo_util.c: In function 'ttm_kmap_atomic_prot': drivers/gpu/drm/ttm/ttm_bo_util.c:265:57: error: 'KM_USER0' undeclared (first use in this function); did you mean 'SI_USER'? #define __kcl__kmap_atomic(__page) kmap_atomic(__page, KM_USER0) ^ drivers/gpu/drm/ttm/ttm_bo_util.c:303:10: note: in expansion of macro '__kcl__kmap_atomic' return __kcl__kmap_atomic(page); ^~~~~~~~~~~~~~~~~~ drivers/gpu/drm/ttm/ttm_bo_util.c:265:57: note: each undeclared identifier is reported only once for each function it appears in #define __kcl__kmap_atomic(__page) kmap_atomic(__page, KM_USER0) ^ drivers/gpu/drm/ttm/ttm_bo_util.c:303:10: note: in expansion of macro '__kcl__kmap_atomic' return __kcl__kmap_atomic(page); ^~~~~~~~~~~~~~~~~~ drivers/gpu/drm/ttm/ttm_bo_util.c:265:37: error: too many arguments to function 'kmap_atomic' #define __kcl__kmap_atomic(__page) kmap_atomic(__page, KM_USER0) ^ drivers/gpu/drm/ttm/ttm_bo_util.c:303:10: note: in expansion of macro '__kcl__kmap_atomic' return __kcl__kmap_atomic(page); ^~~~~~~~~~~~~~~~~~ In file included from include/linux/highmem.h:35:0, from include/drm/drmP.h:40, from include/kcl/kcl_drm.h:6, from drivers/gpu/drm/ttm/backport/backport.h:6, from <command-line>:0: arch/x86/include/asm/highmem.h:68:7: note: declared here void *kmap_atomic(struct page *page); ^~~~~~~~~~~ >> drivers/gpu/drm/ttm/ttm_bo_util.c:274:48: error: too many arguments to function 'kmap_atomic_prot' #define __ttm_kmap_atomic_prot(__page, __prot) kmap_atomic_prot(__page, KM_USER0, __prot) ^ drivers/gpu/drm/ttm/ttm_bo_util.c:305:10: note: in expansion of macro '__ttm_kmap_atomic_prot' return __ttm_kmap_atomic_prot(page, prot); ^~~~~~~~~~~~~~~~~~~~~~ In file included from include/linux/highmem.h:35:0, from include/drm/drmP.h:40, from include/kcl/kcl_drm.h:6, from drivers/gpu/drm/ttm/backport/backport.h:6, from <command-line>:0: arch/x86/include/asm/highmem.h:67:7: note: declared here void *kmap_atomic_prot(struct page *page, pgprot_t prot); ^~~~~~~~~~~~~~~~ drivers/gpu/drm/ttm/ttm_bo_util.c: In function 'ttm_kunmap_atomic_prot': drivers/gpu/drm/ttm/ttm_bo_util.c:319:28: error: macro "kunmap_atomic" passed 2 arguments, but takes just 1 __kcl__kunmap_atomic(addr); ^ drivers/gpu/drm/ttm/ttm_bo_util.c:266:39: error: 'kunmap_atomic' undeclared (first use in this function); did you mean '__kunmap_atomic'? #define __kcl__kunmap_atomic(__addr) kunmap_atomic(__addr, KM_USER0) ^ drivers/gpu/drm/ttm/ttm_bo_util.c:319:3: note: in expansion of macro '__kcl__kunmap_atomic' __kcl__kunmap_atomic(addr); ^~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/ttm/ttm_bo_util.c:321:27: error: macro "kunmap_atomic" passed 2 arguments, but takes just 1 __ttm_kunmap_atomic(addr); ^ drivers/gpu/drm/ttm/ttm_bo_util.c: In function 'ttm_kmap_atomic_prot': drivers/gpu/drm/ttm/ttm_bo_util.c:306:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ cc1: some warnings being treated as errors vim +/kmap_atomic_prot +274 drivers/gpu/drm/ttm/ttm_bo_util.c b479b92eb4e442 Yifan Zhang 2019-08-20 271 b479b92eb4e442 Yifan Zhang 2019-08-20 272 #ifdef CONFIG_X86 b479b92eb4e442 Yifan Zhang 2019-08-20 273 #if !defined(HAVE_KMAP_ATOMIC_ONE_ARG) b479b92eb4e442 Yifan Zhang 2019-08-20 @274 #define __ttm_kmap_atomic_prot(__page, __prot) kmap_atomic_prot(__page, KM_USER0, __prot) b479b92eb4e442 Yifan Zhang 2019-08-20 275 #define __ttm_kunmap_atomic(__addr) kunmap_atomic(__addr, KM_USER0) b479b92eb4e442 Yifan Zhang 2019-08-20 276 #else 403c1826a45644 Thomas Hellstrom 2018-01-16 277 #define __ttm_kunmap_atomic(__addr) kunmap_atomic(__addr) b479b92eb4e442 Yifan Zhang 2019-08-20 278 #define __ttm_kmap_atomic_prot(__page, __prot) kmap_atomic_prot(__page, __prot) 8c8a8e4c4df8cb Kevin Wang 2018-08-17 279 #endif 403c1826a45644 Thomas Hellstrom 2018-01-16 280 #else 403c1826a45644 Thomas Hellstrom 2018-01-16 281 #define __ttm_kmap_atomic_prot(__page, __prot) vmap(&__page, 1, 0, __prot) 403c1826a45644 Thomas Hellstrom 2018-01-16 282 #define __ttm_kunmap_atomic(__addr) vunmap(__addr) 403c1826a45644 Thomas Hellstrom 2018-01-16 283 #endif 403c1826a45644 Thomas Hellstrom 2018-01-16 284 9c11fcf1a74d33 Thomas Hellstrom 2018-01-16 285 :::::: The code at line 274 was first introduced by commit :::::: b479b92eb4e442ba59ebb9bcbbee4e02fdd9ac56 drm/amd/autoconf: test if kmap_atomic() has one argument :::::: TO: Yifan Zhang <yifan1.zhang(a)amd.com> :::::: CC: Yifan Zhang <yifan1.zhang(a)amd.com> --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation

1 0

[Bug 109574] Blender 2.8
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

1 0

[PATCH v6 0/8] add driver for "boe, tv101wum-nl6", "boe, tv101wum-n53", "auo, kd101n80-45na" and "auo, b101uan08.3" panels
by Jitao Shi 18 Sep '19

18 Sep '19

Changes since v5: - covert the documents to yaml - fine tune boe, tv101wum-n53 panel video timine Changes since v4: - add auo,b101uan08.3 panel for this driver. - add boe,tv101wum-n53 panel for this driver. Changes since v3: - remove check enable_gpio. - fine tune the auo,kd101n80-45na panel's power on timing. Changes since v2: - correct the panel size - remove blank line in Kconfig - move auo,kd101n80-45na panel driver in this series. Changes since v1: - update typo nl6 -> n16. - update new panel config and makefile are added in alphabetically order. - add the panel mode and panel info in driver data. - merge auo,kd101n80-45a and boe,tv101wum-nl6 in one driver Jitao Shi (8): dt-bindings: display: panel: Add BOE tv101wum-n16 panel bindings drm/panel: support for BOE tv101wum-nl6 wuxga dsi video mode panel dt-bindings: display: panel: add auo kd101n80-45na panel bindings drm/panel: support for auo,kd101n80-45na wuxga dsi video mode panel dt-bindings: display: panel: add boe tv101wum-n53 panel documentation drm/panel: support for boe,tv101wum-n53 wuxga dsi video mode panel dt-bindings: display: panel: add AUO auo,b101uan08.3 panel documentation drm/panel: support for auo,b101uan08.3 wuxga dsi video mode panel .../display/panel/auo,b101uan08.3.yaml | 67 ++ .../display/panel/auo,kd101n80-45na.yaml | 67 ++ .../display/panel/boe,tv101wum-n53.yaml | 67 ++ .../display/panel/boe,tv101wum-nl6.yaml | 67 ++ drivers/gpu/drm/panel/Kconfig | 9 + drivers/gpu/drm/panel/Makefile | 1 + .../gpu/drm/panel/panel-boe-tv101wum-nl6.c | 876 ++++++++++++++++++ 7 files changed, 1154 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/panel/auo,b101uan08.3.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/auo,kd101n80-45na.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/boe,tv101wum-n53.yaml create mode 100644 Documentation/devicetree/bindings/display/panel/boe,tv101wum-nl6.yaml create mode 100644 drivers/gpu/drm/panel/panel-boe-tv101wum-nl6.c -- 2.21.0

2 9

DRM Driver implementation question
by Gareth Williams 18 Sep '19

18 Sep '19

Hi Laurent/Kieran, I need to upstream a driver for a display controller that within its registers memory region contains registers related to a PWM device. The PWM device is for controlling the backlight of the display. Ideally, I would like to create a separated driver for the PWM, so that I can re-use "pwm-backlight", but since the registers for the PWM are right in the middle of the registers for the display controller I would need to ioremap the memory region for the PWM registers region twice, once from the display controller driver, and once from the PWM driver. Do you think that the double ioremap would be acceptable upstream? Kind Regards, Gareth

3 4

[PULL] drm-misc-next-fixes
by Maxime Ripard 18 Sep '19

18 Sep '19

Hi Dave, Daniel, Here is a drm-misc-next-fixes PR, with two fixes that should go in this current merge window. Thanks! Maxime drm-misc-next-fixes-2019-09-18: - One fix for the KMS object lifetime checks with DP drivers - One revert for an ADV7511 probe breakage on older systems The following changes since commit 88537ddbbe4c755e193aa220a306395edf08a4cf: drm/mcde: Fix DSI transfers (2019-09-04 22:05:34 +0200) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-fixes-2019-09-18 for you to fetch changes up to e0f32f78e51b9989ee89f608fd0dd10e9c230652: drm/kms: Duct-tape for mode object lifetime checks (2019-09-18 11:27:18 +0200) ---------------------------------------------------------------- - One fix for the KMS object lifetime checks with DP drivers - One revert for an ADV7511 probe breakage on older systems ---------------------------------------------------------------- Daniel Vetter (1): drm/kms: Duct-tape for mode object lifetime checks Rob Clark (1): Revert "drm/bridge: adv7511: Attach to DSI host at probe time" drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 12 +++--------- drivers/gpu/drm/drm_drv.c | 4 ++-- drivers/gpu/drm/drm_mode_object.c | 4 ++-- 3 files changed, 7 insertions(+), 13 deletions(-)

1 0

[PATCH v3 0/7] drm: add some ttm/vram info to debugfs
by Gerd Hoffmann 18 Sep '19

18 Sep '19

Gerd Hoffmann (7): drm: add drm_print_bits drm/ttm: add drm gem ttm helpers, starting with drm_gem_ttm_print_info() drm/vram: use drm_gem_ttm_print_info drm/vram: add vram-mm debugfs file drm/qxl: use drm_gem_object_funcs callbacks drm/qxl: use drm_gem_ttm_print_info drm/vram: fix Kconfig drivers/gpu/drm/qxl/qxl_drv.h | 1 + include/drm/drm_gem_ttm_helper.h | 19 +++++++++ include/drm/drm_gem_vram_helper.h | 1 + include/drm/drm_print.h | 3 ++ include/drm/drm_vram_mm_helper.h | 1 + drivers/gpu/drm/drm_gem_ttm_helper.c | 56 +++++++++++++++++++++++++ drivers/gpu/drm/drm_gem_vram_helper.c | 4 +- drivers/gpu/drm/drm_print.c | 33 +++++++++++++++ drivers/gpu/drm/drm_vram_mm_helper.c | 44 +++++++++++++++++++ drivers/gpu/drm/qxl/qxl_drv.c | 8 ---- drivers/gpu/drm/qxl/qxl_object.c | 13 ++++++ Documentation/gpu/drm-mm.rst | 12 ++++++ drivers/gpu/drm/Kconfig | 8 +++- drivers/gpu/drm/Makefile | 3 ++ drivers/gpu/drm/ast/Kconfig | 2 + drivers/gpu/drm/bochs/Kconfig | 2 + drivers/gpu/drm/hisilicon/hibmc/Kconfig | 3 +- drivers/gpu/drm/mgag200/Kconfig | 2 + drivers/gpu/drm/vboxvideo/Kconfig | 2 + 19 files changed, 206 insertions(+), 11 deletions(-) create mode 100644 include/drm/drm_gem_ttm_helper.h create mode 100644 drivers/gpu/drm/drm_gem_ttm_helper.c -- 2.18.1

4 11

[PATCH v6 0/4] Add HDMI jack support on RK3288
by Cheng-Yi Chiang 18 Sep '19

18 Sep '19

This patch series supports HDMI jack reporting on RK3288, which uses DRM dw-hdmi driver and hdmi-codec codec driver. The previous discussion about reporting jack status using hdmi-notifier and drm_audio_component is at https://lore.kernel.org/patchwork/patch/1083027/ The new approach is to use a callback mechanism that is specific to hdmi-codec. The dependent change on hdmi-codec.c https://patchwork.kernel.org/patch/11047447 has been picked up by Mark Brown in ASoC tree for-5.4 branch. Changes from v5 to v6: 1. Remove the patch for sound/soc/codecs/hdmi-codec.c because it is accepted. 2. Rebase the rest of patches based on drm-misc-next tree. Cheng-Yi Chiang (4): drm: bridge: dw-hdmi: Report connector status using callback drm: dw-hdmi-i2s: Use fixed id for codec device ASoC: rockchip_max98090: Add dai_link for HDMI ASoC: rockchip_max98090: Add HDMI jack support .../drm/bridge/synopsys/dw-hdmi-i2s-audio.c | 13 +- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 41 ++++++- include/drm/bridge/dw_hdmi.h | 4 + sound/soc/rockchip/Kconfig | 3 +- sound/soc/rockchip/rk3288_hdmi_analog.c | 3 +- sound/soc/rockchip/rockchip_max98090.c | 116 ++++++++++++++---- 6 files changed, 153 insertions(+), 27 deletions(-) -- 2.23.0.237.gc6a4ce50a0-goog

3 6

[PATCH] dt-bindings: gpu: Convert Samsung Image Scaler to dt-schema
by Maciej Falkowski 18 Sep '19

18 Sep '19

Convert Samsung Image Scaler to newer dt-schema format. Signed-off-by: Maciej Falkowski <m.falkowski(a)samsung.com> Signed-off-by: Marek Szyprowski <m.szyprowski(a)samsung.com> --- .../bindings/gpu/samsung-scaler.txt | 27 --------- .../bindings/gpu/samsung-scaler.yaml | 57 +++++++++++++++++++ 2 files changed, 57 insertions(+), 27 deletions(-) delete mode 100644 Documentation/devicetree/bindings/gpu/samsung-scaler.txt create mode 100644 Documentation/devicetree/bindings/gpu/samsung-scaler.yaml diff --git a/Documentation/devicetree/bindings/gpu/samsung-scaler.txt b/Documentation/devicetree/bindings/gpu/samsung-scaler.txt deleted file mode 100644 index 9c3d98105dfd..000000000000 --- a/Documentation/devicetree/bindings/gpu/samsung-scaler.txt +++ /dev/null @@ -1,27 +0,0 @@ -* Samsung Exynos Image Scaler - -Required properties: - - compatible : value should be one of the following: - (a) "samsung,exynos5420-scaler" for Scaler IP in Exynos5420 - (b) "samsung,exynos5433-scaler" for Scaler IP in Exynos5433 - - - reg : Physical base address of the IP registers and length of memory - mapped region. - - - interrupts : Interrupt specifier for scaler interrupt, according to format - specific to interrupt parent. - - - clocks : Clock specifier for scaler clock, according to generic clock - bindings. (See Documentation/devicetree/bindings/clock/exynos*.txt) - - - clock-names : Names of clocks. For exynos scaler, it should be "mscl" - on 5420 and "pclk", "aclk" and "aclk_xiu" on 5433. - -Example: - scaler@12800000 { - compatible = "samsung,exynos5420-scaler"; - reg = <0x12800000 0x1294>; - interrupts = <0 220 IRQ_TYPE_LEVEL_HIGH>; - clocks = <&clock CLK_MSCL0>; - clock-names = "mscl"; - }; diff --git a/Documentation/devicetree/bindings/gpu/samsung-scaler.yaml b/Documentation/devicetree/bindings/gpu/samsung-scaler.yaml new file mode 100644 index 000000000000..ee2caab22977 --- /dev/null +++ b/Documentation/devicetree/bindings/gpu/samsung-scaler.yaml @@ -0,0 +1,57 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/gpu/samsung-scaler.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Samsung Exynos SoC Image Scaler + +maintainers: + - Inki Dae <inki.dae(a)samsung.com> + +properties: + compatible: + enum: + - "samsung,exynos5420-scaler" + - "samsung,exynos5433-scaler" + + reg: + maxItems: 1 + + interrupts: + maxItems: 1 + + clocks: + minItems: 1 + maxItems: 3 + + clock-names: + oneOf: + - items: + - const: mscl + - items: + - const: pclk + - const: aclk + - const: aclk_xiu + description: | + For exynos scaler it should be: + - "mscl" on Exynos5420 + - "pclk", "aclk", "aclk_xiu" on Exynos5433 + +required: + - compatible + - reg + - interrupts + - clocks + - clock-names + +examples: + - | + scaler@12800000 { + compatible = "samsung,exynos5420-scaler"; + reg = <0x12800000 0x1294>; + interrupts = <0 220 4>; // IRQ_TYPE_LEVEL_HIGH + clocks = <&clock 0>; // CLK_MSCL0 + clock-names = "mscl"; + }; + -- 2.17.1

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019