mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rodrigo Siqueira Jordao <rjordrigo@amd.com>
To: Melissa Wen <mwen@igalia.com>,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	airlied@linux.ie, alexander.deucher@amd.com,
	christian.koenig@amd.com, daniel@ffwll.ch,
	harry.wentland@amd.com, Rodrigo.Siqueira@amd.com,
	sunpeng.li@amd.com, Xinhui.Pan@amd.com
Cc: Qingqing Zhuo <qingqing.zhuo@amd.com>,
	Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com>,
	linux-kernel@vger.kernel.org, Jasdeep Dhillon <jdhillon@amd.com>
Subject: Re: [PATCH 0/3] Move FPU related code from DCN3.1x drivers to DML folder
Date: Wed, 16 Mar 2022 08:49:33 -0400	[thread overview]
Message-ID: <f1f242ca-4701-9352-7a88-38c546f3cabe@amd.com> (raw)
In-Reply-To: <20220307154801.2196284-1-mwen@igalia.com>



On 2022-03-07 10:47, Melissa Wen wrote:
> This series moves FPU code from DCN 3.1x drivers to dml/dcn31 folder to
> isolate FPU operations. For this, it creates dcn31_fpu files to centralize
> FPU operations and structs from dcn31x drivers, that include:
> - _vcs_dpi_ip_params_st and _vcs_dpi_soc_bounding_box_st structs
> - dcn31x_update_bw_bounding_box() functions
> - dcn31_calculate_wm_and_dlg_fp()
> 
> Also, it adds dc_assert_fp_enabled() in public dml-fpu functions, as required,
> and I've checked if their calls are properly wrapped by DC_FP_START/END (and
> removed when inside dml/fpu files too).
> 
> Melissa Wen (3):
>    drm/amd/dicplay: move FPU related code from dcn31 to dml/dcn31 folder
>    drm/amd/display: move FPU related code from dcn315 to dml/dcn31 folder
>    drm/amd/display: move FPU related code from dcn316 to dml/dcn31 folder
> 
>   drivers/gpu/drm/amd/display/dc/dcn31/Makefile |  26 -
>   .../drm/amd/display/dc/dcn31/dcn31_resource.c | 355 +------
>   .../drm/amd/display/dc/dcn31/dcn31_resource.h |   4 +-
>   .../gpu/drm/amd/display/dc/dcn315/Makefile    |  26 -
>   .../amd/display/dc/dcn315/dcn315_resource.c   | 232 +----
>   .../amd/display/dc/dcn315/dcn315_resource.h   |   3 +
>   .../gpu/drm/amd/display/dc/dcn316/Makefile    |  26 -
>   .../amd/display/dc/dcn316/dcn316_resource.c   | 231 +----
>   .../amd/display/dc/dcn316/dcn316_resource.h   |   3 +
>   drivers/gpu/drm/amd/display/dc/dml/Makefile   |   2 +
>   .../drm/amd/display/dc/dml/dcn31/dcn31_fpu.c  | 863 ++++++++++++++++++
>   .../drm/amd/display/dc/dml/dcn31/dcn31_fpu.h  |  44 +
>   12 files changed, 921 insertions(+), 894 deletions(-)
>   create mode 100644 drivers/gpu/drm/amd/display/dc/dml/dcn31/dcn31_fpu.c
>   create mode 100644 drivers/gpu/drm/amd/display/dc/dml/dcn31/dcn31_fpu.h
> 

Hi Melissa,

Thanks a lot for your patchset. We have already tested it with IGT, and 
we are running some manual tests to ensure that everything is fine. We 
will include your patch in this week's DC upstream, and if everything is 
alright, we will merge it next Monday.


      parent reply	other threads:[~2022-03-16 12:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 15:47 Melissa Wen
2022-03-07 15:47 ` [PATCH 1/3] drm/amd/dicplay: move FPU related code from dcn31 to dml/dcn31 folder Melissa Wen
2022-03-07 15:48 ` [PATCH 2/3] drm/amd/display: move FPU related code from dcn315 " Melissa Wen
2022-03-07 15:48 ` [PATCH 3/3] drm/amd/display: move FPU related code from dcn316 " Melissa Wen
2022-03-16 12:49 ` Rodrigo Siqueira Jordao [this message]

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=f1f242ca-4701-9352-7a88-38c546f3cabe@amd.com \
    --to=rjordrigo@amd.com \
    --cc=Dmytro.Laktyushkin@amd.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=jdhillon@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mwen@igalia.com \
    --cc=qingqing.zhuo@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

all inboxes | Powered by JetHome®