From: Jani Nikula <jani.nikula@intel.com>
To: "Sharma, Swati2" <swati2.sharma@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Stanislav Lisovskiy" <stanislav.lisovskiy@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Add bigjoiner force enable option to debugfs
Date: Wed, 17 Jan 2024 20:01:40 +0200 [thread overview]
Message-ID: <87y1cnq1ob.fsf@intel.com> (raw)
In-Reply-To: <94796951-a166-43fa-b476-a8522c8a272d@intel.com>
On Wed, 17 Jan 2024, "Sharma, Swati2" <swati2.sharma@intel.com> wrote:
> 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:
>>> 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?
Yeah. But this gets called for every single display mode via
intel_dp_mode_valid().
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-01-17 18:01 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
2024-01-17 18:01 ` Jani Nikula [this message]
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=87y1cnq1ob.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stanislav.lisovskiy@intel.com \
--cc=swati2.sharma@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