dri-devel January 2021

dri-devel@lists.freedesktop.org

322 participants
737 discussions

[PATCH v3 0/7] Add support for Adreno 508/509/512
by AngeloGioacchino Del Regno 14 Jan '21

14 Jan '21

In this patch series, we are adding support for lower end Adreno 5 series GPUs, such as A508, A509 and A512 that we have found in the Qualcomm SDM630, SDM636 and SDM660 SoCs. On a note, adding support for these three units, also adds 99% of the required "things" for another two GPUs, A505 and A506 but, even if adding them requires literally two lines of code, noone of us has got any SoC equipped with these ones hence we wouldn't be able to test. Even though there is basically no reason for them to not work correctly, kernel side, I chose to avoid adding the two "magic" lines. Anyway, this patchset also addresses some issues that we've found in the A5XX part of the Adreno driver, regarding a logic mistake in one of the VPC protect values and a forced overwrite of the register named A5XX_PC_DBG_ECO_CNTL, forcing the setting of vtxFifo and primFifo thresholds that was valid only for higher end GPUs. This patch series has been tested on the following devices: - Sony Xperia XA2 Ultra (SDM630 Nile Discovery) - Sony Xperia 10 (SDM630 Ganges Kirin) - Sony Xperia 10 Plus (SDM636 Ganges Mermaid) Changes in v3: - Rebased on 5.11-rc3 - Changed emails to reflect new ones - Tested on F(x)Tec Pro1 and Xperia XZ Premium (MSM8998) Changes in v2: - Define REG_A5XX_UCHE_MODE_CNTL and fix open-coded REG_A5XX_VPC_DBG_ECO_CNTL in the all flat shading optimization disablement commit, as requested by Rob Clark. AngeloGioacchino Del Regno (4): drm/msm/a5xx: Remove overwriting A5XX_PC_DBG_ECO_CNTL register drm/msm/a5xx: Separate A5XX_PC_DBG_ECO_CNTL write from main branch drm/msm/a5xx: Add support for Adreno 508, 509, 512 GPUs drm/msm/a5xx: Reset VBIF before PC only on A510 and A530 Konrad Dybcio (3): drm/msm/a5xx: Fix VPC protect value in gpu_write() drm/msm/a5xx: Disable flat shading optimization drm/msm/a5xx: Disable UCHE global filter drivers/gpu/drm/msm/adreno/a5xx.xml.h | 2 + drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 195 ++++++++++++++++++--- drivers/gpu/drm/msm/adreno/a5xx_power.c | 4 +- drivers/gpu/drm/msm/adreno/adreno_device.c | 52 ++++++ drivers/gpu/drm/msm/adreno/adreno_gpu.h | 15 ++ 5 files changed, 241 insertions(+), 27 deletions(-) -- 2.29.2

2 10

[PATCH rdma-core v5 0/6] Add user space dma-buf support
by Jianxin Xiong 14 Jan '21

14 Jan '21

This is the fifth version of the patch series. Change log: v5: * Use a different mr_type for dmabuf so that ibv_dofork_range() is not called inside ibv_dereg_mr() for dmabuf based mr v4: https://www.spinics.net/lists/linux-rdma/msg98135.html * Rework the cmake funciton rdma_cython_module to support both single source (.pyx) and multiple source (.pyx + [.c]*) scenarios instead of using two separate functions * Rename 'dri_*' to 'drm_*' for the dmabuf allocation interface * Add option to dmabuf allocation routine to allow allocation from GTT instead of VRAM * Add proper CPU access flags when allocating dmabufs * Remove 'radeon' driver support from the dmabuf allocation routines * Add comand line arguments to the tests for selecting GPU unit and setting the option for allocating from GTT v3: https://www.spinics.net/lists/linux-rdma/msg98059.html * Add parameter 'iova' to the new ibv_reg_dmabuf_mr() API * Change the way of allocating dma-buf object - use /dev/dri/renderD* instead of /dev/dri/card* and use GEM object instead of dumb buffer * Add cmake function to allow building modules with mixed cython and C source files * Add new tests that use dma-buf MRs for send/recv and rdma traffic * Skip dma-buf tests on unsupported systems * Remove some use of random values in the new tests * Add dealloc() and close() methods to the new classes * Replace string.format with f-string in python code * Fix some coding style issues: spacing, indentation, typo, comments v2: https://www.spinics.net/lists/linux-rdma/msg97936.html * Put the kernel header updates into a separate commit * Add comments for the data structure used in python ioctl calls * Fix issues related to symbol versioning * Fix styling issues: extra spaces, unncecessary variable, typo * Fix an inproper error code usage * Put the new op into ibv_context_ops instead if verbs_context v1: https://www.spinics.net/lists/linux-rdma/msg97865.html * Add user space API for registering dma-buf based memory regions * Update pyverbs with the new API * Add new tests This is the user space counter-part of the kernel patch set to add dma-buf support to the RDMA subsystem. This series consists of six patches. The first patch updates the kernel headers for dma-buf support. Patch 2 adds the new API function and updates the man pages. Patch 3 implements the new API in the mlx5 provider. Patch 4 adds new class definitions to pyverbs for the new API. Patch 5 adds a set of new tests for the new API. Patch 6 fixes bug in the utility code of the tests. Pull request at github: https://github.com/linux-rdma/rdma-core/pull/895 Jianxin Xiong (6): Update kernel headers verbs: Support dma-buf based memory region mlx5: Support dma-buf based memory region pyverbs: Add dma-buf based MR support tests: Add tests for dma-buf based memory regions tests: Bug fix for get_access_flags() buildlib/pyverbs_functions.cmake | 78 ++++++--- debian/libibverbs1.symbols | 2 + kernel-headers/rdma/ib_user_ioctl_cmds.h | 14 ++ libibverbs/CMakeLists.txt | 2 +- libibverbs/cmd_mr.c | 38 +++++ libibverbs/driver.h | 8 + libibverbs/dummy_ops.c | 11 ++ libibverbs/libibverbs.map.in | 6 + libibverbs/man/ibv_reg_mr.3 | 27 ++- libibverbs/verbs.c | 18 ++ libibverbs/verbs.h | 11 ++ providers/mlx5/mlx5.c | 2 + providers/mlx5/mlx5.h | 3 + providers/mlx5/verbs.c | 22 +++ pyverbs/CMakeLists.txt | 11 +- pyverbs/dmabuf.pxd | 15 ++ pyverbs/dmabuf.pyx | 73 ++++++++ pyverbs/dmabuf_alloc.c | 278 +++++++++++++++++++++++++++++++ pyverbs/dmabuf_alloc.h | 19 +++ pyverbs/libibverbs.pxd | 2 + pyverbs/mr.pxd | 6 + pyverbs/mr.pyx | 105 +++++++++++- tests/args_parser.py | 4 + tests/test_mr.py | 264 ++++++++++++++++++++++++++++- tests/utils.py | 30 +++- 25 files changed, 1013 insertions(+), 36 deletions(-) create mode 100644 pyverbs/dmabuf.pxd create mode 100644 pyverbs/dmabuf.pyx create mode 100644 pyverbs/dmabuf_alloc.c create mode 100644 pyverbs/dmabuf_alloc.h -- 1.8.3.1

1 6

[pull] amdgpu, amdkfd drm-fixes-5.11
by Alex Deucher 14 Jan '21

14 Jan '21

Hi Dave, Daniel, Fixes for 5.11. The following changes since commit 7c53f6b671f4aba70ff15e1b05148b10d58c2837: Linux 5.11-rc3 (2021-01-10 14:34:50 -0800) are available in the Git repository at: https://gitlab.freedesktop.org/agd5f/linux.git tags/amd-drm-fixes-5.11-2021-01-14 for you to fetch changes up to 2f0fa789f7b9fb022440f8f846cae175233987aa: drm/amd/display: Fix to be able to stop crc calculation (2021-01-14 14:06:43 -0500) ---------------------------------------------------------------- amd-drm-fixes-5.11-2021-01-14: amdgpu: - Update repo location in MAINTAINERS - Add some new renoir PCI IDs - Revert CRC UAPI changes - Revert OLED display fix which cases clocking problems for some systems - Misc vangogh fixes - GFX fix for sienna cichlid - DCN1.0 fix for pipe split - Fix incorrect PSP command amdkfd: - Fix possible out of bounds read in vcrat creation ---------------------------------------------------------------- Alex Deucher (1): MAINTAINERS: update radeon/amdgpu/amdkfd git trees Alexandre Demers (1): drm/amdgpu: fix DRM_INFO flood if display core is not supported (bug 210921) Huang Rui (1): drm/amdgpu: fix vram type and bandwidth error for DDR5 and DDR4 Jeremy Cline (1): drm/amdkfd: Fix out-of-bounds read in kdf_create_vcrat_image_cpu() Li, Roman (1): drm/amd/display: disable dcn10 pipe split by default Likun Gao (1): drm/amdgpu: set power brake sequence Nikola Cornij (1): drm/amd/display: Add a missing DCN3.01 API mapping Prike Liang (1): drm/amdgpu: add green_sardine device id (v2) Qingqing Zhuo (1): drm/amd/display: NULL pointer hang Rodrigo Siqueira (4): Revert "drm/amd/display: Fixed Intermittent blue screen on OLED panel" Revert "drm/amd/display: Fix unused variable warning" Revert "drm/amdgpu/disply: fix documentation warnings in display manager" Revert "drm/amd/display: Expose new CRC window property" Victor Zhao (1): drm/amdgpu/psp: fix psp gfx ctrl cmds Wayne Lin (1): drm/amd/display: Fix to be able to stop crc calculation Wesley Chalmers (1): drm/amd/display: Initialize stack variable chen gong (1): drm/amdgpu/gfx10: add updated GOLDEN_TSC_COUNT_UPPER/LOWER register offsets for VGH mengwang (1): drm/amdgpu: add new device id for Renior MAINTAINERS | 4 +- drivers/gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c | 53 +++++--- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 2 +- drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 2 + drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c | 48 ++++++- drivers/gpu/drm/amd/amdgpu/psp_gfx_if.h | 2 +- drivers/gpu/drm/amd/amdgpu/soc15.c | 3 +- drivers/gpu/drm/amd/amdkfd/kfd_crat.c | 11 +- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 142 ++------------------- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h | 38 ------ .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crc.c | 54 +------- .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crc.h | 5 +- drivers/gpu/drm/amd/display/dc/core/dc_link_dp.c | 8 +- drivers/gpu/drm/amd/display/dc/dcn10/dcn10_mpc.c | 2 +- .../gpu/drm/amd/display/dc/dcn10/dcn10_resource.c | 4 +- .../drm/amd/display/dc/dcn301/dcn301_resource.c | 1 + .../display/dc/dml/dcn20/display_mode_vba_20v2.c | 11 +- 17 files changed, 125 insertions(+), 265 deletions(-)

1 0

[Bug 211189] vgaarb overrides boot device unexpectedly with Intel and discrete AMDGPU
by bugzilla-daemon＠bugzilla.kernel.org 14 Jan '21

14 Jan '21

https://bugzilla.kernel.org/show_bug.cgi?id=211189 Alex Deucher (alexdeucher(a)gmail.com) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexdeucher(a)gmail.com --- Comment #2 from Alex Deucher (alexdeucher(a)gmail.com) --- Please attach your dmesg output. I agree this looks like an sbios issue since the the efifb is apparently bound to the radeon chip. -- 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 0

Re: [Bug 211189] New: vgaarb overrides boot device unexpectedly with Intel and discrete AMDGPU
by Bjorn Helgaas 14 Jan '21

14 Jan '21

[cc'd efifb and vgaarb maintainers on bugzilla, but not sure whether people pay attention to that] On Thu, Jan 14, 2021 at 10:42:53AM +0000, bugzilla-daemon(a)bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=211189 > > Bug ID: 211189 > Summary: vgaarb overrides boot device unexpectedly with Intel > and discrete AMDGPU > Product: Drivers > Version: 2.5 > Kernel Version: 5.10.7-200.fc33.x86_64 > Hardware: x86-64 > OS: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: PCI > Assignee: drivers_pci(a)kernel-bugs.osdl.org > Reporter: dominik(a)greysector.net > Regression: No > > The system is a MSI Z77A-GD65 mainboard configured to boot in UEFI mode. > Despite setting integrated GPU (from i5-3570K CPU) as the default in firmware > setup, the kernel sets the discrete GPU (Radeon HD 7950) as boot_vga. This > results in wrong order in e.g. switcherooctl: > $ switcherooctl list > Device: 0 > Name: Advanced Micro Devices, Inc. [AMD®/ATI] Tahiti PRO [Radeon HD > 7950/8950 OEM / R9 280] > Default: yes > Environment: DRI_PRIME=pci-0000_01_00_0 > > Device: 1 > Name: Intel® HD Graphics 4000 > Default: no > Environment: DRI_PRIME=pci-0000_00_02_0 > $ lspci -vnn > ... > 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd > Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA > controller]) > DeviceName: Onboard IGD > Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2111] > Flags: bus master, fast devsel, latency 0, IRQ 31 > Memory at f7800000 (64-bit, non-prefetchable) [size=4M] > Memory at d0000000 (64-bit, prefetchable) [size=256M] > I/O ports at f000 [size=64] > Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [d0] Power Management version 2 > Capabilities: [a4] PCI Advanced Features > Kernel driver in use: i915 > Kernel modules: i915 > ... > 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. > [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 > [VGA controller]) > Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2761] > Flags: bus master, fast devsel, latency 0, IRQ 32 > Memory at e0000000 (64-bit, prefetchable) [size=256M] > Memory at f7d00000 (64-bit, non-prefetchable) [size=256K] > I/O ports at e000 [size=256] > Expansion ROM at 000c0000 [disabled] [size=128K] > Capabilities: [48] Vendor Specific Information: Len=08 <?> > Capabilities: [50] Power Management version 3 > Capabilities: [58] Express Legacy Endpoint, MSI 00 > Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 > <?> > Capabilities: [150] Advanced Error Reporting > Capabilities: [270] Secondary PCI Express > Capabilities: [2b0] Address Translation Service (ATS) > Capabilities: [2c0] Page Request Interface (PRI) > Capabilities: [2d0] Process Address Space ID (PASID) > Kernel driver in use: amdgpu > Kernel modules: radeon, amdgpu > > $ for f in /sys/bus/pci/devices/*/boot_vga ; do echo -n "$f:" ; cat $f ; done > /sys/bus/pci/devices/0000:00:02.0/boot_vga:0 > /sys/bus/pci/devices/0000:01:00.0/boot_vga:1 > > $ dmesg > ... > [ 0.267216] pci 0000:01:00.0: BAR 0: assigned to efifb This is from drivers/video/fbdev/efifb.c and makes me wonder if this is a firmware defect. You set 00:02.0 to be the default in firmware setup, but apparently the EFI FB is using 01:00.0? > [ 0.268571] pci 0000:00:02.0: vgaarb: setting as boot VGA device > [ 0.268571] pci 0000:00:02.0: vgaarb: VGA device added: > decodes=io+mem,owns=io+mem,locks=none > [ 0.268571] pci 0000:01:00.0: vgaarb: VGA device added: > decodes=io+mem,owns=io+mem,locks=none > [ 0.268571] pci 0000:00:02.0: vgaarb: no bridge control possible > [ 0.268571] pci 0000:01:00.0: vgaarb: bridge control possible > [ 0.268571] pci 0000:01:00.0: vgaarb: overriding boot device > [ 0.268571] vgaarb: loaded > [ 0.754748] efifb: probing for efifb > [ 0.754766] efifb: No BGRT, not showing boot graphics > [ 0.754768] efifb: framebuffer at 0xe0000000, using 8100k, total 8100k > [ 0.754769] efifb: mode is 1920x1080x32, linelength=7680, pages=1 > [ 0.754770] efifb: scrolling: redraw > [ 0.754772] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 > [ 2.984727] i915 0000:00:02.0: vgaarb: changed VGA decodes: > olddecodes=io+mem,decodes=none:owns=io+mem > [ 3.011601] [drm] Initialized i915 1.6.0 20200917 for 0000:00:02.0 on minor > 0 > [ 3.213870] [drm] amdgpu kernel modesetting enabled. > [ 3.275739] i915 0000:00:02.0: [drm] fb1: i915drmfb frame buffer device > [ 3.275972] fb0: switching to amdgpudrmfb from EFI VGA > [ 3.276112] amdgpu 0000:01:00.0: vgaarb: deactivate vga console > [ 3.276240] [drm] initializing kernel modesetting (TAHITI 0x1002:0x679A > 0x1462:0x2761 0x00). > ... > [ 4.069577] amdgpu 0000:01:00.0: [drm] fb0: amdgpudrmfb frame buffer device > [ 4.351324] [drm] Initialized amdgpu 3.40.0 20150101 for 0000:01:00.0 on > minor 1 > > -- > 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 0

[Bug 211189] vgaarb overrides boot device unexpectedly with Intel and discrete AMDGPU
by bugzilla-daemon＠bugzilla.kernel.org 14 Jan '21

14 Jan '21

https://bugzilla.kernel.org/show_bug.cgi?id=211189 Bjorn Helgaas (bjorn(a)helgaas.com) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |airlied(a)linux.ie, | |bjorn(a)helgaas.com, | |pjones(a)redhat.com Component|PCI |Video(DRI - non Intel) Assignee|drivers_pci(a)kernel-bugs.osd |drivers_video-dri@kernel-bu |l.org |gs.osdl.org --- Comment #1 from Bjorn Helgaas (bjorn(a)helgaas.com) --- Reassigning to video/DRI since I don't think this is a PCI problem. If the integrated GPU (00:02.0) is set to the default in firmware setup, this: pci 0000:01:00.0: BAR 0: assigned to efifb makes me wonder if this is a firmware issue. -- 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 0

[PATCH v6 0/4] drm/i915: Add support for Intel's eDP backlight controls
by Lyude Paul 14 Jan '21

14 Jan '21

A while ago we ran into issues while trying to enable the eDP backlight control interface as defined by VESA, in order to make the DPCD backlight controls on newer laptop panels work. The issue ended up being much more complicated however, as we also apparently needed to add support for an Intel-specific DPCD backlight control interface as the VESA interface is broken on many laptop panels. For lack of a better name, we just call this the Intel HDR backlight interface. While this only adds support for the SDR backlight mode (I think), this will fix a lot of user's laptop panels that we weren't able to properly automatically detect DPCD backlight controls on previously. Series-wide changes in v3: * Pass down brightness values to enable/disable backlight callbacks in a separate patch * Rebase Lyude Paul (4): drm/i915: Keep track of pwm-related backlight hooks separately drm/i915/dp: Enable Intel's HDR backlight interface (only SDR for now) drm/i915/dp: Allow forcing specific interfaces through enable_dpcd_backlight drm/dp: Revert "drm/dp: Introduce EDID-based quirks" drivers/gpu/drm/drm_dp_helper.c | 83 +--- drivers/gpu/drm/drm_dp_mst_topology.c | 3 +- .../drm/i915/display/intel_display_types.h | 14 +- drivers/gpu/drm/i915/display/intel_dp.c | 9 +- .../drm/i915/display/intel_dp_aux_backlight.c | 286 ++++++++++++-- drivers/gpu/drm/i915/display/intel_dp_mst.c | 3 +- drivers/gpu/drm/i915/display/intel_panel.c | 368 +++++++++++------- drivers/gpu/drm/i915/display/intel_panel.h | 4 + drivers/gpu/drm/i915/display/intel_psr.c | 2 +- drivers/gpu/drm/i915/i915_params.c | 2 +- include/drm/drm_dp_helper.h | 21 +- 11 files changed, 504 insertions(+), 291 deletions(-) -- 2.29.2

2 7

[PATCH] drm/amd/display: Simplify bool comparison
by Yang Li 14 Jan '21

14 Jan '21

Fix the following coccicheck warning: ./drivers/gpu/drm/amd/display/dc/dml/dcn20/display_mode_vba_20.c:3141:30-39: WARNING: Comparison to bool Reported-by: Abaci Robot <abaci(a)linux.alibaba.com> Signed-off-by: Yang Li <abaci-bugfix(a)linux.alibaba.com> --- drivers/gpu/drm/amd/display/dc/dml/dcn20/display_mode_vba_20.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/display/dc/dml/dcn20/display_mode_vba_20.c b/drivers/gpu/drm/amd/display/dc/dml/dcn20/display_mode_vba_20.c index 45f0289..f33e3de 100644 --- a/drivers/gpu/drm/amd/display/dc/dml/dcn20/display_mode_vba_20.c +++ b/drivers/gpu/drm/amd/display/dc/dml/dcn20/display_mode_vba_20.c @@ -3138,7 +3138,7 @@ static void CalculateFlipSchedule( 4.0 * (TimeForFetchingMetaPTEImmediateFlip / LineTime + 0.125), 1) / 4.0; - if ((GPUVMEnable == true || DCCEnable == true)) { + if ((GPUVMEnable || DCCEnable)) { mode_lib->vba.ImmediateFlipBW[0] = BandwidthAvailableForImmediateFlip * ImmediateFlipBytes / TotImmediateFlipBytes; TimeForFetchingRowInVBlankImmediateFlip = dml_max( -- 1.8.3.1

2 1

[PATCH] drm/amdgpu: Repeat assignment to max_slave_planes
by ZhiJie.Zhang 14 Jan '21

14 Jan '21

Signed-off-by: ZhiJie.Zhang <zhangzhijie(a)loongson.cn> --- drivers/gpu/drm/amd/display/dc/dce110/dce110_resource.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/amd/display/dc/dce110/dce110_resource.c b/drivers/gpu/drm/amd/display/dc/dce110/dce110_resource.c index 3f63822b8e28..9a86d43a6233 100644 --- a/drivers/gpu/drm/amd/display/dc/dce110/dce110_resource.c +++ b/drivers/gpu/drm/amd/display/dc/dce110/dce110_resource.c @@ -1272,7 +1272,6 @@ static bool underlay_create(struct dc_context *ctx, struct resource_pool *pool) /* update the public caps to indicate an underlay is available */ ctx->dc->caps.max_slave_planes = 1; - ctx->dc->caps.max_slave_planes = 1; return true; } -- 2.29.2

2 1

[PATCH 00/10] Fix documentation warnings at linux-next
by Mauro Carvalho Chehab 14 Jan '21

14 Jan '21

This series fixes the documentation warnings found at next-20210114. Most of the changes here are trivial. While those patches could be merged via the docs tree during the next merge window, It sounds better to have those patches merged directly via each maintainer's tree, where the new warnings were introduced. Regards, Mauro Mauro Carvalho Chehab (10): doc/zh_CN: fix Sphinx errors ABI: sysfs-fs-f2fs: fix a table identation KVM: x86: hyper-v: add a blank line to remove building warnings ABI: sysfs-firmware-sgi_uv docs: fpga: dfl.rst: Fix a couple building issues drm: amd: amdgpu_dm.h: fix a wrong kernel-doc markup dwc3: document gadget_max_speed doc: zh_CN/mips: fix doc cross-references media: v4l2-subdev.rst: fix a missing whitespace seqlock: kernel-doc: fix a prototype Documentation/ABI/testing/sysfs-firmware-sgi_uv | 1 + Documentation/ABI/testing/sysfs-fs-f2fs | 3 ++- Documentation/driver-api/media/v4l2-subdev.rst | 2 +- Documentation/fpga/dfl.rst | 4 ++-- Documentation/translations/zh_CN/mips/booting.rst | 2 +- Documentation/translations/zh_CN/mips/features.rst | 2 +- Documentation/translations/zh_CN/mips/index.rst | 2 +- Documentation/translations/zh_CN/mips/ingenic-tcu.rst | 6 +++--- Documentation/virt/kvm/api.rst | 1 + drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h | 2 +- drivers/usb/dwc3/core.h | 1 + include/linux/seqlock.h | 2 +- 12 files changed, 16 insertions(+), 12 deletions(-) -- 2.29.2

3 3

← Newer
1
...
49
50
51
52
53
54
55
...
74
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2021