From: Alex Hung <alex.hung@amd.com>
To: Aurabindo Pillai <aurabindo.pillai@amd.com>,
igt-dev@lists.freedesktop.org
Cc: hersenxs.wu@amd.com
Subject: Re: [igt-dev] [PATCH v2 1/2] lib/amdgpu: Add check for ODM combine segments debugfs endpoint
Date: Fri, 18 Aug 2023 15:02:48 -0600 [thread overview]
Message-ID: <2792a229-769e-d894-6f6e-7e87e7a19e27@amd.com> (raw)
In-Reply-To: <20230818175637.419349-1-aurabindo.pillai@amd.com>
On 2023-08-18 11:56, Aurabindo Pillai wrote:
> Signed-off-by: Aurabindo Pillai <aurabindo.pillai@amd.com>
> ---
> lib/igt_amd.c | 10 ++++++++++
> lib/igt_amd.h | 4 ++++
> 2 files changed, 14 insertions(+)
>
> diff --git a/lib/igt_amd.c b/lib/igt_amd.c
> index 83011e8ca..1a720ff56 100644
> --- a/lib/igt_amd.c
> +++ b/lib/igt_amd.c
> @@ -325,6 +325,16 @@ static bool igt_amd_output_has_dsc(int drm_fd, char *connector_name)
> return igt_amd_output_has_debugfs(drm_fd, connector_name, DEBUGFS_DSC_CLOCK_EN);
> }
>
> +/**
> + * igt_amd_output_has_odm_combine_segments: check if connector has dsc debugfs entry
> + * @drm_fd: DRM file descriptor
> + * @connector_name: The connector's name, on which we're reading the status
> + */
> +bool igt_amd_output_has_odm_combine_segments(int drm_fd, char *connector_name)
> +{
> + return igt_amd_output_has_debugfs(drm_fd, connector_name, DEBUGFS_ODM_COMBINE_SEG);
> +}
This helper function is the same as one line igt_amd_output_has_debugfs
and it is only used once in patch 2. The log in patch 2 seems to explain
its purpose quite well too.
Is there a special reason to have a new helper function? Do you expect
the check for ODM combine SEG will change or expand?
Alex
> +
> /**
> * is_dp_dsc_supported: Checks if connector is DSC capable
> * @display: A pointer to an #igt_display_t structure
> diff --git a/lib/igt_amd.h b/lib/igt_amd.h
> index 6f538a195..c05b4b730 100644
> --- a/lib/igt_amd.h
> +++ b/lib/igt_amd.h
> @@ -54,6 +54,9 @@
> #define DEBUGFS_DM_VISUAL_CONFIRM "amdgpu_dm_visual_confirm"
> #define DEBUGFS_DM_CAPABILITIES "amdgpu_dm_capabilities"
>
> +/* ODM Combine */
> +#define DEBUGFS_ODM_COMBINE_SEG "odm_combine_segments"
> +
> enum amd_dsc_clock_force {
> DSC_AUTOMATIC = 0,
> DSC_FORCE_ON,
> @@ -197,4 +200,5 @@ int igt_amd_get_visual_confirm(int drm_fd);
> bool igt_amd_set_visual_confirm(int drm_fd, enum amdgpu_debug_visual_confirm option);
>
> bool igt_amd_is_mall_capable(int drm_fd);
> +bool igt_amd_output_has_odm_combine_segments(int drm_fd, char *connector_name);
> #endif /* IGT_AMD_H */
next prev parent reply other threads:[~2023-08-18 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 17:56 [igt-dev] [PATCH v2 1/2] lib/amdgpu: Add check for ODM combine segments debugfs endpoint Aurabindo Pillai
2023-08-18 17:56 ` [igt-dev] [PATCH v2 2/2] tests/amdgpu: Add test for ODM combine Aurabindo Pillai
2023-08-18 21:20 ` Alex Hung
2023-08-21 8:27 ` Kamil Konieczny
2023-08-18 18:27 ` [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [v2,1/2] lib/amdgpu: Add check for ODM combine segments debugfs endpoint Patchwork
2023-08-18 18:48 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-08-18 19:00 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-08-18 21:02 ` Alex Hung [this message]
2023-08-21 15:41 ` [igt-dev] [PATCH v2 1/2] " Aurabindo Pillai
2023-08-19 21:34 ` [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [v2,1/2] " Patchwork
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=2792a229-769e-d894-6f6e-7e87e7a19e27@amd.com \
--to=alex.hung@amd.com \
--cc=aurabindo.pillai@amd.com \
--cc=hersenxs.wu@amd.com \
--cc=igt-dev@lists.freedesktop.org \
/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