dri-devel June 2020

dri-devel@lists.freedesktop.org

315 participants
731 discussions

[PATCH] drm/panel-simple: fix connector type for newhaven_nhd_43_480272ef_atxl
by Tomi Valkeinen 21 Jun '20

21 Jun '20

Add connector type for newhaven_nhd_43_480272ef_atxl, as drm_panel_bridge_add() requires connector type to be set. Signed-off-by: Tomi Valkeinen <tomi.valkeinen(a)ti.com> Cc: stable(a)vger.kernel.org # v5.5+ --- drivers/gpu/drm/panel/panel-simple.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c index 3ad828eaefe1..00c1a8dc4ce8 100644 --- a/drivers/gpu/drm/panel/panel-simple.c +++ b/drivers/gpu/drm/panel/panel-simple.c @@ -2465,6 +2465,7 @@ static const struct panel_desc newhaven_nhd_43_480272ef_atxl = { .bus_format = MEDIA_BUS_FMT_RGB888_1X24, .bus_flags = DRM_BUS_FLAG_DE_HIGH | DRM_BUS_FLAG_PIXDATA_DRIVE_POSEDGE | DRM_BUS_FLAG_SYNC_DRIVE_POSEDGE, + .connector_type = DRM_MODE_CONNECTOR_DPI, }; static const struct display_timing nlt_nl192108ac18_02d_timing = { -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

2 1

[PATCH RESEND v2 0/4] panel-simple: CDTech S070PWS19HP-FC21 and S070SWV29HG-DC44, Tianma TM070JVHG33
by Matthias Schiffer 21 Jun '20

21 Jun '20

From: Matthias Schiffer <matthias.schiffer(a)tq-group.com> This adds a few panels TQ-Systems uses with various starterkit mainboards. Device trees actually using these panels will be added with a later submission. Matthias Schiffer (2): dt-bindings: display: simple: add CDTech S070PWS19HP-FC21 and S070SWV29HG-DC44 dt-bindings: display: simple: add Tianma TM070JVHG33 Max Merchel (1): drm/panel: simple: add Tianma TM070JVHG33 Michael Krummsdorf (1): drm/panel: simple: add CDTech S070PWS19HP-FC21 and S070SWV29HG-DC44 .../bindings/display/panel/panel-simple.yaml | 6 ++ drivers/gpu/drm/panel/panel-simple.c | 75 +++++++++++++++++++ 2 files changed, 81 insertions(+) -- 2.17.1

3 7

[PATCH] drm/panel-simple: fix connector type for LogicPD Type28 Display
by Adam Ford 21 Jun '20

21 Jun '20

The LogicPD Type28 display used by several Logic PD products has not worked since v5.5. The connector type for the LogicPD Type 28 display is missing and drm_panel_bridge_add() requires connector type to be set. Signed-off-by: Adam Ford <aford173(a)gmail.com> CC: stable(a)vger.kernel.org #v5.5+ diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c index b6ecd1552132..334e9de5b2c8 100644 --- a/drivers/gpu/drm/panel/panel-simple.c +++ b/drivers/gpu/drm/panel/panel-simple.c @@ -2495,6 +2495,7 @@ static const struct panel_desc logicpd_type_28 = { .bus_format = MEDIA_BUS_FMT_RGB888_1X24, .bus_flags = DRM_BUS_FLAG_DE_HIGH | DRM_BUS_FLAG_PIXDATA_DRIVE_POSEDGE | DRM_BUS_FLAG_SYNC_DRIVE_NEGEDGE, + .connector_type = DRM_MODE_CONNECTOR_DPI, }; static const struct panel_desc mitsubishi_aa070mc01 = { -- 2.17.1

4 4

[GIT PULL FOR v5.8] R-Car DU fixes
by Laurent Pinchart 21 Jun '20

21 Jun '20

Hi Dave and Daniel, Just one small fix for the R-Car DU driver. The following changes since commit 8a7a3d1d0dcf2bb63dafe7275020420005e13e54: Merge tag 'amd-drm-fixes-5.8-2020-06-17' of git://people.freedesktop.org/~agd5f/linux into drm-fixes (2020-06-19 10:02:30 +1000) are available in the Git repository at: git://linuxtv.org/pinchartl/media.git tags/du-fixes-20200621 for you to fetch changes up to 5f9af404eec82981c4345c9943be48422234e7ab: drm: rcar-du: Fix build error (2020-06-21 05:12:57 +0300) ---------------------------------------------------------------- Build fix for the R-Car DU DRM driver ---------------------------------------------------------------- Daniel Gomez (1): drm: rcar-du: Fix build error drivers/gpu/drm/rcar-du/Kconfig | 1 + 1 file changed, 1 insertion(+) -- Regards, Laurent Pinchart

1 0

[PATCH v2 0/4] ast cleanups
by Thomas Zimmermann 20 Jun '20

20 Jun '20

Ast still has to be converted to managed initialization, and embed the DRM device in the ast structure. In preparation of these changes, add some cleanups to the driver. Tested on ast HW. v2: * remove device tests from ast_pm_freeze() (Daniel) * convert WARN_*() (Sam) * typo fixes Thomas Zimmermann (4): drm/ast: Remove unused code paths for AST 1180 drm/ast: Remove test for device from ast_pm_freeze() drm/ast: Upcast from DRM device to ast structure via to_ast_private() drm/ast: Use per-device logging macros drivers/gpu/drm/ast/ast_dp501.c | 24 +++---- drivers/gpu/drm/ast/ast_drv.c | 4 -- drivers/gpu/drm/ast/ast_drv.h | 7 +- drivers/gpu/drm/ast/ast_main.c | 115 +++++++++++++++----------------- drivers/gpu/drm/ast/ast_mode.c | 73 ++++++++++---------- drivers/gpu/drm/ast/ast_post.c | 28 ++++---- drivers/gpu/drm/ast/ast_ttm.c | 2 +- 7 files changed, 116 insertions(+), 137 deletions(-) -- 2.27.0

2 5

[PATCH v4 0/4] dt-bindings: display: ti,tfp410.txt: convert to yaml
by Ricardo Cañuelo 20 Jun '20

20 Jun '20

This series converts the DT binding for the TI TFP410 DPI-to-DVI encoder to json-schema. It also fixes a minor bug in the ti-tfp410 driver that causes a wrong calculation of the setup and hold times when the de-skew feature is enabled. The retrieval of the de-skew value from the DT has also been updated to reflect the binding changes. Changes in v4: - ti,tfp410.yaml: - "ports" node set back as required (Laurent Pinchart). This means that dove-sbc-a510.dts will not comply with the binding and will have to be fixed at some point. The bindings have been tested with: make dt_binding_check ARCH=<arch> DT_SCHEMA_FILES=<...ti,tfp410.yaml> make dtbs_check ARCH=<arch> DT_SCHEMA_FILES=<...ti,tfp410.yaml> for <arch> = arm and arm64. This uncovered a number of dts files that use the TFP410 but not through I2C and don't define the ti,deskew property. These should also be fixed. Ricardo Cañuelo (4): dt-bindings: display: ti,tfp410.txt: convert to yaml dt-bindings: display: ti,tfp410.yaml: Redefine ti,deskew property drm/bridge: tfp410: fix de-skew value retrieval from DT drm/bridge: tfp410: Fix setup and hold time calculation .../bindings/display/bridge/ti,tfp410.txt | 66 --------- .../bindings/display/bridge/ti,tfp410.yaml | 131 ++++++++++++++++++ drivers/gpu/drm/bridge/ti-tfp410.c | 10 +- 3 files changed, 136 insertions(+), 71 deletions(-) delete mode 100644 Documentation/devicetree/bindings/display/bridge/ti,tfp410.txt create mode 100644 Documentation/devicetree/bindings/display/bridge/ti,tfp410.yaml -- 2.18.0

2 5

[PATCH] drm/msm/dpu: Fix usage of ERR_PTR()
by Zenghui Yu 20 Jun '20

20 Jun '20

ERR_PTR() is used in the kernel to encode an usual *negative* errno code into a pointer. Passing a positive value (ENOMEM) to it will break the following IS_ERR() check. Though memory allocation is unlikely to fail, it's still worth fixing. And grepping shows that this is the only misuse of ERR_PTR() in kernel. Fixes: 25fdd5933e4c ("drm/msm: Add SDM845 DPU support") Signed-off-by: Zenghui Yu <yuzenghui(a)huawei.com> --- drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c index a1b79ee2bd9d..a2f6b688a976 100644 --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c @@ -2173,7 +2173,7 @@ struct drm_encoder *dpu_encoder_init(struct drm_device *dev, dpu_enc = devm_kzalloc(dev->dev, sizeof(*dpu_enc), GFP_KERNEL); if (!dpu_enc) - return ERR_PTR(ENOMEM); + return ERR_PTR(-ENOMEM); rc = drm_encoder_init(dev, &dpu_enc->base, &dpu_encoder_funcs, drm_enc_mode, NULL); -- 2.19.1

2 2

Re: [PATCH v2] drm/amdkfd: Fix memory leaks according to error branches
by Markus Elfring 20 Jun '20

20 Jun '20

> The function kobject_init_and_add alloc memory like: > kobject_init_and_add->kobject_add_varg->kobject_set_name_vargs > ->kvasprintf_const->kstrdup_const->kstrdup->kmalloc_track_caller > ->kmalloc_slab, in err branch this memory not free. If use > kmemleak, this path maybe catched. > These changes are to add kobject_put in kobject_init_and_add > failed branch, fix potential memleak. I suggest to improve this change description. * Can an other wording variant be nicer? * Will the tag “Fixes” become helpful for the commit message? Regards, Markus

3 5

Re: [PATCH v3] drm/amd: Fix memory leak according to error branch
by Markus Elfring 20 Jun '20

20 Jun '20

> The function kobject_init_and_add alloc memory like: > kobject_init_and_add->kobject_add_varg->kobject_set_name_vargs > ->kvasprintf_const->kstrdup_const->kstrdup->kmalloc_track_caller > ->kmalloc_slab, in err branch this memory not free. If use > kmemleak, this path maybe catched. > These changes are to add kobject_put in kobject_init_and_add > failed branch, fix potential memleak. … > Changes since V2: > *remove duplicate kobject_put in kfd_procfs_init. Under which circumstances are going to improve this change description accordingly? Would you like to add the tag “Fixes” to the commit message? Regards, Markus

3 2

[Bug 199475] New: AMDGPU Failed to blank
by bugzilla-daemon＠bugzilla.kernel.org 20 Jun '20

20 Jun '20

https://bugzilla.kernel.org/show_bug.cgi?id=199475 Bug ID: 199475 Summary: AMDGPU Failed to blank Product: Drivers Version: 2.5 Kernel Version: 4.15.18 Hardware: Other OS: Linux Tree: Mainline Status: NEW Severity: low Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: andreassx0(a)gmail.com Regression: No Im getting this error on starup: drm:hwss_wait_for_blank_complete [amdgpu] *ERROR* DC: failed to blank crtc! -- You are receiving this mail because: You are watching the assignee of the bug.

1 9

← Newer
1
...
36
37
38
39
40
41
42
...
74
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2020