dri-devel September 2021

dri-devel@lists.freedesktop.org

348 participants
817 discussions

[PATCH] drm/bridge: ti-sn65dsi83: Check link status register after enabling the bridge
by Marek Vasut 05 Oct '21

05 Oct '21

In rare cases, the bridge may not start up correctly, which usually leads to no display output. In case this happens, warn about it in the kernel log. Signed-off-by: Marek Vasut <marex(a)denx.de> Cc: Jagan Teki <jagan(a)amarulasolutions.com> Cc: Laurent Pinchart <laurent.pinchart(a)ideasonboard.com> Cc: Linus Walleij <linus.walleij(a)linaro.org> Cc: Robert Foss <robert.foss(a)linaro.org> Cc: Sam Ravnborg <sam(a)ravnborg.org> Cc: dri-devel(a)lists.freedesktop.org --- NOTE: See the following: https://e2e.ti.com/support/interface-group/interface/f/interface-forum/9420… https://community.nxp.com/t5/i-MX-Processors/i-MX8M-MIPI-DSI-Interface-LVDS… --- drivers/gpu/drm/bridge/ti-sn65dsi83.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/gpu/drm/bridge/ti-sn65dsi83.c b/drivers/gpu/drm/bridge/ti-sn65dsi83.c index a32f70bc68ea4..4ea71d7f0bfbc 100644 --- a/drivers/gpu/drm/bridge/ti-sn65dsi83.c +++ b/drivers/gpu/drm/bridge/ti-sn65dsi83.c @@ -520,6 +520,11 @@ static void sn65dsi83_atomic_enable(struct drm_bridge *bridge, /* Clear all errors that got asserted during initialization. */ regmap_read(ctx->regmap, REG_IRQ_STAT, &pval); regmap_write(ctx->regmap, REG_IRQ_STAT, pval); + + usleep_range(10000, 12000); + regmap_read(ctx->regmap, REG_IRQ_STAT, &pval); + if (pval) + dev_err(ctx->dev, "Unexpected link status 0x%02x\n", pval); } static void sn65dsi83_atomic_disable(struct drm_bridge *bridge, -- 2.33.0

3 9

[PATCH v1 1/4] dt-bindings: msm: add DT bindings for sc7280
by Krishna Manikandan 05 Oct '21

05 Oct '21

MSM Mobile Display Subsystem (MDSS) encapsulates sub-blocks like DPU display controller, DSI, EDP etc. Add required DPU device tree bindings for SC7280. Signed-off-by: Krishna Manikandan <mkrishn(a)codeaurora.org> --- .../bindings/display/msm/dpu-sc7280.yaml | 228 +++++++++++++++++++++ 1 file changed, 228 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/msm/dpu-sc7280.yaml diff --git a/Documentation/devicetree/bindings/display/msm/dpu-sc7280.yaml b/Documentation/devicetree/bindings/display/msm/dpu-sc7280.yaml new file mode 100644 index 0000000..3d256c0 --- /dev/null +++ b/Documentation/devicetree/bindings/display/msm/dpu-sc7280.yaml @@ -0,0 +1,228 @@ +# SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/msm/dpu-sc7280.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Qualcomm Display DPU dt properties for SC7280 target + +maintainers: + - Krishna Manikandan <mkrishn(a)codeaurora.org> + +description: | + Device tree bindings for MSM Mobile Display Subsystem(MDSS) that encapsulates + sub-blocks like DPU display controller, DSI and DP interfaces etc. Device tree + bindings of MDSS and DPU are mentioned for SC7280 target. + +properties: + compatible: + items: + - const: qcom,sc7280-mdss + + reg: + maxItems: 1 + + reg-names: + const: mdss + + power-domains: + maxItems: 1 + + clocks: + items: + - description: Display AHB clock from gcc + - description: Display AHB clock from dispcc + - description: Display core clock + + clock-names: + items: + - const: iface + - const: ahb + - const: core + + interrupts: + maxItems: 1 + + interrupt-controller: true + + "#address-cells": true + + "#size-cells": true + + "#interrupt-cells": + const: 1 + + iommus: + items: + - description: Phandle to apps_smmu node with SID mask for Hard-Fail port0 + + ranges: true + + interconnects: + items: + - description: Interconnect path specifying the port ids for data bus + + interconnect-names: + const: mdp0-mem + +patternProperties: + "^display-controller@[0-9a-f]+$": + type: object + description: Node containing the properties of DPU. + + properties: + compatible: + items: + - const: qcom,sc7280-dpu + + reg: + items: + - description: Address offset and size for mdp register set + - description: Address offset and size for vbif register set + + reg-names: + items: + - const: mdp + - const: vbif + + clocks: + items: + - description: Display hf axi clock + - description: Display sf axi clock + - description: Display ahb clock + - description: Display lut clock + - description: Display core clock + - description: Display vsync clock + + clock-names: + items: + - const: bus + - const: nrt_bus + - const: iface + - const: lut + - const: core + - const: vsync + + interrupts: + maxItems: 1 + + power-domains: + maxItems: 1 + + operating-points-v2: true + + ports: + $ref: /schemas/graph.yaml#/properties/ports + description: | + Contains the list of output ports from DPU device. These ports + connect to interfaces that are external to the DPU hardware, + such as DSI, DP etc. Each output port contains an endpoint that + describes how it is connected to an external interface. + + properties: + port@0: + $ref: /schemas/graph.yaml#/properties/port + description: DPU_INTF1 (DSI) + + port@1: + $ref: /schemas/graph.yaml#/properties/port + description: DPU_INTF5 (EDP) + + required: + - port@0 + + required: + - compatible + - reg + - reg-names + - clocks + - interrupts + - power-domains + - operating-points-v2 + - ports + +required: + - compatible + - reg + - reg-names + - power-domains + - clocks + - interrupts + - interrupt-controller + - iommus + - ranges + +additionalProperties: false + +examples: + - | + #include <dt-bindings/clock/qcom,dispcc-sc7280.h> + #include <dt-bindings/clock/qcom,gcc-sc7280.h> + #include <dt-bindings/interrupt-controller/arm-gic.h> + #include <dt-bindings/interconnect/qcom,sc7280.h> + #include <dt-bindings/power/qcom-rpmpd.h> + + display-subsystem@ae00000 { + #address-cells = <1>; + #size-cells = <1>; + compatible = "qcom,sc7280-mdss"; + reg = <0xae00000 0x1000>; + reg-names = "mdss"; + power-domains = <&dispcc DISP_CC_MDSS_CORE_GDSC>; + clocks = <&gcc GCC_DISP_AHB_CLK>, + <&dispcc DISP_CC_MDSS_AHB_CLK>, + <&dispcc DISP_CC_MDSS_MDP_CLK>; + clock-names = "iface", "ahb", "core"; + + interrupts = <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>; + interrupt-controller; + #interrupt-cells = <1>; + + interconnects = <&mmss_noc MASTER_MDP0 &mc_virt SLAVE_EBI1>; + interconnect-names = "mdp0-mem"; + + iommus = <&apps_smmu 0x900 0x402>; + ranges; + + display-controller@ae01000 { + compatible = "qcom,sc7280-dpu"; + reg = <0x0ae01000 0x8f000>, + <0x0aeb0000 0x2008>; + + reg-names = "mdp", "vbif"; + + clocks = <&gcc GCC_DISP_HF_AXI_CLK>, + <&gcc GCC_DISP_SF_AXI_CLK>, + <&dispcc DISP_CC_MDSS_AHB_CLK>, + <&dispcc DISP_CC_MDSS_MDP_LUT_CLK>, + <&dispcc DISP_CC_MDSS_MDP_CLK>, + <&dispcc DISP_CC_MDSS_VSYNC_CLK>; + clock-names = "bus", "nrt_bus", "iface", "lut", "core", + "vsync"; + + interrupt-parent = <&mdss>; + interrupts = <0>; + power-domains = <&rpmhpd SC7280_CX>; + operating-points-v2 = <&mdp_opp_table>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + dpu_intf1_out: endpoint { + remote-endpoint = <&dsi0_in>; + }; + }; + + port@1 { + reg = <1>; + dpu_intf5_out: endpoint { + remote-endpoint = <&edp_in>; + }; + }; + }; + }; + }; +... -- 2.7.4

5 16

[PATCH] drm/i915: Fix bug in user proto-context creation that leaked contexts
by Matthew Brost 05 Oct '21

05 Oct '21

Set number of engines before attempting to create contexts so the function free_engines can clean up properly. Also check return of alloc_engines for NULL. v2: (Tvrtko) - Send as stand alone patch (John Harrison) - Check for alloc_engines returning NULL Cc: Jason Ekstrand <jason(a)jlekstrand.net> Fixes: d4433c7600f7 ("drm/i915/gem: Use the proto-context to handle create parameters (v5)") Signed-off-by: Matthew Brost <matthew.brost(a)intel.com> Cc: <stable(a)vger.kernel.org> --- drivers/gpu/drm/i915/gem/i915_gem_context.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gem/i915_gem_context.c b/drivers/gpu/drm/i915/gem/i915_gem_context.c index c2ab0e22db0a..9627c7aac6a3 100644 --- a/drivers/gpu/drm/i915/gem/i915_gem_context.c +++ b/drivers/gpu/drm/i915/gem/i915_gem_context.c @@ -898,6 +898,11 @@ static struct i915_gem_engines *user_engines(struct i915_gem_context *ctx, unsigned int n; e = alloc_engines(num_engines); + if (!e) { + return ERR_PTR(-ENOMEM); + } + e->num_engines = num_engines; + for (n = 0; n < num_engines; n++) { struct intel_context *ce; int ret; @@ -931,7 +936,6 @@ static struct i915_gem_engines *user_engines(struct i915_gem_context *ctx, goto free_engines; } } - e->num_engines = num_engines; return e; -- 2.32.0

2 3

Re: refactor the i915 GVT support
by Luis Chamberlain 05 Oct '21

05 Oct '21

On Fri, Aug 20, 2021 at 04:17:24PM +0200, Christoph Hellwig wrote: > On Thu, Aug 19, 2021 at 04:29:29PM +0800, Zhenyu Wang wrote: > > I'm working on below patch to resolve this. But I met a weird issue in > > case when building i915 as module and also kvmgt module, it caused > > busy wait on request_module("kvmgt") when boot, it doesn't happen if > > building i915 into kernel. I'm not sure what could be the reason? > > Luis, do you know if there is a problem with a request_module from > a driver ->probe routine that is probably called by a module_init > function itself? Generally no, but you can easily foot yourself in the feet by creating cross dependencies and not dealing with them properly. I'd make sure to keep module initialization as simple as possible, and run whatever takes more time asynchronously, then use a state machine to allow you to verify where you are in the initialization phase or query it or wait for a completion with a timeout. It seems the code in question is getting some spring cleaning, and its unclear where the code is I can inspect. If there's a tree somewhere I can take a peak I'd be happy to review possible oddities that may stick out. My goto model for these sorts of problems is to abstract the issue *outside* of the driver in question and implement new selftests to try to reproduce. This serves two purposes, 1) helps with testing 2) may allow you to see the problem more clearly. Luis

4 9

[Bug 206349] New: WARNING: dcn20_validate_bandwidth+0x87/0x9e [ amdgpu on 5700 XT ]
by bugzilla-daemon＠bugzilla.kernel.org 05 Oct '21

05 Oct '21

https://bugzilla.kernel.org/show_bug.cgi?id=206349 Bug ID: 206349 Summary: WARNING: dcn20_validate_bandwidth+0x87/0x9e [ amdgpu on 5700 XT ] Product: Drivers Version: 2.5 Kernel Version: 5.5.0 Hardware: x86-64 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: doublej472(a)gmail.com Regression: No Created attachment 287027 --> https://bugzilla.kernel.org/attachment.cgi?id=287027&action=edit dmesg warnings from amdgpu I've been seeing this warning pop up in my dmesg for a while from amdgpu, all relating to dcn20_validate_bandwidth. I'm not sure if it's affecting my machine in a significant manner, but it keeps showing up. [ 8236.203353] arch-desktop kernel: ------------[ cut here ]------------ [ 8236.203403] arch-desktop kernel: WARNING: CPU: 9 PID: 555 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_resource.c:2959 dcn20_validate_bandwidth+0x87/0x9e [amdgpu] [ 8236.203405] arch-desktop kernel: Modules linked in: bridge stp llc bcache crc64 raid1 snd_usb_audio snd_usbmidi_lib kvm_amd snd_rawmidi kvm amdgpu gpu_sched k10temp ttm sch_fq_codel efivarfs [ 8236.203414] arch-desktop kernel: CPU: 9 PID: 555 Comm: Xorg Not tainted 5.5.0-gentoo #1 [ 8236.203415] arch-desktop kernel: Hardware name: System manufacturer System Product Name/PRIME X370-PRO, BIOS 5220 09/12/2019 [ 8236.203451] arch-desktop kernel: RIP: 0010:dcn20_validate_bandwidth+0x87/0x9e [amdgpu] [ 8236.203453] arch-desktop kernel: Code: 00 00 01 eb 29 31 d2 f2 0f 11 85 70 21 00 00 48 89 ee e8 e9 f7 ff ff 89 c2 22 85 b8 1d 00 00 74 09 c6 85 b8 1d 00 00 00 eb 04 <0f> 0b 89 d0 f2 0f 10 1c 24 f2 0f 11 9d 70 21 00 00 48 83 c4 10 5d [ 8236.203455] arch-desktop kernel: RSP: 0018:ffff8e9800c9fa80 EFLAGS: 00010246 [ 8236.203457] arch-desktop kernel: RAX: 0000000000000000 RBX: ffff8b19d3f6b900 RCX: 0000000000215f49 [ 8236.203458] arch-desktop kernel: RDX: 0000000000000001 RSI: 0000000000215f09 RDI: 000000000002e300 [ 8236.203460] arch-desktop kernel: RBP: ffff8b17ee190000 R08: ffff8b1b7b406840 R09: ffffffffc0345b6b [ 8236.203461] arch-desktop kernel: R10: ffff8b1b66e6a000 R11: ffff8b1b66e6a000 R12: 0000000000000000 [ 8236.203462] arch-desktop kernel: R13: 0000000000000000 R14: ffff8b17ee190000 R15: 0000000000000002 [ 8236.203464] arch-desktop kernel: FS: 00007ff890a4e980(0000) GS:ffff8b1b7ea40000(0000) knlGS:0000000000000000 [ 8236.203465] arch-desktop kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 8236.203467] arch-desktop kernel: CR2: 00005620d7c8eef0 CR3: 00000007e2886000 CR4: 0000000000340ee0 [ 8236.203468] arch-desktop kernel: Call Trace: [ 8236.203504] arch-desktop kernel: dc_validate_global_state+0x1b6/0x1d7 [amdgpu] [ 8236.203549] arch-desktop kernel: amdgpu_dm_atomic_check+0x52a/0x666 [amdgpu] [ 8236.203556] arch-desktop kernel: drm_atomic_check_only+0x586/0x62e [ 8236.203559] arch-desktop kernel: ? drm_atomic_set_crtc_for_connector+0xd9/0xe1 [ 8236.203562] arch-desktop kernel: drm_atomic_commit+0xe/0x44 [ 8236.203565] arch-desktop kernel: drm_atomic_helper_set_config+0x50/0x66 [ 8236.203569] arch-desktop kernel: drm_mode_setcrtc+0x221/0x5dc [ 8236.203574] arch-desktop kernel: ? drm_mode_getcrtc+0x145/0x145 [ 8236.203576] arch-desktop kernel: drm_ioctl_kernel+0x8d/0xe1 [ 8236.203579] arch-desktop kernel: drm_ioctl+0x1f9/0x2d3 [ 8236.203582] arch-desktop kernel: ? drm_mode_getcrtc+0x145/0x145 [ 8236.203613] arch-desktop kernel: amdgpu_drm_ioctl+0x45/0x71 [amdgpu] [ 8236.203617] arch-desktop kernel: vfs_ioctl+0x19/0x26 [ 8236.203620] arch-desktop kernel: do_vfs_ioctl+0x574/0x59e [ 8236.203623] arch-desktop kernel: ksys_ioctl+0x49/0x68 [ 8236.203626] arch-desktop kernel: __x64_sys_ioctl+0x11/0x14 [ 8236.203629] arch-desktop kernel: do_syscall_64+0x48/0x55 [ 8236.203632] arch-desktop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 8236.203634] arch-desktop kernel: RIP: 0033:0x7ff890d0b5c7 [ 8236.203636] arch-desktop kernel: Code: 00 00 00 75 0c 48 c7 c0 ff ff ff ff 48 83 c4 18 c3 e8 0d c8 01 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 99 e8 0c 00 f7 d8 64 89 01 48 [ 8236.203638] arch-desktop kernel: RSP: 002b:00007ffea4921a48 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 8236.203639] arch-desktop kernel: RAX: ffffffffffffffda RBX: 00007ffea4921a80 RCX: 00007ff890d0b5c7 [ 8236.203641] arch-desktop kernel: RDX: 00007ffea4921a80 RSI: 00000000c06864a2 RDI: 000000000000000c [ 8236.203642] arch-desktop kernel: RBP: 00000000c06864a2 R08: 0000000000000000 R09: 0000000000000000 [ 8236.203643] arch-desktop kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00005620d7fe1e70 [ 8236.203644] arch-desktop kernel: R13: 000000000000000c R14: 00005620d8e342f0 R15: 00005620d6dc2040 [ 8236.203649] arch-desktop kernel: ---[ end trace 82184d8b2d613936 ]--- I've attached a few more warnings to this bug report. I'm not sure what causes this warning. It *might* happen whenever the GPU is being used, if I leave the machine alone it tends to not show. It could be related to waking up my monitor? (Attached to a DisplayPort cable, running at 1920x1080 @ 144 Hz, if that matters) My system is running on an ASUS PRIME X370-PRO motherboard with a ryzen 3900x, 32GB of ram, and a 5700 XT GPU (on a PCIe 3.0 x16 link). Please let me know if you need more info! -- You are receiving this mail because: You are watching the assignee of the bug.

1 1

[PATCH V4 1/2] dt-bindings: display: bridge: lvds-codec: Document LVDS data mapping select
by Marek Vasut 05 Oct '21

05 Oct '21

Decoder input LVDS format is a property of the decoder chip or even its strapping. Add DT property data-mapping the same way lvds-panel does, to define the LVDS data mapping. Signed-off-by: Marek Vasut <marex(a)denx.de> Cc: Laurent Pinchart <laurent.pinchart(a)ideasonboard.com> Cc: Rob Herring <robh+dt(a)kernel.org> Cc: Sam Ravnborg <sam(a)ravnborg.org> Cc: devicetree(a)vger.kernel.org To: dri-devel(a)lists.freedesktop.org --- V2: - Use allOf - Move the data-mapping to endpoint V3: - Rebase on V2 submitted a while ago, reinstate changelog - Drop the allOf and un-rebase on previous pclk patch V4: - port@1, remove $ref: /schemas/graph.yaml#/properties/port and add $ref: /schemas/graph.yaml#/$defs/port-base --- .../bindings/display/bridge/lvds-codec.yaml | 33 ++++++++++++++++++- 1 file changed, 32 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/display/bridge/lvds-codec.yaml b/Documentation/devicetree/bindings/display/bridge/lvds-codec.yaml index 304a1367faaa7..c0400c60f272a 100644 --- a/Documentation/devicetree/bindings/display/bridge/lvds-codec.yaml +++ b/Documentation/devicetree/bindings/display/bridge/lvds-codec.yaml @@ -55,11 +55,26 @@ properties: For LVDS decoders, port 0 is the LVDS input port@1: - $ref: /schemas/graph.yaml#/properties/port + $ref: /schemas/graph.yaml#/$defs/port-base description: | For LVDS encoders, port 1 is the LVDS output For LVDS decoders, port 1 is the parallel output + properties: + endpoint: + $ref: /schemas/media/video-interfaces.yaml# + unevaluatedProperties: false + + properties: + data-mapping: + enum: + - jeida-18 + - jeida-24 + - vesa-24 + description: | + The color signals mapping order. See details in + Documentation/devicetree/bindings/display/panel/lvds.yaml + required: - port@0 - port@1 @@ -71,6 +86,22 @@ properties: power-supply: true +if: + not: + properties: + compatible: + contains: + const: lvds-decoder +then: + properties: + ports: + properties: + port@1: + properties: + endpoint: + properties: + data-mapping: false + required: - compatible - ports -- 2.30.2

3 6

[Bug 213201] New: [KAVERI] memory leak - unreferenced object 0xffff8881700cf988 (size 56)
by bugzilla-daemon＠bugzilla.kernel.org 04 Oct '21

04 Oct '21

https://bugzilla.kernel.org/show_bug.cgi?id=213201 Bug ID: 213201 Summary: [KAVERI] memory leak - unreferenced object 0xffff8881700cf988 (size 56) Product: Drivers Version: 2.5 Kernel Version: 5.13-rc3 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: erhard_f(a)mailbox.org CC: daniel(a)ffwll.ch Regression: No Created attachment 296967 --> https://bugzilla.kernel.org/attachment.cgi?id=296967&action=edit kernel dmesg (5.13-rc3, AMD A10 PRO-7800B) Get this shortly after booting kernel 5.13-rc3. Looks like amdgpu is involved: unreferenced object 0xffff8881700cf988 (size 56): comm "systemd-udevd", pid 216, jiffies 4294885043 (age 1739.830s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 0d 01 70 00 00 00 00 00 ..........p..... 7b 98 01 00 00 c9 ff ff 00 00 00 00 00 00 00 00 {............... backtrace: [<00000000f3e5fc85>] kmem_cache_alloc+0x10a/0x1e4 [<00000000fff767c3>] acpi_ps_alloc_op+0x4e/0xdc [<00000000445cacf1>] acpi_ps_create_op+0x24e/0x473 [<000000003452a27a>] acpi_ps_parse_loop+0x25e/0xa39 [<000000004e3469e0>] acpi_ps_parse_aml+0xf3/0x450 [<00000000be1f7fd0>] acpi_ps_execute_method+0x278/0x2bb [<000000004564e9a8>] acpi_ns_evaluate+0x34f/0x45d [<0000000072f73c39>] acpi_evaluate_object+0x201/0x3b5 [<0000000036379e33>] amdgpu_atcs_call+0x11d/0x19b [amdgpu] [<00000000829cc77d>] amdgpu_acpi_init+0xf3/0x7b8 [amdgpu] [<00000000671194bb>] amdgpu_driver_load_kms+0x1e5/0x354 [amdgpu] [<000000005ad1722a>] amdgpu_pci_probe+0x150/0x1d2 [amdgpu] [<00000000e32ddc8a>] pci_device_probe+0xf3/0x17e [<00000000f74eb70d>] really_probe+0x215/0x539 [<00000000af9fda84>] driver_probe_device+0x9d/0xd6 [<00000000bc527018>] device_driver_attach+0x66/0x8a unreferenced object 0xffff8881700ceb30 (size 56): comm "systemd-udevd", pid 216, jiffies 4294885043 (age 1739.834s) hex dump (first 32 bytes): 88 f9 0c 70 81 88 ff ff 0d 01 2d 00 00 00 00 00 ...p......-..... 7c 98 01 00 00 c9 ff ff 00 00 00 00 00 00 00 00 |............... backtrace: [<00000000f3e5fc85>] kmem_cache_alloc+0x10a/0x1e4 [<00000000fff767c3>] acpi_ps_alloc_op+0x4e/0xdc [<00000000445cacf1>] acpi_ps_create_op+0x24e/0x473 [<000000003452a27a>] acpi_ps_parse_loop+0x25e/0xa39 [<000000004e3469e0>] acpi_ps_parse_aml+0xf3/0x450 [<00000000be1f7fd0>] acpi_ps_execute_method+0x278/0x2bb [<000000004564e9a8>] acpi_ns_evaluate+0x34f/0x45d [<0000000072f73c39>] acpi_evaluate_object+0x201/0x3b5 [<0000000036379e33>] amdgpu_atcs_call+0x11d/0x19b [amdgpu] [<00000000829cc77d>] amdgpu_acpi_init+0xf3/0x7b8 [amdgpu] [<00000000671194bb>] amdgpu_driver_load_kms+0x1e5/0x354 [amdgpu] [<000000005ad1722a>] amdgpu_pci_probe+0x150/0x1d2 [amdgpu] [<00000000e32ddc8a>] pci_device_probe+0xf3/0x17e [<00000000f74eb70d>] really_probe+0x215/0x539 [<00000000af9fda84>] driver_probe_device+0x9d/0xd6 [<00000000bc527018>] device_driver_attach+0x66/0x8a # inxi -bZ System: Host: yea Kernel: 5.13.0-rc3-bdver3 x86_64 bits: 64 Console: tty 1 Distro: Gentoo Base System release 2.7 Machine: Type: Desktop Mobo: ASRock model: FM2A88M Pro3+ serial: N/A UEFI: American Megatrends v: P2.60 date: 01/11/2016 CPU: Info: Quad Core AMD A10 PRO-7800B R7 12 Compute Cores 4C+8G [MCP] speed: 1897 MHz min/max: 1400/3500 MHz Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics] driver: amdgpu v: kernel Display: server: X.org 1.20.11 driver: amdgpu,ati unloaded: fbdev,modesetting tty: 211x54 Message: Advanced graphics data unavailable in console for root. Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 # lspci -s 00:01.0 -vv 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Kaveri [Radeon R7 Graphics] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 56 IOMMU group: 0 Region 0: Memory at c0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at d0000000 (64-bit, prefetchable) [size=8M] Region 4: I/O ports at f000 [size=256] Region 5: Memory at feb00000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ FLReset- DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix+, MaxEETLPPrefixes 1 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee02004 Data: 0029 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270 v1] Secondary PCI Express LnkCtl3: LnkEquIntrruptEn- PerformEqu- LaneErrStat: 0 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 00000020, Page Request Allocation: 00000000 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 10 PASIDCtl: Enable- Exec- Priv- Kernel driver in use: amdgpu Kernel modules: amdgpu -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

1 14

[PATCH v3 0/3] MSM8953 MDP/DSI PHY enablement
by Sireesh Kodali 04 Oct '21

04 Oct '21

This patch series adds support for the MDP and DSI PHY as found on the MSM8953 platform (APQ8053, SDM450, SDA450, SDM625, SDM626). All the SoCs on this platform use the adreno 506 GPU. Changes since v2: - Changed dt-bindings to use enum instead of oneOf Changes since v1: - Split the dsi phy doc changes into a separate commit - Add Reviewed-by tag to patch 2 Sireesh Kodali (1): dt-bindings: msm: dsi: Add MSM8953 dsi phy Vladimir Lypak (2): drm/msm/dsi: Add phy configuration for MSM8953 drm/msm/mdp5: Add configuration for MDP v1.16 .../bindings/display/msm/dsi-phy-14nm.yaml | 1 + drivers/gpu/drm/msm/disp/mdp5/mdp5_cfg.c | 89 +++++++++++++++++++ drivers/gpu/drm/msm/dsi/phy/dsi_phy.c | 2 + drivers/gpu/drm/msm/dsi/phy/dsi_phy.h | 1 + drivers/gpu/drm/msm/dsi/phy/dsi_phy_14nm.c | 21 +++++ 5 files changed, 114 insertions(+) -- 2.33.0

3 5

[PATCH 0/6] *** Add AST2600 GFX node ***
by tommy-huang 04 Oct '21

04 Oct '21

Add AST2600 GFX support first. Joel Stanley (5): ARM: dts: aspeed: Add GFX node to AST2600 ARM: dts: aspeed: ast2600-evb: Enable GFX device drm/aspeed: Add AST2600 support HACK: drm/aspeed: INTR_STS hadndling HACK: drm/aspeed: Paramterise modes tommy-huang (1): dt-bindings: gpu: Add ASPEED GFX bindings document .../devicetree/bindings/gpu/aspeed-gfx.txt | 1 + arch/arm/boot/dts/aspeed-ast2600-evb.dts | 13 +++++++++++++ arch/arm/boot/dts/aspeed-g6.dtsi | 11 +++++++++++ drivers/gpu/drm/aspeed/aspeed_gfx_drv.c | 18 +++++++++++++----- 4 files changed, 38 insertions(+), 5 deletions(-) -- 2.17.1

2 7

[PATCH 2/2] dt-bindings: panel-simple-dsi: add JDI R63452 panel bindings
by Raffaele Tranquillini 04 Oct '21

04 Oct '21

This add the bindings for the JDI FHD_R63452 1080x1920 5.2" LCD DSI panel used on the Xiaomi Mi 5 smartphone. Signed-off-by: Raffaele Tranquillini <raffaele.tranquillini(a)gmail.com> --- .../devicetree/bindings/display/panel/panel-simple-dsi.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/devicetree/bindings/display/panel/panel-simple-dsi.yaml b/Documentation/devicetree/bindings/display/panel/panel-simple-dsi.yaml index fbd71669248f..2c00813f5d20 100644 --- a/Documentation/devicetree/bindings/display/panel/panel-simple-dsi.yaml +++ b/Documentation/devicetree/bindings/display/panel/panel-simple-dsi.yaml @@ -35,6 +35,8 @@ properties: - boe,tv080wum-nl0 # Innolux P079ZCA 7.85" 768x1024 TFT LCD panel - innolux,p079zca + # JDI FHD_R63452 1080x1920 5.2" IPS LCD Panel + - jdi,fhd-r63452 # Khadas TS050 5" 1080x1920 LCD panel - khadas,ts050 # Kingdisplay KD097D04 9.7" 1536x2048 TFT LCD panel -- 2.32.0

2 1

← Newer
1
...
16
17
18
19
20
21
22
...
82
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2021