- 15 Nov, 2022 1 commit
-
-
git://linuxtv.org/pinchartl/mediaDave Airlie authored
- Renesas RZ/G2L DSI support - Renesas DU Kconfig cleanup - Xilinx DPSUB fix Signed-off-by:
Dave Airlie <airlied@redhat.com> From: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Link: https://patchwork.freedesktop.org/patch/msgid/Y2u+mhkPJQ4de3q5@pendragon.ideasonboard.com
-
- 14 Nov, 2022 1 commit
-
-
Ben Skeggs authored
These are fixes from Lyude, and were meant to have been included in the last round of drm-next patches. - Fix some nasty memory issues that broke Lyude's display: - 0 initialize both nvif args and parsed HDMI infoframe buffers - Fixed missing memset(…, 0, …) for nvif args before sending VSI infoframe - Fixed incorrect data pointer and size in nvkm_uoutp_mthd_infoframe() (was previously pointing at the start of the nvif_outp_infoframe_args struct instead of at the start of the infoframe data - Get rid of duplicated scdc assignments, since we only use it to write the scdc registers Signed-off-by:Ben Skeggs <bskeggs@redhat.com> Signed-off-by:
-
- 09 Nov, 2022 38 commits
-
-
Nathan Huckleberry authored
The mode_valid field in drm_bridge_helper_funcs is expected to be of type enum drm_mode_status (* mode_valid) (struct drm_bridge *bridge, struct drm_display_mode *mode); The mismatched return type breaks forward edge kCFI since the underlying function definition does not match the function hook definition. A new warning in clang will catch this at compile time: drivers/gpu/drm/xlnx/zynqmp_dp.c:1573:16: error: incompatible function pointer types initializing 'enum drm_mode_status (*)(struct drm_bridge *, const struct drm_display_info *, const struct drm_display_mode *)' with an expression of type 'int (struct drm_bridge *, const struct drm_display_info *, const struct drm_display_mode *)' [-Werror,-Wincompatible-function-pointer-types-strict] .mode_valid = zynqmp_dp_bridge_mode_valid, ^~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 error generated. The return type of zynqmp_dp_bridge_mode_valid should be changed from int to enum drm_mode_status. Reported-by:Dan Carpenter <error27@gmail.com> Link: https://github.com/ClangBuiltLinux/linux/issues/1703 Link: https://github.com/ClangBuiltLinux/linux/issues/1750Signed-off-by:
Nathan Huckleberry <nhuck@google.com> Reviewed-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> [nathan: Rebase on drm-misc-next and fix conflicts Add note about new clang warning] Signed-off-by:
Nathan Chancellor <nathan@kernel.org> Signed-off-by:
-
Biju Das authored
Enhance device lanes check by reading TXSETR register at probe(), and enforced in rzg2l_mipi_dsi_host_attach(). As per HW manual, we can read TXSETR register only after DPHY initialization. Suggested-by:
Biju Das <biju.das.jz@bp.renesas.com> Reviewed-by:
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Signed-off-by:
-
Biju Das authored
This driver supports the MIPI DSI encoder found in the RZ/G2L SoC. It currently supports DSI video mode only. Signed-off-by:
Sam Ravnborg <sam@ravnborg.org> Reviewed-by:
-
Biju Das authored
The RZ/G2L MIPI DSI TX is embedded in the Renesas RZ/G2L family SoC's. It can operate in DSI mode, with up to four data lanes. Signed-off-by:
Rob Herring <robh@kernel.org> Reviewed-by:
Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by:
-
Laurent Pinchart authored
Commit 841281fe ("drm: rcar-du: Drop LVDS device tree backward compatibility") has removed device tree overlay sources used for backward compatibility with old bindings, but forgot to remove related dependencies from Kconfig. Fix it. Fixes: 841281fe ("drm: rcar-du: Drop LVDS device tree backward compatibility") Reviewed-by:
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com> Signed-off-by:
-
https://gitlab.freedesktop.org/skeggsb/nouveauDave Airlie authored
This is the pull request for a whole bunch of fixes and prep-work that was done to support Ampere acceleration prior to GSP-RM being available. It uses the ACR firmware released by NVIDIA in linux-firmware, as we do on earlier GPUs. The work to support running on top of GSP-RM also heavily depends on various pieces of this series. In addition to the new HW support, general stability of the driver should be improved, especially around recovering HW from bugs that can be generated by userspace driver components. Signed-off-by:
-
Ben Skeggs authored
v2: - whitespace Signed-off-by:
Gourav Samaiya <gsamaiya@nvidia.com>
-
Ben Skeggs authored
v2. fixup for ga103 early merge Signed-off-by:
Lyude Paul <lyude@redhat.com>
-
Ben Skeggs authored
v2. fixup for ga103 early merge Signed-off-by:
-
Ben Skeggs authored
v2. fixup for ga103 early merge Signed-off-by:
-
Ben Skeggs authored
Match RM. Signed-off-by:
-
Ben Skeggs authored
Match RM. Signed-off-by:
-
Ben Skeggs authored
We weren't sending the high bits, though they're zero currently anyway. Signed-off-by:
-
Ben Skeggs authored
NVIDIA provided this on Turing, but we kept using the hardcoded version from Volta (where they didn't). Switch to the firmware version prior to Ampere. Signed-off-by:
-
Ben Skeggs authored
Match RM. Signed-off-by:
-
Ben Skeggs authored
Match RM. Signed-off-by:
-
Ben Skeggs authored
Match RM. Signed-off-by:
-
Ben Skeggs authored
Match RM. Signed-off-by:
-
Ben Skeggs authored
Essentially ripped verbatim from NVGPU, comments and all, and adapted to nvkm's structs and style. - maybe fixes an nvgpu bug though, a small tweak was needed to match RM v2: - remove unnecessary WARN_ON Signed-off-by:
-
Ben Skeggs authored
Match RM. Signed-off-by:
-
Ben Skeggs authored
We'll want to reuse the former for loading from proper netlist images. Signed-off-by:
-
Ben Skeggs authored
Match RM. Signed-off-by:
-
Ben Skeggs authored
We're going to be pulling in a chunk of code from NVGPU to fixup our SMID mappings on Volta and above, which depends on ppc_nr[gpc] reflecting the actual number of PPCs present, not the maximum number. Signed-off-by:
-
Ben Skeggs authored
Ampere. Signed-off-by:
-
Ben Skeggs authored
Ampere. Signed-off-by:
-
Ben Skeggs authored
Ampere. Signed-off-by:
-
Ben Skeggs authored
Ampere. Signed-off-by:
-
Ben Skeggs authored
Match RM. Signed-off-by:
-
Ben Skeggs authored
Match RM. Signed-off-by:
-
Ben Skeggs authored
This doesn't fix any known issue, but RM started doing it at some point, so presumably it's needed for something. Signed-off-by:
-
Ben Skeggs authored
Signed-off-by:
-
Ben Skeggs authored
This won't work on Ampere, and, it's questionable whether we should have been using our FW's method of storing the golden context image with NV's firmware to begin with. Signed-off-by:
-
Ben Skeggs authored
This doesn't work on Ampere for some reason, switch to directly modifying NV_PGRAPH_FECS_CTXSW_MAILBOX instead. Signed-off-by:
-
Ben Skeggs authored
This was thought to be per-channel initially - it's not. The backing pages for the VMM mappings are shared for all channels. - switches to more straight-forward patch interfaces - prepares for sub-context support - this is saving a *sizeable* amount of vram v2: - whitespace Signed-off-by:
-
Ben Skeggs authored
Signed-off-by:
-
Ben Skeggs authored
This was thought to be per-channel initially - it's not. The backing pages for the VMM mappings are shared for all channels. - switches to more straight-forward patch interfaces - prepares for sub-context support Signed-off-by:
-
Ben Skeggs authored
This was thought to be per-channel initially - it's not. The backing pages for the VMM mappings are shared for all channels. - switches to more straight-forward patch interfaces - prepares for sub-context support Signed-off-by:
-
Ben Skeggs authored
Needed for GV100 (and only GV100 for some reason) for WFI_GOLDEN_SAVE. Signed-off-by:
-
