From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.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 DCD4816BE3A; Mon, 10 Feb 2025 11:09:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.168.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1739185763; cv=none; b=mOYhjnujuu5J7to5uI1rMHIiKf6uLIB/QJVDM6AqONmNocUqTn7XVLMvCv3PawiJ+RY2d6wIbYmPDxXBIDgBCbc0T+um26hkrNweSKeZVdgVhp0jdwKy/BOC2LBvoP16uBlWlrLvWDWVWj4dSxRSWNcXMzwzRRH5s/AnTHCurjU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1739185763; c=relaxed/simple; bh=fiAmj02tnY4RlOfIc3fnucfwbpXcpZX1q76PPA5gZTA=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=YHMqbl/A8p/oKaduqSHfV+Ro60BVNWjINF8tdDDgnxufLlvwaNgr51C39tYBEOJpom1GKvkHP7jf4gTHMYfWwxmoZjJxlCvSKD3HXP9tHZmd/H44SiWVp5/tPdAXxO9dhom5ElCmcPe0W9rxyMPThpS01evUhqnuJzflq25JwoI= 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=LbTsaX1E; arc=none smtp.client-ip=205.220.168.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="LbTsaX1E" Received: from pps.filterd (m0279862.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 51AA7axe003521; Mon, 10 Feb 2025 11:09:10 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= ggBUKbTWnZ2Htvo1oilHaJI1DyEA5fb4ePZIIAtLG2w=; b=LbTsaX1Ejs6VpnLq UM1hJK8+3iuKDJKQeKh6AItSyWUKG8CwybY0ku2Y+Jo+WNJJMKBzmLe7CEoDCBCa 5RIDoC+Au7JFq344Qbesl3jBxZ8ZnGxk1dmoXR+V1uywbEo68Ps8zBzgWOCJbtlQ Z+4ny81sMgg4v8ur5BvD3U249BUBaoOQmk9qru80jXTgayEjn0N+w0ejKT5JQuo8 pAbzlPHPFE/96xLcN2ecfm5isxofO8PvuqeZdOdlkhHPgIB8/DiJUd9E7pUGrMGR w+uzeS5BKLAWGQMn/LQ7tRKPf0Xe1FrRPGW+JJ9swDJhUf130/xOF/j11MGeX58S Y/s+pg== Received: from nalasppmta04.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 44p0dym2ne-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 10 Feb 2025 11:09:09 +0000 (GMT) Received: from nalasex01a.na.qualcomm.com (nalasex01a.na.qualcomm.com [10.47.209.196]) by NALASPPMTA04.qualcomm.com (8.18.1.2/8.18.1.2) with ESMTPS id 51AB98Gt022894 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 10 Feb 2025 11:09:08 GMT Received: from [10.218.7.247] (10.80.80.8) by nalasex01a.na.qualcomm.com (10.47.209.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.9; Mon, 10 Feb 2025 03:09:00 -0800 Message-ID: Date: Mon, 10 Feb 2025 16:38:56 +0530 Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 0/5] Add UFS support for SM8750 To: Manivannan Sadhasivam , , CC: Konrad Dybcio , Melody Olvera , Vinod Koul , "Kishon Vijay Abraham I" , Rob Herring , "Krzysztof Kozlowski" , Conor Dooley , "Alim Akhtar" , Avri Altman , "Bart Van Assche" , Bjorn Andersson , "Andy Gross" , Konrad Dybcio , "Satya Durga Srinivasu Prabhala" , Trilok Soni , , , , , , Manish Pandey References: <20250113-sm8750_ufs_master-v1-0-b3774120eb8c@quicinc.com> <20250209152140.cyry6g7ltccxcmyj@thinkpad> <20250210101338.boziqlrxl2cei775@thinkpad> Content-Language: en-US From: Nitin Rawat In-Reply-To: <20250210101338.boziqlrxl2cei775@thinkpad> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nalasex01a.na.qualcomm.com (10.47.209.196) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-ORIG-GUID: tf5xNFri-tkr3gQKi4kRaPgBcrEAm_IK X-Proofpoint-GUID: tf5xNFri-tkr3gQKi4kRaPgBcrEAm_IK 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-10_05,2025-02-10_01,2024-11-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 suspectscore=0 bulkscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 mlxlogscore=999 mlxscore=0 priorityscore=1501 spamscore=0 adultscore=0 phishscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2501170000 definitions=main-2502100093 On 2/10/2025 3:43 PM, Manivannan Sadhasivam wrote: > + Can (for the MCQ query) > > On Mon, Feb 10, 2025 at 10:39:04AM +0100, neil.armstrong@linaro.org wrote: >> On 09/02/2025 16:21, Manivannan Sadhasivam wrote: >>> On Fri, Feb 07, 2025 at 11:47:12PM +0100, Konrad Dybcio wrote: >>>> On 13.01.2025 10:46 PM, Melody Olvera wrote: >>>>> Add UFS support for SM8750 SoCs. >>>>> >>>>> Signed-off-by: Melody Olvera >>>>> --- >>>>> Nitin Rawat (5): >>>>> dt-bindings: phy: qcom,sc8280xp-qmp-ufs-phy: Document the SM8750 QMP UFS PHY >>>>> phy: qcom-qmp-ufs: Add PHY Configuration support for SM8750 >>>>> dt-bindings: ufs: qcom: Document the SM8750 UFS Controller >>>>> arm64: dts: qcom: sm8750: Add UFS nodes for SM8750 SoC >>>>> arm64: dts: qcom: sm8750: Add UFS nodes for SM8750 QRD and MTP boards >>>> >>>> You still need the same workaround 8550/8650 have in the UFS driver >>>> (UFSHCD_QUIRK_BROKEN_LSDBS_CAP) for it to work reliably, or at least >>>> that was the case for me on a 8750 QRD. >>>> >>>> Please check whether we can make that quirk apply based on ctrl >>>> version or so, so that we don't have to keep growing the compatible >>>> list in the driver. >>>> >>> >>> That would be a bizarre. When I added the quirk, I was told that it would affect >>> only SM8550 and SM8650 (this one I learned later). I'm not against applying the >>> quirk based on UFSHC version if the bug is carried forward, but that would be an >>> indication of bad design. >> >> Isn't 8750 capable of using MCQ now ? because this is the whole issue behind >> this UFSHCD_QUIRK_BROKEN_LSDBS_CAP, it's supposed to use MCQ by default... but >> we don't. >> >> Is there any news about that ? It's a clear regression against downstream, not >> having MCQ makes the UFS driver struggle to reach high bandwidth when the system >> is busy because we can't spread the load over all CPUs and we have only single >> queue to submit requests. >> > > There are hardware issues on SM8550 and SM8650(?) for the MCQ feature. > Apparently, Qcom carries the workaround in downstream, but I got tired of > pushing them to upstream the fix(es). > > Maybe Can Guo can share what is the latest update on this. > > - Mani > Hi Mani, I have already replied to konrad mail earlier in this thread. The LSDBS workaround is only applicable for SM8650 and SM8550. SM8750 and onwards doesn't need this WA anymore as it is fixed in HW. Regards, Nitin