From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0b-0031df01.pphosted.com (mx0b-0031df01.pphosted.com [205.220.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3FF041D5142; Wed, 19 Feb 2025 10:02:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.180.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1739959372; cv=none; b=ViVjknu2fYwXiZaSxnm9ZsQIWK/1j79lZvHUqp8rH62D0oU7SlxJkBpx+kRcHOWw9qb8RFPKEhVj8V6e/jU53CsUN/QpYrVpHxun+mdP6qeVwAdzscftqUFSdIbKpvE0uA9sWAm1YvjwPEQ3m16E301A8Kzl4N33+mozyT1qtls= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1739959372; c=relaxed/simple; bh=65G76LUuM0MqJW76tM6yVQUOfiWz+Ax+9CrpR811tjY=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=XVG55z8AkF5s03WbpJgmHL/4u0Uinhr+juA6VtfhXEaBZAmJF8OqAjQ7Cecitn7e1+2eV1TTB6NY0akr6Ua2GMwcKGMzZ2Deg5R1QCyet+VvZ0PU9W+PaXkk3eCVtwCA0nXYmBg4UN1ntqsb4L+cxJhO1hdep/JSEdL8LmByc34= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=quicinc.com; spf=pass smtp.mailfrom=quicinc.com; dkim=pass (2048-bit key) header.d=quicinc.com header.i=@quicinc.com header.b=GAiKgacw; arc=none smtp.client-ip=205.220.180.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=quicinc.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=quicinc.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=quicinc.com header.i=@quicinc.com header.b="GAiKgacw" Received: from pps.filterd (m0279872.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 51J8JZbc011038; Wed, 19 Feb 2025 10:02:38 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=qcppdkim1; bh= abKLfrCk1L0S+ZCur53/fHQQNoqfewf63mbxjUYlbAk=; b=GAiKgacwzy9qfl4G ShXRoX4fLC4m/UbxheJG0Xv/AHc7yBRlvPdwhoahZvgzV3A4/ClQoXB1SFkeN+Xp qHwKpec4P4GYnLXTh2NhjXXc/hmuecRYRRRxQfbKH5hkWJ9WvSjf//beFbba85Gv 7d9Di3GusU6FfucrMCvHvbN7Jyh9z7uf6DMraxyY/fy/TXsjdqJ0KRoiSjMtdyzV KEug8gyv0VMGuGWVxr8qqfVFFsBdDUXZFkUzW8l0pGdymGm6CdKMZ1E3a6RXUjko Au/4rnFEGlh8Cocj/VjONvmEU3383rEX9EYCglBq2LzbxVtxcbfoMjxY74SXgR8u 8v4+gg== Received: from nalasppmta02.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 44vyy1t34g-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 19 Feb 2025 10:02:37 +0000 (GMT) Received: from nalasex01c.na.qualcomm.com (nalasex01c.na.qualcomm.com [10.47.97.35]) by NALASPPMTA02.qualcomm.com (8.18.1.2/8.18.1.2) with ESMTPS id 51JA2Z3O002290 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 19 Feb 2025 10:02:35 GMT Received: from [10.64.68.119] (10.80.80.8) by nalasex01c.na.qualcomm.com (10.47.97.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.9; Wed, 19 Feb 2025 02:02:29 -0800 Message-ID: <2ede97c5-a4f2-42fb-b3cd-68f26297150b@quicinc.com> Date: Wed, 19 Feb 2025 18:02:27 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 0/4] Add MST support for qcs8300 platform To: Krzysztof Kozlowski , Rob Clark , Abhinav Kumar , Dmitry Baryshkov , Sean Paul , Marijn Suijten , David Airlie , "Simona Vetter" , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Kuogee Hsieh , Bjorn Andersson , Konrad Dybcio CC: , , , , References: <20250212-mst_qcs8300-v1-0-38a8aa08394b@quicinc.com> <87058b73-8854-4dbd-9f27-1da2a8240c16@kernel.org> Content-Language: en-US From: Yongxing Mou In-Reply-To: <87058b73-8854-4dbd-9f27-1da2a8240c16@kernel.org> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) To nalasex01c.na.qualcomm.com (10.47.97.35) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: IwZw3lzO3wGe7zZ1Ez3qwhGQB9xAXfyz X-Proofpoint-ORIG-GUID: IwZw3lzO3wGe7zZ1Ez3qwhGQB9xAXfyz X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1057,Hydra:6.0.680,FMLib:17.12.68.34 definitions=2025-02-19_04,2025-02-18_01,2024-11-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 clxscore=1015 adultscore=0 bulkscore=0 phishscore=0 suspectscore=0 malwarescore=0 spamscore=0 priorityscore=1501 impostorscore=0 lowpriorityscore=0 mlxscore=0 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2502100000 definitions=main-2502190080 On 2025/2/12 17:06, Krzysztof Kozlowski wrote: > On 12/02/2025 08:12, Yongxing Mou wrote: >> This series of patches introduces how to enable MST functionality on >> the qcs8300 platform. The qcs8300 platform uses dpu_8_4 hardware, which >> is the same as the sa8775p, but it only has one DPU. So it only has one >> DP0 controller, supporting 4-stream MST. This patch only enables >> 2-stream MST, using intf0 and intf3. The first and second patches are >> modifications to the correspond dt-bindings, third patch is the dp >> controller driver after not reuse sm8650, fourth patch is the qcs8300 >> dts modification which add the clk support for stream 1. >> >> Signed-off-by: Yongxing Mou >> --- >> This patch depends on following series: >> https://lore.kernel.org/all/20250120-mdssdt_qcs8300-v4-0-1687e7842125@quicinc.com/ >> https://lore.kernel.org/all/20250114-dts_qcs8300-v3-0-d114cc5e4af9@quicinc.com/ >> https://lore.kernel.org/all/20241202-dp_mst_bindings-v1-0-9a9a43b0624a@quicinc.com >> https://lore.kernel.org/all/20241205-dp_mst-v1-0-f8618d42a99a@quicinc.com/ > > Buggy patch cannot be the dependency. You need to fix the original patch > instead. You are not supposed to wait till knowingly incorrect patches > get merged so you can send a fix. You must respond to that patch > stopping its merging process. > > Best regards, > Krzysztof Thanks for the reminder. I hadn't noticed that before. We will wait for our dependencies to be ready before sending the new patchset.