From: "Naladala, Ramanaidu" <Ramanaidu.naladala@intel.com>
To: "B, Jeevan" <jeevan.b@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Sharma, Swati2" <swati2.sharma@intel.com>
Subject: Re: [PATCH i-g-t v1 1/3] lib/igt_kms: Add mode restriction check for Intel scaling
Date: Tue, 8 Apr 2025 22:17:08 +0530 [thread overview]
Message-ID: <cecf3a77-dda7-4d62-b400-a29c99cc317b@intel.com> (raw)
In-Reply-To: <DM4PR11MB631277D5A542425D801C0F7390A02@DM4PR11MB6312.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2818 bytes --]
Hi Jeevan,
On 3/28/2025 2:21 PM, B, Jeevan wrote:
>> -----Original Message-----
>> From: igt-dev<igt-dev-bounces@lists.freedesktop.org> On Behalf Of Naladala
>> Ramanaidu
>> Sent: Friday, March 28, 2025 2:23 AM
>> To:igt-dev@lists.freedesktop.org
>> Cc: Sharma, Swati2<swati2.sharma@intel.com>; Naladala, Ramanaidu
>> <ramanaidu.naladala@intel.com>
>> Subject: [PATCH i-g-t v1 1/3] lib/igt_kms: Add mode restriction check for Intel
>> scaling
>>
>> Add function to verify display mode parameters (horizontal resolution, vertical
>> resolution, refresh rate) within 4K limits for scaling operation.
>>
>> Signed-off-by: Naladala Ramanaidu<ramanaidu.naladala@intel.com>
>> ---
>> lib/igt_kms.c | 23 +++++++++++++++++++++++ lib/igt_kms.h | 1 +
>> 2 files changed, 24 insertions(+)
>>
>> diff --git a/lib/igt_kms.c b/lib/igt_kms.c index 99c8707c7..332f6dbf3 100644
>> --- a/lib/igt_kms.c
>> +++ b/lib/igt_kms.c
>> @@ -93,6 +93,10 @@
>> #define MAX_EDID 2
>> #define DISPLAY_TILE_BLOCK 0x12
>>
>> +#define HDISPLAY_SCALING_MAX 3840
>> +#define VDISPLAY_SCALING_MAX 2160
>> +#define VREFRESH_SCALING_MAX 60
> Can you please mention the spec number or Kernel patch where we have this restrictions mentioned ?
As per Bspec: 49199 Pipe scalers maximum horizontal source size 4096
pixels.
>
>> +
>> typedef bool (*igt_connector_attr_set)(int dir, const char *attr, const char
>> *value);
>>
>> struct igt_connector_attr {
>> @@ -6998,6 +7002,25 @@ int get_num_scalers(igt_display_t *display, enum pipe
>> pipe)
>> return num_scalers;
>> }
>>
>> +/**
>> + * is_intel_support_scaling:
>> + * @drmModeModeInfo *mode: Pointer to a structure with display mode
>> information.
>> + *
>> + * Finds the display mode's horizontal resolution, vertical resolution,
>> +and refresh
>> + * rate are within the specified maximum limits.
>> + *
>> + * Returns: true on success, false on failure */ bool
>> +is_intel_support_scaling(drmModeModeInfo *mode) {
>> + if ((mode->hdisplay <= HDISPLAY_SCALING_MAX) &&
>> + (mode->vdisplay <= VDISPLAY_SCALING_MAX) &&
>> + (mode->vrefresh <= VREFRESH_SCALING_MAX))
>> + return true;
>> +
>> + return false;
>> +}
>> +
>> /**
>> * igt_parse_marked_value:
>> * @buf: Buffer containing the content to parse diff --git a/lib/igt_kms.h
>> b/lib/igt_kms.h index 0381c82ad..0e3d1297d 100644
>> --- a/lib/igt_kms.h
>> +++ b/lib/igt_kms.h
>> @@ -1279,5 +1279,6 @@ void igt_set_link_params(int drm_fd, igt_output_t
>> *output,
>> char *link_rate, char *lane_count); int
>> igt_backlight_read(int *result, const char *fname, igt_backlight_context_t
>> *context); int igt_backlight_write(int value, const char *fname,
>> igt_backlight_context_t *context);
>> +bool is_intel_support_scaling(drmModeModeInfo *mode);
>>
>> #endif /* __IGT_KMS_H__ */
>> --
>> 2.43.0
[-- Attachment #2: Type: text/html, Size: 4578 bytes --]
next prev parent reply other threads:[~2025-04-08 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 20:52 [PATCH i-g-t v1 0/3] Reduce scaling tests log size Naladala Ramanaidu
2025-03-27 20:52 ` [PATCH i-g-t v1 1/3] lib/igt_kms: Add mode restriction check for Intel scaling Naladala Ramanaidu
2025-03-28 8:51 ` B, Jeevan
2025-04-08 16:47 ` Naladala, Ramanaidu [this message]
2025-03-27 20:53 ` [PATCH i-g-t v1 2/3] tests/kms_plane_scaling: Reduce Log Level by Skipping Unsupported Modes in Scaling Tests Naladala Ramanaidu
2025-03-27 20:53 ` [PATCH i-g-t v1 3/3] HAX patch do not merge Naladala Ramanaidu
2025-03-28 2:06 ` ✗ Xe.CI.BAT: failure for Reduce scaling tests log size Patchwork
2025-03-28 8:34 ` ✗ i915.CI.BAT: " Patchwork
2025-03-28 9:57 ` ✗ Xe.CI.BAT: failure for Reduce scaling tests log size (rev2) Patchwork
2025-03-28 10:20 ` ✗ i915.CI.BAT: " Patchwork
2025-03-28 14:33 ` ✗ Xe.CI.Full: failure for Reduce scaling tests log size Patchwork
2025-03-28 21:38 ` ✗ Xe.CI.Full: failure for Reduce scaling tests log size (rev2) Patchwork
2025-04-06 17:22 ` ✗ Xe.CI.Full: failure for Reduce scaling tests log size Patchwork
2025-04-06 18:28 ` ✗ Xe.CI.Full: failure for Reduce scaling tests log size (rev2) 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=cecf3a77-dda7-4d62-b400-a29c99cc317b@intel.com \
--to=ramanaidu.naladala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@intel.com \
--cc=swati2.sharma@intel.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