AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Timur Kristóf" <timur.kristof@gmail.com>
To: amd-gfx@lists.freedesktop.org, Alexander.Deucher@amd.com,
	Mario Limonciello <mario.limonciello@amd.com>,
	Ivan Lipski <ivan.lipski@amd.com>,
	harry.wentland@amd.com, Leo Li <sunpeng.li@amd.com>,
	Alex Hung <alex.hung@amd.com>
Cc: "Timur Kristóf" <timur.kristof@gmail.com>
Subject: [PATCH 0/5] drm/amd/display: Clean up some DCE 6 code
Date: Sun, 18 Jan 2026 18:31:45 +0100	[thread overview]
Message-ID: <20260118173150.19790-1-timur.kristof@gmail.com> (raw)

Reduce code duplication and ease maintenance burden for old
DCE versions. Clean up some code that was duplicated between
DCE 6 and the rest of DCE.

Timur Kristóf (5):
  drm/amd/display: Use dce_audio_create for DCE 6
  drm/amd/display: Delete unused dce_clk_mgr.c
  drm/amd/display: Remove unused dce60_clk_mgr register definitions
  drm/amd/display: Handle DCE 6 in dce_clk_mgr.c
  drm/amd/display: Handle DCE 6 in dce110_register_irq_handlers

 .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 165 +--
 .../gpu/drm/amd/display/dc/clk_mgr/clk_mgr.c  |  12 +-
 .../display/dc/clk_mgr/dce100/dce_clk_mgr.c   |  64 +-
 .../display/dc/clk_mgr/dce60/dce60_clk_mgr.c  | 166 ---
 .../display/dc/clk_mgr/dce60/dce60_clk_mgr.h  |  36 -
 .../gpu/drm/amd/display/dc/dce/dce_audio.c    | 131 ---
 .../gpu/drm/amd/display/dc/dce/dce_audio.h    |   9 -
 .../gpu/drm/amd/display/dc/dce/dce_clk_mgr.c  | 967 ------------------
 .../amd/display/dc/inc/hw/clk_mgr_internal.h  |  11 -
 .../dc/resource/dce60/dce60_resource.c        |   2 +-
 10 files changed, 88 insertions(+), 1475 deletions(-)
 delete mode 100644 drivers/gpu/drm/amd/display/dc/clk_mgr/dce60/dce60_clk_mgr.c
 delete mode 100644 drivers/gpu/drm/amd/display/dc/clk_mgr/dce60/dce60_clk_mgr.h
 delete mode 100644 drivers/gpu/drm/amd/display/dc/dce/dce_clk_mgr.c

-- 
2.52.0


             reply	other threads:[~2026-01-18 17:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-18 17:31 Timur Kristóf [this message]
2026-01-18 17:31 ` [PATCH 1/5] drm/amd/display: Use dce_audio_create for DCE 6 Timur Kristóf
2026-02-02 14:50   ` Rodrigo Siqueira
2026-01-18 17:31 ` [PATCH 2/5] drm/amd/display: Delete unused dce_clk_mgr.c Timur Kristóf
2026-02-02 14:54   ` Rodrigo Siqueira
2026-01-18 17:31 ` [PATCH 3/5] drm/amd/display: Remove unused dce60_clk_mgr register definitions Timur Kristóf
2026-02-03 23:43   ` Rodrigo Siqueira
2026-01-18 17:31 ` [PATCH 4/5] drm/amd/display: Handle DCE 6 in dce_clk_mgr.c Timur Kristóf
2026-01-30 18:47   ` Alex Hung
2026-02-03 23:45   ` Rodrigo Siqueira
2026-02-09 17:21   ` Alex Hung
2026-02-09 22:11     ` Timur Kristóf
2026-02-15  5:06       ` Alex Hung
2026-02-16 15:19         ` Timur Kristóf
2026-02-16 17:49           ` Alex Hung
2026-02-16 18:22             ` Timur Kristóf
2026-01-18 17:31 ` [PATCH 5/5] drm/amd/display: Handle DCE 6 in dce110_register_irq_handlers Timur Kristóf
2026-02-09 15:48 ` [PATCH 0/5] drm/amd/display: Clean up some DCE 6 code Rodrigo Siqueira
2026-02-09 17:25   ` Alex Hung

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260118173150.19790-1-timur.kristof@gmail.com \
    --to=timur.kristof@gmail.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=alex.hung@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=ivan.lipski@amd.com \
    --cc=mario.limonciello@amd.com \
    --cc=sunpeng.li@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox