dri-devel September 2020

dri-devel@lists.freedesktop.org

359 participants
868 discussions

[PATCH] dt-bindings: gpu: samsung-rotator: Use unevaluatedProperties
by Krzysztof Kozlowski 03 Sep '20

03 Sep '20

Additional properties or nodes actually might appear (e.g. power domains) so use unevaluatedProperties to fix dtbs_check warnings like: arch/arm/boot/dts/exynos4210-i9100.dt.yaml: rotator@12810000: 'iommus', 'power-domains' do not match any of the regexes: 'pinctrl-[0-9]+' Signed-off-by: Krzysztof Kozlowski <krzk(a)kernel.org> --- Documentation/devicetree/bindings/gpu/samsung-rotator.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/gpu/samsung-rotator.yaml b/Documentation/devicetree/bindings/gpu/samsung-rotator.yaml index 665c6e3b31d3..c897c687bdab 100644 --- a/Documentation/devicetree/bindings/gpu/samsung-rotator.yaml +++ b/Documentation/devicetree/bindings/gpu/samsung-rotator.yaml @@ -36,7 +36,7 @@ required: - clocks - clock-names -additionalProperties: false +unevaluatedProperties: false examples: - | -- 2.17.1

2 1

[PULL] drm-misc-next
by Maxime Ripard 03 Sep '20

03 Sep '20

Hi Dave, Daniel, Here's this week PR for drm-misc-next Thanks! Maxime drm-misc-next-2020-09-03: drm-misc-next for 5.10: UAPI Changes: Cross-subsystem Changes: Core Changes: - doc: update the doc to encourage drivers to use devm_drm_dev_alloc - ttm: More reworks / cleanups Driver Changes: - sun4i: Minor fix in the LVDS encoder - panels: New panel: AM-1280800N3TZQW-T00H The following changes since commit cd6da0b113512b15a4d35f355f9ecd8858297369: drm/mgag200: fix spelling mistake "expeced" -> "expected" (2020-08-27 11:17:52 +0200) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2020-09-03 for you to fetch changes up to 4c8e84b8876dc726a7e5327b3113d75423c46728: drm/managed: Cleanup of unused functions and polishing docs (2020-09-03 16:25:06 +0200) ---------------------------------------------------------------- drm-misc-next for 5.10: UAPI Changes: Cross-subsystem Changes: Core Changes: - doc: update the doc to encourage drivers to use devm_drm_dev_alloc - ttm: More reworks / cleanups Driver Changes: - sun4i: Minor fix in the LVDS encoder - panels: New panel: AM-1280800N3TZQW-T00H ---------------------------------------------------------------- Christian König (3): drm/ttm: make sure that we always zero init mem.bus v2 drm/nouveau: move io_reserve_lru handling into the driver v5 drm/ttm: remove io_reserve_lru handling v3 Daniel Vetter (1): drm/managed: Cleanup of unused functions and polishing docs Dave Airlie (2): drm/amdgpu/ttm: remove unused parameter to move blit drm/radeon/ttm: don't store driver copy of device pointer. Dinghao Liu (1): drm/crc-debugfs: Fix memleak in crc_control_write Gerd Hoffmann (2): drm/virtio: fix unblank drm/virtio: drop virtio_gpu_output->enabled Jagan Teki (2): dt-bindings: display: simple: Add AM-1280800N3TZQW-T00H drm/panel: simple: Add AM-1280800N3TZQW-T00H Laurent Pinchart (1): drm: panel: Fix bpc for OrtusTech COM43H4M85ULC panel Maxime Ripard (1): drm/sun4i: lvds: Invert the LVDS polarity Melissa Wen (1): drm/vkms: add alpha-premultiplied color blending Randy Dunlap (3): drm: virtio: fix kconfig dependency warning dma-buf: fix kernel-doc warning in dma-fence.c dma-buf: fix kernel-doc warning in <linux/dma-buf.h> Rikard Falkeborn (1): drm/gma500: Constify static structs Robert Chiras (1): drm/panel: rm67191: Remove CLOCK_NON_CONTINUOUS flag Sam McNally (1): drm/dp_mst: Support remote i2c writes Sidong Yang (1): drm/vkms: avoid warning in vkms_get_vblank_timestamp Tian Tao (1): drm/hisilicon: Removed the dependency on the mmu Ville Syrjälä (2): drm: Nuke mode->private_flags drm: Replace mode->export_head with a boolean Vinod Koul (1): drm/bridge: Fix the dsi remote end-points .../bindings/display/panel/panel-simple.yaml | 2 + Documentation/driver-api/driver-model/devres.rst | 2 +- drivers/dma-buf/dma-fence.c | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 8 +- drivers/gpu/drm/bridge/lontium-lt9611.c | 4 +- drivers/gpu/drm/drm_connector.c | 45 +++++--- drivers/gpu/drm/drm_debugfs_crc.c | 4 +- drivers/gpu/drm/drm_dp_mst_topology.c | 106 +++++++++++++++--- drivers/gpu/drm/drm_drv.c | 78 ++++--------- drivers/gpu/drm/drm_managed.c | 2 +- drivers/gpu/drm/gma500/framebuffer.c | 6 +- drivers/gpu/drm/hisilicon/hibmc/Kconfig | 2 +- drivers/gpu/drm/nouveau/nouveau_bo.c | 101 +++++++++++++---- drivers/gpu/drm/nouveau/nouveau_bo.h | 3 + drivers/gpu/drm/nouveau/nouveau_drv.h | 2 + drivers/gpu/drm/nouveau/nouveau_ttm.c | 44 +++++++- drivers/gpu/drm/panel/panel-raydium-rm67191.c | 3 +- drivers/gpu/drm/panel/panel-simple.c | 31 +++++- drivers/gpu/drm/radeon/radeon_ttm.c | 8 +- drivers/gpu/drm/sun4i/sun4i_tcon.c | 4 +- drivers/gpu/drm/ttm/ttm_bo.c | 43 +++----- drivers/gpu/drm/ttm/ttm_bo_util.c | 121 ++------------------- drivers/gpu/drm/ttm/ttm_bo_vm.c | 39 ++----- drivers/gpu/drm/ttm/ttm_resource.c | 3 - drivers/gpu/drm/virtio/Kconfig | 2 +- drivers/gpu/drm/virtio/virtgpu_display.c | 15 ++- drivers/gpu/drm/virtio/virtgpu_drv.h | 2 +- drivers/gpu/drm/virtio/virtgpu_plane.c | 6 +- drivers/gpu/drm/vkms/vkms_composer.c | 55 +++++++--- drivers/gpu/drm/vkms/vkms_crtc.c | 5 + include/drm/drm_device.h | 2 +- include/drm/drm_drv.h | 16 +-- include/drm/drm_modes.h | 26 ++--- include/drm/ttm/ttm_bo_api.h | 1 - include/drm/ttm/ttm_bo_driver.h | 5 - include/drm/ttm/ttm_resource.h | 16 --- include/linux/dma-buf.h | 3 +- 37 files changed, 436 insertions(+), 380 deletions(-)

1 0

[PATCH] dt-bindings: gpu: arm,mali-utgard: Use unevaluatedProperties
by Krzysztof Kozlowski 03 Sep '20

03 Sep '20

Additional properties or nodes actually might appear (e.g. operating points table) so use unevaluatedProperties to fix dtbs_check warnings like: arch/arm/boot/dts/exynos4210-i9100.dt.yaml: gpu@13000000: 'opp_table' does not match any of the regexes: 'pinctrl-[0-9]+' Signed-off-by: Krzysztof Kozlowski <krzk(a)kernel.org> --- Documentation/devicetree/bindings/gpu/arm,mali-utgard.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-utgard.yaml b/Documentation/devicetree/bindings/gpu/arm,mali-utgard.yaml index 6226d31ec4b7..021690391bea 100644 --- a/Documentation/devicetree/bindings/gpu/arm,mali-utgard.yaml +++ b/Documentation/devicetree/bindings/gpu/arm,mali-utgard.yaml @@ -119,7 +119,7 @@ required: - clocks - clock-names -additionalProperties: false +unevaluatedProperties: false allOf: - if: -- 2.17.1

2 1

[PATCH v4 0/15] drm/bridge: support chained bridges + panel updates
by Sam Ravnborg 03 Sep '20

03 Sep '20

The objective is that all bridge drivers shall support a chained setup connector creation is moved to the display drivers. This is just one step on this path. The general approach for the bridge drivers: - Introduce bridge operations - Introduce use of panel bridge and make connector creation optional v4: - Dropped patch for ti-sn65dsi86. Await full conversion. - Dropped patch for ti-tpd12s015. It was wrong (Laurent) - Drop boe,hv070wsa-100 patch, it was applied - Combined a few patches to fix connector created twice (Laurent) - Fix memory leak in get_edid in several drivers (Laurent) - Added patch to validate panel descriptions in panel-simple - Set bridge.type in relevant drivers v3: - Rebase on top of drm-misc-next - Address kbuild test robot feedback v2: - Updated bus_flags for boe,hv070wsa-100 - Collected r-b, but did not apply patches yet - On the panel side the panel-simple driver gained a default connector type for all the dumb panels that do not include so in their description. With this change panels always provide a connector type, and we have the potential to drop most uses of devm_drm_panel_bridge_add_typed(). - Added conversion of a few more bridge drivers Patches can build but no run-time testing. So both test and review feedback appreciated! Sam Sam Ravnborg (15): drm/panel: panel-simple: validate panel description drm/panel: panel-simple: add default connector_type drm/bridge: tc358764: drop drm_connector_(un)register drm/bridge: tc358764: add drm_panel_bridge support drm/bridge: tc358767: add detect bridge operation drm/bridge: tc358767: add get_edid bridge operation drm/bridge: tc358767: add drm_panel_bridge support drm/bridge: parade-ps8622: add drm_panel_bridge support drm/bridge: megachips: add helper to create connector drm/bridge: megachips: get drm_device from bridge drm/bridge: megachips: enable detect bridge operation drm/bridge: megachips: add get_edid bridge operation drm/bridge: megachips: make connector creation optional drm/bridge: nxp-ptn3460: add get_edid bridge operation drm/bridge: nxp-ptn3460: add drm_panel_bridge support .../drm/bridge/megachips-stdpxxxx-ge-b850v3-fw.c | 97 +++++++++------- drivers/gpu/drm/bridge/nxp-ptn3460.c | 103 ++++++++--------- drivers/gpu/drm/bridge/parade-ps8622.c | 100 +++------------- drivers/gpu/drm/bridge/tc358764.c | 110 +++--------------- drivers/gpu/drm/bridge/tc358767.c | 126 +++++++++++---------- drivers/gpu/drm/panel/panel-simple.c | 48 +++++++- 6 files changed, 242 insertions(+), 342 deletions(-)

4 36

[PATCH v10 00/17] acpi/pwm/i915: Convert pwm-crc and i915 driver's PWM code to use the atomic PWM API
by Hans de Goede 03 Sep '20

03 Sep '20

Hi All, Here is hopefully the last version of this series, as everything seems to be ready for merging this now. The only difference from v9 is correcting some mistakes in the commit-msg of: [PATCH v10 06/17] pwm: lpss: Make pwm_lpss_apply() not rely on hardware state I plan is to push the entire series to drm-intel-next-queued (because of interdependencies) once the series has passed CI. This series has been tested (and re-tested after adding various bug-fixes) extensively. It has been tested on the following devices: -Asus T100TA BYT + CRC-PMIC PWM -Toshiba WT8-A BYT + CRC-PMIC PWM -Thundersoft TS178 BYT + CRC-PMIC PWM, inverse PWM -Asus T100HA CHT + CRC-PMIC PWM -Terra Pad 1061 BYT + LPSS PWM -Trekstor Twin 10.1 BYT + LPSS PWM -Asus T101HA CHT + LPSS PWM -GPD Pocket CHT + LPSS PWM -Acer One S1003 CHT + LPSS PWM Regards, Hans Changelog: Changes in v10: - Fixup the commit msg of: [PATCH v10 06/17] pwm: lpss: Make pwm_lpss_apply() not rely on hardware state Changes in v9: - Replace: [PATCH v8 06/17] pwm: lpss: Use pwm_lpss_restore() when restoring state on resume [PATCH v8 07/17] pwm: lpss: Always update state and set update bit with: [PATCH v9 06/17] pwm: lpss: Make pwm_lpss_apply() not rely on hardware state [PATCH v9 07/17] pwm: lpss: Remove suspend/resume handlers Changes in v8: - Add a new patch dealing with the ACPI/DSDT GFX0._PS3 code poking the PWM controller in unexpected ways on some Cherry Trail devices Changes in v7: - Fix a u64 divide leading to undefined reference to `__udivdi3' errors on 32 bit platforms by casting the divisor to an unsigned long Changes in v6: - Rebase on v5.9-rc1 - Adjust pwm-crc patches for pwm_state.period and .duty_cycle now being u64 Changes in v5: - Dropped the "pwm: lpss: Correct get_state result for base_unit == 0" patch. The base_unit == 0 condition should never happen and sofar it is unclear what the proper behavior / correct values to store in the pwm_state should be when this does happen. Since this patch was added as an extra pwm-lpss fix in v4 of this patch-set and otherwise is orthogonal to the of this patch-set just drop it (again). - "[PATCH 04/16] pwm: lpss: Add range limit check for the base_unit register value" - Use clamp_val(... instead of clam_t(unsigned long long, ... - "[PATCH 05/16] pwm: lpss: Add pwm_lpss_prepare_enable() helper" - This is a new patch in v5 of this patchset - [PATCH 06/16] pwm: lpss: Use pwm_lpss_apply() when restoring state on resume - Use the new pwm_lpss_prepare_enable() helper Changes in v4: - "[PATCH v4 06/16] pwm: lpss: Correct get_state result for base_unit == 0" - This is a new patch in v4 of this patchset - "[PATCH v4 12/16] pwm: crc: Implement get_state() method" - Use DIV_ROUND_UP when calculating the period and duty_cycle values - "[PATCH v4 16/16] drm/i915: panel: Use atomic PWM API for devs with an external PWM controller" - Add a note to the commit message about the changes in pwm_disable_backlight() - Use the pwm_set/get_relative_duty_cycle() helpers Changes in v3: - "[PATCH v3 04/15] pwm: lpss: Add range limit check for the base_unit register value" - Use base_unit_range - 1 as maximum value for the clamp() - "[PATCH v3 05/15] pwm: lpss: Use pwm_lpss_apply() when restoring state on resume" - This replaces the "pwm: lpss: Set SW_UPDATE bit when enabling the PWM" patch from previous versions of this patch-set, which really was a hack working around the resume issue which this patch fixes properly. - PATCH v3 6 - 11 pwm-crc changes: - Various small changes resulting from the reviews by Andy and Uwe, including some refactoring of the patches to reduce the amount of churn in the patch-set Changes in v2: - Fix coverletter subject - Drop accidentally included debugging patch - "[PATCH v3 02/15] ACPI / LPSS: Save Cherry Trail PWM ctx registers only once ( - Move #define LPSS_SAVE_CTX_ONCE define to group it with LPSS_SAVE_CTX

2 21

[Bug 209129] HW related error message under Gnome important tab
by bugzilla-daemon＠bugzilla.kernel.org 03 Sep '20

03 Sep '20

https://bugzilla.kernel.org/show_bug.cgi?id=209129 --- Comment #14 from Laszlo (laszlo.a.toth(a)googlemail.com) --- Then please assign a person at the mentioned new thread who can examine the reason of this bug, verify the root cause, assess whether they have fixed it or not. Then he can suggest the appropriate kernel and probably driver . . . I am user who needs some support during the correcting procedure . . . . -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

[PATCH v9 00/17] acpi/pwm/i915: Convert pwm-crc and i915 driver's PWM code to use the atomic PWM API
by Hans de Goede 03 Sep '20

03 Sep '20

Hi All, So the bug-fix which prompted v8, lead to some discussion about the pwm-lpss suspend/resume code. So as discussed this version drops the following 2 patches: [PATCH v8 06/17] pwm: lpss: Use pwm_lpss_restore() when restoring state on resume [PATCH v8 07/17] pwm: lpss: Always update state and set update bit Replacing them with: [PATCH v9 06/17] pwm: lpss: Make pwm_lpss_apply() not rely on hardware state [PATCH v9 07/17] pwm: lpss: Remove suspend/resume handlers Andy, Thierry, can you review these 2 new patches please? The plan still is to push the entire series to drm-intel-next-queued (because of interdependencies) once the 2 new patches are reviewed and the series has passed CI. This series has been tested (and re-tested after adding various bug-fixes) extensively. It has been tested on the following devices: -Asus T100TA BYT + CRC-PMIC PWM -Toshiba WT8-A BYT + CRC-PMIC PWM -Thundersoft TS178 BYT + CRC-PMIC PWM, inverse PWM -Asus T100HA CHT + CRC-PMIC PWM -Terra Pad 1061 BYT + LPSS PWM -Trekstor Twin 10.1 BYT + LPSS PWM -Asus T101HA CHT + LPSS PWM -GPD Pocket CHT + LPSS PWM -Acer One S1003 CHT + LPSS PWM Regards, Hans Changelog: Changes in v9: - Replace: [PATCH v8 06/17] pwm: lpss: Use pwm_lpss_restore() when restoring state on resume [PATCH v8 07/17] pwm: lpss: Always update state and set update bit with: [PATCH v9 06/17] pwm: lpss: Make pwm_lpss_apply() not rely on hardware state [PATCH v9 07/17] pwm: lpss: Remove suspend/resume handlers Changes in v8: - Add a new patch dealing with the ACPI/DSDT GFX0._PS3 code poking the PWM controller in unexpected ways on some Cherry Trail devices Changes in v7: - Fix a u64 divide leading to undefined reference to `__udivdi3' errors on 32 bit platforms by casting the divisor to an unsigned long Changes in v6: - Rebase on v5.9-rc1 - Adjust pwm-crc patches for pwm_state.period and .duty_cycle now being u64 Changes in v5: - Dropped the "pwm: lpss: Correct get_state result for base_unit == 0" patch. The base_unit == 0 condition should never happen and sofar it is unclear what the proper behavior / correct values to store in the pwm_state should be when this does happen. Since this patch was added as an extra pwm-lpss fix in v4 of this patch-set and otherwise is orthogonal to the of this patch-set just drop it (again). - "[PATCH 04/16] pwm: lpss: Add range limit check for the base_unit register value" - Use clamp_val(... instead of clam_t(unsigned long long, ... - "[PATCH 05/16] pwm: lpss: Add pwm_lpss_prepare_enable() helper" - This is a new patch in v5 of this patchset - [PATCH 06/16] pwm: lpss: Use pwm_lpss_apply() when restoring state on resume - Use the new pwm_lpss_prepare_enable() helper Changes in v4: - "[PATCH v4 06/16] pwm: lpss: Correct get_state result for base_unit == 0" - This is a new patch in v4 of this patchset - "[PATCH v4 12/16] pwm: crc: Implement get_state() method" - Use DIV_ROUND_UP when calculating the period and duty_cycle values - "[PATCH v4 16/16] drm/i915: panel: Use atomic PWM API for devs with an external PWM controller" - Add a note to the commit message about the changes in pwm_disable_backlight() - Use the pwm_set/get_relative_duty_cycle() helpers Changes in v3: - "[PATCH v3 04/15] pwm: lpss: Add range limit check for the base_unit register value" - Use base_unit_range - 1 as maximum value for the clamp() - "[PATCH v3 05/15] pwm: lpss: Use pwm_lpss_apply() when restoring state on resume" - This replaces the "pwm: lpss: Set SW_UPDATE bit when enabling the PWM" patch from previous versions of this patch-set, which really was a hack working around the resume issue which this patch fixes properly. - PATCH v3 6 - 11 pwm-crc changes: - Various small changes resulting from the reviews by Andy and Uwe, including some refactoring of the patches to reduce the amount of churn in the patch-set Changes in v2: - Fix coverletter subject - Drop accidentally included debugging patch - "[PATCH v3 02/15] ACPI / LPSS: Save Cherry Trail PWM ctx registers only once ( - Move #define LPSS_SAVE_CTX_ONCE define to group it with LPSS_SAVE_CTX

2 20

[Bug 209129] HW related error message under Gnome important tab
by bugzilla-daemon＠bugzilla.kernel.org 03 Sep '20

03 Sep '20

https://bugzilla.kernel.org/show_bug.cgi?id=209129 --- Comment #13 from Borislav Petkov (bp(a)alien8.de) --- > Ok, then what shall I do? Did you not read this? "What you could do for starters is try the latest kernel 5.8 to check whether this has been fixed in the meantime." -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

[Bug 209129] HW related error message under Gnome important tab
by bugzilla-daemon＠bugzilla.kernel.org 03 Sep '20

03 Sep '20

https://bugzilla.kernel.org/show_bug.cgi?id=209129 --- Comment #12 from Laszlo (laszlo.a.toth(a)googlemail.com) --- Ok, then what shall I do? -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

[Bug 209129] HW related error message under Gnome important tab
by bugzilla-daemon＠bugzilla.kernel.org 03 Sep '20

03 Sep '20

https://bugzilla.kernel.org/show_bug.cgi?id=209129 Borislav Petkov (bp(a)alien8.de) changed: What |Removed |Added ---------------------------------------------------------------------------- Component|x86-64 |Video(DRI - non Intel) Assignee|platform_x86_64@kernel-bugs |drivers_video-dri@kernel-bu |.osdl.org |gs.osdl.org Product|Platform Specific/Hardware |Drivers --- Comment #11 from Borislav Petkov (bp(a)alien8.de) --- Hmm, so it looks like that GpuWatchdog thing is chrome thread. And the error in your dmesg before it: [ 266.208179] [TTM] Buffer eviction failed [ 266.346883] GpuWatchdog[2984]: segfault at 0 ip says that a buffer eviction in the TTM fails which probably causes the watchdog to segfault. In any case, this is a DRM issue, not a platform one. Reassigning... What you could do for starters is try the latest kernel 5.8 to check whether this has been fixed in the meantime. HTH. -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

← Newer
1
...
79
80
81
82
83
84
85
86
87
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2020