All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mikko Kovanen <mikko.kovanen@aavamobile.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dsi: fix VBT send packet port selection for dual link DSI
Date: Tue, 29 Nov 2022 11:56:55 +0200	[thread overview]
Message-ID: <87cz963wyg.fsf@intel.com> (raw)
In-Reply-To: <87tu2j4ehb.fsf@intel.com>

On Mon, 28 Nov 2022, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Sat, 26 Nov 2022, Mikko Kovanen <mikko.kovanen@aavamobile.com> wrote:
>> intel_dsi->ports contains bitmask of enabled ports and correspondingly
>> logic for selecting port for VBT packet sending must use port specific
>> bitmask when deciding appropriate port.
>>
>> Fixes: 08c59dde71b7 ("drm/i915/dsi: fix VBT send packet port selection for ICL+")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Mikko Kovanen <mikko.kovanen@aavamobile.com>
>
> Holy crap, that's embarrassing! Thanks!
>
> Despite the mistake, it always works for single-link DSI as well as port
> A on dual-link DSI, which probably covers most use cases. It's the
> commands targeted at port B (VLV+ DSI) or port C (ICL+ DSI) that go
> haywire.
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>

Pushed to drm-intel-next, thanks for the patch.

And promptly after pushing I realized I failed to added the link to the
issue in the commit message. Here it is for posterity:

Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/7601


BR,
Jani.

>
>> ---
>>  drivers/gpu/drm/i915/display/intel_dsi_vbt.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dsi_vbt.c b/drivers/gpu/drm/i915/display/intel_dsi_vbt.c
>> index 75e8cc4337c9..fce69fa446d5 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dsi_vbt.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dsi_vbt.c
>> @@ -137,9 +137,9 @@ static enum port intel_dsi_seq_port_to_port(struct intel_dsi *intel_dsi,
>>  		return ffs(intel_dsi->ports) - 1;
>>  
>>  	if (seq_port) {
>> -		if (intel_dsi->ports & PORT_B)
>> +		if (intel_dsi->ports & BIT(PORT_B))
>>  			return PORT_B;
>> -		else if (intel_dsi->ports & PORT_C)
>> +		else if (intel_dsi->ports & BIT(PORT_C))
>>  			return PORT_C;
>>  	}

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-11-29  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26 13:27 [Intel-gfx] [PATCH] drm/i915/dsi: fix VBT send packet port selection for dual link DSI Mikko Kovanen
2022-11-26 14:03 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for " Patchwork
2022-11-26 14:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-28  9:26 ` [Intel-gfx] [PATCH] " Jani Nikula
2022-11-29  9:56   ` Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-26 13:00 Mikko Kovanen

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=87cz963wyg.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mikko.kovanen@aavamobile.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.