Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Rob Clark <robin.clark@oss.qualcomm.com>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Abhinav Kumar <abhinav.kumar@linux.dev>,
	Jessica Zhang <jesszhan0024@gmail.com>,
	Sean Paul <sean@poorly.run>,
	Marijn Suijten <marijn.suijten@somainline.org>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Luca Weiss <luca.weiss@fairphone.com>,
	Alexander Koskovich <AKoskovich@pm.me>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Yongxing Mou <yongxing.mou@oss.qualcomm.com>
Subject: Re: [PATCH] drm/msm/dpu: correct DP MST interface configuration
Date: Wed, 25 Mar 2026 11:00:49 +0100	[thread overview]
Message-ID: <101aae08-efde-4d9d-8af2-613d4cc9698a@oss.qualcomm.com> (raw)
In-Reply-To: <3f33e61e-d244-4600-9ffe-218371c04541@oss.qualcomm.com>

On 3/25/26 10:57 AM, Konrad Dybcio wrote:
> On 3/25/26 6:32 AM, Dmitry Baryshkov wrote:
>> Due to historical reasons we ended up with dummy values being specified
>> for MST-related interfaces some of them had INTF_NONE, others had
>> non-existing DP controller indices. Those workarounds are no longer
>> necessary. Fix types and indices for all DP-MST related INTF instances.
>>
>> The only exception is INTF_3 on SC8180X, which has unique design. It can
>> be used either with INTF_0 / DP0 or with INTF_4 / DP1. This interface is
>> left with the dummy value until somebody implements necessary bits for
>> that platform.
>>
>> Co-developed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
>> Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
>> Signed-off-by: Yongxing Mou <yongxing.mou@oss.qualcomm.com>
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>> ---
> 
>>  		.name = "intf_8", .id = INTF_8,
>>  		.base = 0x3c000, .len = 0x280,
>> -		.type = INTF_NONE,
>> -		.controller_id = MSM_DP_CONTROLLER_1,
>> +		.type = INTF_DP,
>> +		.controller_id = MSM_DP_CONTROLLER_1,	/* pair with intf_8 for DP MST */
> 
> with intf_4

Otherwise this is all correct

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Luca/Alexander, Milos will also have INTF0+INTF_3 paired

Konrad

  reply	other threads:[~2026-03-25 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25  5:32 [PATCH] drm/msm/dpu: correct DP MST interface configuration Dmitry Baryshkov
2026-03-25  9:57 ` Konrad Dybcio
2026-03-25 10:00   ` Konrad Dybcio [this message]
2026-04-06 23:42 ` Dmitry Baryshkov

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=101aae08-efde-4d9d-8af2-613d4cc9698a@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=AKoskovich@pm.me \
    --cc=abhinav.kumar@linux.dev \
    --cc=airlied@gmail.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jesszhan0024@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.weiss@fairphone.com \
    --cc=lumag@kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    --cc=yongxing.mou@oss.qualcomm.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