From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Stanislav Lisovskiy" <stanislav.lisovskiy@intel.com>
Cc: jani.nikula@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Add bigjoiner force enable option to debugfs
Date: Wed, 17 Jan 2024 22:16:39 +0530 [thread overview]
Message-ID: <94796951-a166-43fa-b476-a8522c8a272d@intel.com> (raw)
In-Reply-To: <ZTkRRRf2lTksA_a2@intel.com>
Hi Ville,
On 25-Oct-23 6:29 PM, Ville Syrjälä wrote:
> On Wed, Oct 18, 2023 at 04:24:00PM +0300, Stanislav Lisovskiy wrote:
>> For validation purposes, it might be useful to be able to
>> force Bigjoiner mode, even if current dotclock/resolution
>> do not require that.
>> Lets add such to option to debugfs.
>>
>> v2: - Apparently intel_dp_need_bigjoiner can't be used, when
>> debugfs entry is created so lets just check manually
>> the DISPLAY_VER.
>>
>> v3: - Switch to intel_connector from drm_connector(Jani Nikula)
>> - Remove redundant modeset lock(Jani Nikula)
>> - Use kstrtobool_from_user for boolean value(Jani Nikula)
>>
>> v4: - Apply the changes to proper function(Jani Nikula)
>>
>> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
>> ---
>> .../drm/i915/display/intel_display_debugfs.c | 66 +++++++++++++++++++
>> .../drm/i915/display/intel_display_types.h | 2 +
>> drivers/gpu/drm/i915/display/intel_dp.c | 6 +-
>> 3 files changed, 73 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> index fbe75d47a165..9b810c6f96ea 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
>> @@ -1398,6 +1398,30 @@ out: drm_modeset_unlock(&dev->mode_config.connection_mutex);
>> return ret;
>> }
>>
>> +static int i915_bigjoiner_enable_show(struct seq_file *m, void *data)
>> +{
>> + struct intel_connector *connector = to_intel_connector(m->private);
>> + struct drm_crtc *crtc;
>> + struct intel_encoder *encoder = intel_attached_encoder(connector);
>> + struct intel_dp *intel_dp = enc_to_intel_dp(encoder);
>> + int ret = 0;
>> +
>> + if (!encoder)
>> + return -ENODEV;
>> +
>> + crtc = connector->base.state->crtc;
>> + if (connector->base.status != connector_status_connected || !crtc) {
>> + ret = -ENODEV;
>
> Why do we need this extra complication?
>
>> + goto out;
>> + }
>> +
>> + seq_printf(m, "Bigjoiner enable: %d\n", intel_dp->force_bigjoiner_enable);
>> +
>> +out:
>> +
>> + return ret;
>> +}
>> +
>> static ssize_t i915_dsc_output_format_write(struct file *file,
>> const char __user *ubuf,
>> size_t len, loff_t *offp)
>> @@ -1419,12 +1443,39 @@ static ssize_t i915_dsc_output_format_write(struct file *file,
>> return len;
>> }
>>
>> +static ssize_t i915_bigjoiner_enable_fops_write(struct file *file,
>> + const char __user *ubuf,
>> + size_t len, loff_t *offp)
>> +{
>> + struct seq_file *m = file->private_data;
>> + struct intel_connector *connector = m->private;
>> + struct intel_encoder *encoder = intel_attached_encoder(connector);
>> + struct intel_dp *intel_dp = enc_to_intel_dp(encoder);
>> + bool bigjoiner_en = 0;
>> + int ret;
>> +
>> + ret = kstrtobool_from_user(ubuf, len, &bigjoiner_en);
>> + if (ret < 0)
>> + return ret;
>> +
>> + intel_dp->force_bigjoiner_enable = bigjoiner_en;
>> + *offp += len;
>> +
>> + return len;
>> +}
>> +
>> static int i915_dsc_output_format_open(struct inode *inode,
>> struct file *file)
>> {
>> return single_open(file, i915_dsc_output_format_show, inode->i_private);
>> }
>>
>> +static int i915_bigjoiner_enable_open(struct inode *inode,
>> + struct file *file)
>> +{
>> + return single_open(file, i915_bigjoiner_enable_show, inode->i_private);
>> +}
>> +
>> static const struct file_operations i915_dsc_output_format_fops = {
>> .owner = THIS_MODULE,
>> .open = i915_dsc_output_format_open,
>> @@ -1434,6 +1485,15 @@ static const struct file_operations i915_dsc_output_format_fops = {
>> .write = i915_dsc_output_format_write
>> };
>>
>> +static const struct file_operations i915_bigjoiner_enable_fops = {
>> + .owner = THIS_MODULE,
>> + .open = i915_bigjoiner_enable_open,
>> + .read = seq_read,
>> + .llseek = seq_lseek,
>> + .release = single_release,
>> + .write = i915_bigjoiner_enable_fops_write
>> +};
>> +
>> /*
>> * Returns the Current CRTC's bpc.
>> * Example usage: cat /sys/kernel/debug/dri/0/crtc-0/i915_current_bpc
>> @@ -1513,6 +1573,12 @@ void intel_connector_debugfs_add(struct intel_connector *intel_connector)
>> connector, &i915_dsc_output_format_fops);
>> }
>>
>> + if (DISPLAY_VER(dev_priv) >= 11 &&
>> + intel_connector->base.connector_type == DRM_MODE_CONNECTOR_DisplayPort) {
>
> eDP missing
>
>> + debugfs_create_file("i915_bigjoiner_force_enable", 0644, root,
>> + &intel_connector->base, &i915_bigjoiner_enable_fops);
>> + }
>> +
>> if (connector->connector_type == DRM_MODE_CONNECTOR_DSI ||
>> connector->connector_type == DRM_MODE_CONNECTOR_eDP ||
>> connector->connector_type == DRM_MODE_CONNECTOR_DisplayPort ||
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h
>> index 8d8b2f8d37a9..e0de6eeaf59e 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_types.h
>> +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
>> @@ -1753,6 +1753,8 @@ struct intel_dp {
>> bool is_mst;
>> int active_mst_links;
>>
>> + bool force_bigjoiner_enable;
>> +
>> /* connector directly attached - won't be use for modeset in mst world */
>> struct intel_connector *attached_connector;
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
>> index 4f6835a7578e..6a9148232a9c 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>> @@ -1153,7 +1153,11 @@ bool intel_dp_need_bigjoiner(struct intel_dp *intel_dp,
>> if (!intel_dp_can_bigjoiner(intel_dp))
>> return false;
>>
>> - return clock > i915->max_dotclk_freq || hdisplay > 5120;
>> + if (intel_dp->force_bigjoiner_enable)
>> + drm_dbg_kms(&i915->drm, "Forcing bigjoiner mode\n");
>
> That's going to cause excessive dmesg spam.
Then how from dmesg we will get to know, big joiner was forced?
Shouldn't we have atleast one debug print to know this?
>
>> +
>> + return clock > i915->max_dotclk_freq || hdisplay > 5120 ||
>> + intel_dp->force_bigjoiner_enable;
>> }
>>
>> static enum drm_mode_status
>> --
>> 2.37.3
>
next prev parent reply other threads:[~2024-01-17 16:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 13:24 [Intel-gfx] [PATCH] drm/i915: Add bigjoiner force enable option to debugfs Stanislav Lisovskiy
2023-10-18 23:17 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Add bigjoiner force enable option to debugfs (rev4) Patchwork
2023-10-25 12:59 ` [Intel-gfx] [PATCH] drm/i915: Add bigjoiner force enable option to debugfs Ville Syrjälä
2024-01-17 16:46 ` Sharma, Swati2 [this message]
2024-01-17 18:01 ` Jani Nikula
2024-01-18 6:01 ` Sharma, Swati2
-- strict thread matches above, loose matches on Subject: below --
2023-11-16 10:37 Stanislav Lisovskiy
2023-11-16 13:48 ` Modem, Bhanuprakash
2023-10-12 12:34 Stanislav Lisovskiy
2023-10-12 14:59 ` Jani Nikula
2023-10-13 9:54 ` Lisovskiy, Stanislav
2023-10-17 9:49 ` kernel test robot
2023-10-09 13:30 Stanislav Lisovskiy
2023-10-11 8:49 ` Jani Nikula
2023-10-11 8:59 ` Lisovskiy, Stanislav
2023-10-06 14:15 Stanislav Lisovskiy
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=94796951-a166-43fa-b476-a8522c8a272d@intel.com \
--to=swati2.sharma@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=stanislav.lisovskiy@intel.com \
--cc=ville.syrjala@linux.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