From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, imre.deak@intel.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12.y] drm/i915/dsi: Use TRANS_DDI_FUNC_CTL's own port width macro
Date: Tue, 25 Feb 2025 11:13:57 -0500 [thread overview]
Message-ID: <20250225092150-aa652f5ea80fe710@stable.kernel.org> (raw)
In-Reply-To: <20250224153910.1960010-1-imre.deak@intel.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Provided upstream commit SHA1 does not match found commit
ℹ️ Patch is missing in 6.13.y (ignore if backport was sent)
⚠️ Commit missing in all newer stable branches
The claimed upstream commit SHA1 (76120b3a304aec28fef4910204b81a12db8974da) was not found.
However, I found a matching commit: 879f70382ff3e92fc854589ada3453e3f5f5b601
Status in newer kernel trees:
6.13.y | Not found
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: 879f70382ff3e ! 1: 087834a498981 drm/i915/dsi: Use TRANS_DDI_FUNC_CTL's own port width macro
@@ Metadata
## Commit message ##
drm/i915/dsi: Use TRANS_DDI_FUNC_CTL's own port width macro
+ commit 76120b3a304aec28fef4910204b81a12db8974da upstream.
+
The format of the port width field in the DDI_BUF_CTL and the
TRANS_DDI_FUNC_CTL registers are different starting with MTL, where the
x3 lane mode for HDMI FRL has a different encoding in the two registers.
@@ Commit message
Link: https://patchwork.freedesktop.org/patch/msgid/20250214142001.552916-2-imre.deak@intel.com
(cherry picked from commit 76120b3a304aec28fef4910204b81a12db8974da)
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
+ (cherry picked from commit 879f70382ff3e92fc854589ada3453e3f5f5b601)
+ [Imre: Rebased on v6.12.y, due to upstream API changes in
+ intel_de_read(), TRANS_DDI_FUNC_CTL()]
+ Signed-off-by: Imre Deak <imre.deak@intel.com>
## drivers/gpu/drm/i915/display/icl_dsi.c ##
@@ drivers/gpu/drm/i915/display/icl_dsi.c: gen11_dsi_configure_transcoder(struct intel_encoder *encoder,
/* select data lane width */
- tmp = intel_de_read(display,
- TRANS_DDI_FUNC_CTL(display, dsi_trans));
+ tmp = intel_de_read(dev_priv,
+ TRANS_DDI_FUNC_CTL(dev_priv, dsi_trans));
- tmp &= ~DDI_PORT_WIDTH_MASK;
- tmp |= DDI_PORT_WIDTH(intel_dsi->lane_count);
+ tmp &= ~TRANS_DDI_PORT_WIDTH_MASK;
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
next prev parent reply other threads:[~2025-02-25 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 10:22 FAILED: patch "[PATCH] drm/i915/dsi: Use TRANS_DDI_FUNC_CTL's own port width macro" failed to apply to 6.12-stable tree gregkh
2025-02-24 15:39 ` [PATCH 6.12.y] drm/i915/dsi: Use TRANS_DDI_FUNC_CTL's own port width macro Imre Deak
2025-02-25 16:13 ` Sasha Levin [this message]
2025-03-05 12:57 ` Greg KH
2025-03-05 15:50 ` Imre Deak
2025-03-06 19:11 ` Sasha Levin
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=20250225092150-aa652f5ea80fe710@stable.kernel.org \
--to=sashal@kernel.org \
--cc=imre.deak@intel.com \
--cc=stable@vger.kernel.org \
/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.