From: Hans de Goede <hdegoede@redhat.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [PATCH 2/2] drm/i915/dsi: Use a fuzzy check for burst mode clock check
Date: Wed, 5 Jun 2019 18:28:43 +0200 [thread overview]
Message-ID: <5961343b-f5ed-d55c-689d-0ebc2ee9c661@redhat.com> (raw)
In-Reply-To: <20190604172936.GH5942@intel.com>
Hi,
Thank you for the reviews.
On 04-06-19 19:29, Ville Syrjälä wrote:
> On Fri, May 24, 2019 at 07:40:28PM +0200, Hans de Goede wrote:
>> Prior to this commit we fail to init the DSI panel on the GPD MicroPC:
>> https://www.indiegogo.com/projects/gpd-micropc-6-inch-handheld-industry-laptop#/
>>
>> The problem is intel_dsi_vbt_init() failing with the following error:
>> *ERROR* Burst mode freq is less than computed
>>
>> The pclk in the VBT panel modeline is 70000, together with 24 bpp and
>> 4 lines this results in a bitrate value of 70000 * 24 / 4 = 420000.
>> But the target_burst_mode_freq in the VBT is 418000.
>>
>> This commit works around this problem by adding an intel_fuzzy_clock_check
>> when target_burst_mode_freq < bitrate and setting target_burst_mode_freq to
>> bitrate when that checks succeeds, fixing the panel not working.
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>> drivers/gpu/drm/i915/intel_dsi_vbt.c | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_dsi_vbt.c b/drivers/gpu/drm/i915/intel_dsi_vbt.c
>> index 022bf59418df..a2a9b9d0eeaa 100644
>> --- a/drivers/gpu/drm/i915/intel_dsi_vbt.c
>> +++ b/drivers/gpu/drm/i915/intel_dsi_vbt.c
>> @@ -895,6 +895,17 @@ bool intel_dsi_vbt_init(struct intel_dsi *intel_dsi, u16 panel_id)
>> if (mipi_config->target_burst_mode_freq) {
>> u32 bitrate = intel_dsi_bitrate(intel_dsi);
>>
>> + /*
>> + * Sometimes the VBT contains a slightly lower clock,
>> + * then the bitrate we have calculated, in this case
>> + * just replace it with the calculated bitrate.
>> + */
>> + if (mipi_config->target_burst_mode_freq < bitrate &&
>> + intel_fuzzy_clock_check(
>> + mipi_config->target_burst_mode_freq,
>> + bitrate))
>> + mipi_config->target_burst_mode_freq = bitrate;
>
> Maybe should squash these patches together to make the stable
> backport less painful?
Good idea, done.
> Anyways, seems OK to me.
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
And pushed with your Reviewed-by.
Regards,
Hans
next prev parent reply other threads:[~2019-06-05 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 17:40 [PATCH 1/2] drm/i915: Make intel_fuzzy_clock_check available outside of intel_display.c Hans de Goede
2019-05-24 17:40 ` [PATCH 2/2] drm/i915/dsi: Use a fuzzy check for burst mode clock check Hans de Goede
2019-06-04 17:29 ` Ville Syrjälä
2019-06-05 16:28 ` Hans de Goede [this message]
2019-05-26 14:07 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915: Make intel_fuzzy_clock_check available outside of intel_display.c Patchwork
2019-05-26 14:27 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-27 8:24 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-05-27 10:52 ` ✓ Fi.CI.IGT: success " 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=5961343b-f5ed-d55c-689d-0ebc2ee9c661@redhat.com \
--to=hdegoede@redhat.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.org \
--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