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 8B5F0349AEA for ; Fri, 30 Jan 2026 09:27:47 +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=1769765269; cv=none; b=Md8m8nRpDCg50sH704RvxPjXOO3uJ4/TBRlfJDNs9rGrviloXyDus2pzauPbCiAaFWunKkOxjWVcLOibdxqzg4ZFpKSKwPdmlFlq5KQT7eHHXH6slGITmDu4kBidHec8WQl2YcmU1UCnUTLzQRtPt965q8XUI+vY6yY4am/53Eo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769765269; c=relaxed/simple; bh=IYGbfrb8n+5tWYChZzI8D/HCj0Gp8MMZY5CEURO9AVs=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=BalZwtqluk/i5fC+I+dzRmV4KTNNGyYy8du0uE4frDWSZbVFh9lMJH69yW4TFV2icoQnmccYb+KQQAP8ibb5nD9DxtMEDYyOLirVxmBs7My4asJ+84TMU6jJXceYraCZzl/XBoRPBL8jxqpCrxxHsw2gjO5LN8jrfF6DwYzJmMQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com; spf=pass smtp.mailfrom=oss.qualcomm.com; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b=jCeknWNn; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b=RsJWxYse; arc=none smtp.client-ip=205.220.168.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b="jCeknWNn"; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b="RsJWxYse" Received: from pps.filterd (m0279864.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 60U3Vg4v2992837 for ; Fri, 30 Jan 2026 09:27:46 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qualcomm.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=qcppdkim1; bh= W9DbecvbaDPpU15XT2fpR7qkQ1PD84sWD/u1G4T75MU=; b=jCeknWNnP23wnV99 mOtvkeptG8zkHXSl0fdgrS7nlGTq2SPCCk75OY+ZnarDq7j8xIEZuSO517XVHvaH XwihnkzA4W38pVzTaJNVlcRlPIYG/ZCfp6pN5B6R2toypQVnTyrjqwfsfln5rdl2 W4zBoDk2XTTya1JqPhIql7odCJiS5HNgUe/hQLqX/W2vtOp2ArpqXblxqmScaWE5 WIUlBpZNg58gvVB6cT+pXzxygKDFNbHBi+h4HpFdfqAb1TQualRMrAeGWrPNcp/m Syy7YQIAjqwhBZLy6PtHRrZWK/eUp9XpPG1WqkB+hurfOvR+6eMi5Augay1ibaWG mcACOA== Received: from mail-qk1-f198.google.com (mail-qk1-f198.google.com [209.85.222.198]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 4c0db1j89j-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Fri, 30 Jan 2026 09:27:46 +0000 (GMT) Received: by mail-qk1-f198.google.com with SMTP id af79cd13be357-8c6de73fab8so14994285a.3 for ; Fri, 30 Jan 2026 01:27:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oss.qualcomm.com; s=google; t=1769765266; x=1770370066; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=W9DbecvbaDPpU15XT2fpR7qkQ1PD84sWD/u1G4T75MU=; b=RsJWxYsenDWUEKDtqVwMN46tLA8n6x2M4redSlPt7gmTFHYLOCfdUgfmndmxT5poa2 cMiQdTUpzwiYnnvrrJ8cDo0qMrBroiAjw1R9+yrWko4OIxERGeJ7yjV8vOI2ImwFj/pU TMjeoKxAgL8sqx4cIyIBZxjlBJDu3mu+4AbcX3bh76g3VDnyKHiMujRUoR3ZAddoOBNX 1i+DNrhDmWLd+SSpDOAALCdA7UTLIS6OvF9ofsmknIwWgOp88Ar6ALJHnX2bWiCggOM3 xBwVwbk+ji/8EdbtY1k0NinNMXoLvlbQEmqdpmoIgc63YOygN/hgbmQWu7bodVMjyMER 0nHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1769765266; x=1770370066; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=W9DbecvbaDPpU15XT2fpR7qkQ1PD84sWD/u1G4T75MU=; b=N1nlDEGiDQ95amUOB2Rjcpcx16b3KLw68NYaeuVi1poQ0YlggiqK2SVUtCAUv6jQMA B1Yh8dwgzqYsIWpDuA5DDE0pzavZlOKTOH72A++Zdp1UqClVRjKEMlt1cjIcUMKTjwhV 3V4KdNvYkcQfBicCeKJjgLeZciJilx4ZbusXMhVQH87MNLMaxwVULxPAQui2X9fyJHnY tet8HXN1bpLBYgG3Otl7yfP1aWCF37ZjvlPPOJtrnZgdIl11a+F8uQPkVbYqRsJcOB41 sHKj8+SKGLtDYgC7Lk1ahmQ+2uM3/Xkdv+vxEdy8yYdQ0SQU0ltwAo68h+epQ79ao1Bv z6eA== X-Forwarded-Encrypted: i=1; AJvYcCXhMaBs7MCvF0hngmkfCrmf7xp5n01AEjMcLwsOuWGHQUeOUogKXi7OZVbDNJkBo27LZtkpX3KD6aMieLw=@vger.kernel.org X-Gm-Message-State: AOJu0YzSZmOojGapze68DoHebE3oR/S8EUKgTxrzwM74S5a0bdV3XVMQ cZU72iM4ZRN2p6rhNXcxrxESzULaA7NWgePSeHCHz7/tLsSQpLma2q3G9HiyuDedp8OqK/hsRo1 eBXnP12EIkglS3Xtv8+v2Jlbe/0Jlgl72KbVjOEAaFb28prYSB0Y4tE/k6XhHJaEgo+E= X-Gm-Gg: AZuq6aLfwva2NKdRmHNkoAFxHcRimTof9T8C8O6SrIkT7UgsgCHMTvbIxrS8Lsi+R/E ULcukF0a4np8VSPFypQ17n6M+xxffNck5N7fRWQZhe+qkiInfwcTtBmLhJ0XJU1xO+NYAruyuNR y1PgToOYtL0ub81w9mjVmXE2Xjam4cJ9UgxaQN4k0VbHMKHoVHVKP5kH6K8LEUfzysiASDfrL1I +TubE7siFKNA+KksbeB7DmAy4DKRSC44tBkEC+DmdLId/AvsfN327nK4pMxbUoTwV2c/Upa4Vsy b0bqbZGokqkJob78td49Zw7fV6i/GwNmDcunSRXQviiYegVYtGsWv5HsguFDl1gwzOHrCLrRR6c olnuiRA4F/97IT6O7OgrwlomGe7IiEKRfBbfAABK0POktpddPxGdfnLKJzvA8O3xYfH0= X-Received: by 2002:a05:620a:17a8:b0:8c6:a707:dae7 with SMTP id af79cd13be357-8c9eb265cedmr254399385a.1.1769765265494; Fri, 30 Jan 2026 01:27:45 -0800 (PST) X-Received: by 2002:a05:620a:17a8:b0:8c6:a707:dae7 with SMTP id af79cd13be357-8c9eb265cedmr254397085a.1.1769765264934; Fri, 30 Jan 2026 01:27:44 -0800 (PST) Received: from [192.168.119.254] (078088045245.garwolin.vectranet.pl. [78.88.45.245]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-b8dbeffed15sm387518166b.31.2026.01.30.01.27.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 30 Jan 2026 01:27:44 -0800 (PST) Message-ID: <29353296-8e36-4e47-b32e-c45bd251a979@oss.qualcomm.com> Date: Fri, 30 Jan 2026 10:27:41 +0100 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 v6 0/4] arm64: dts: qcom: Introduce Glymur SoC dtsi and Glymur CRD dts To: Manivannan Sadhasivam Cc: Qiang Yu , Bjorn Andersson , Pankaj Patil , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Conor Dooley , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Krzysztof Kozlowski , Jyothi Kumar Seerapu , Maulik Shah , Sibi Sankar , Taniya Das , Kamal Wadhwa , Manaf Meethalavalappu Pallikunhi , Jishnu Prakash , Dmitry Baryshkov , Abel Vesa References: <20260122-upstream_v3_glymur_introduction-v6-0-245f408ed82a@oss.qualcomm.com> <75lzykd37zdvrks5i2bb4zb2yzjtm25kv3hegmikndkbr772mz@w2ykff3ny45u> <6d2b92d0-55bb-4ce0-ad5e-316210a3d2c5@oss.qualcomm.com> Content-Language: en-US From: Konrad Dybcio In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Proofpoint-ORIG-GUID: AdxjS8gP31u07nTpc90AsiWGS5ULCn6d X-Proofpoint-GUID: AdxjS8gP31u07nTpc90AsiWGS5ULCn6d X-Authority-Analysis: v=2.4 cv=VMTQXtPX c=1 sm=1 tr=0 ts=697c7992 cx=c_pps a=qKBjSQ1v91RyAK45QCPf5w==:117 a=FpWmc02/iXfjRdCD7H54yg==:17 a=IkcTkHD0fZMA:10 a=vUbySO9Y5rIA:10 a=s4-Qcg_JpJYA:10 a=VkNPw1HP01LnGYTKEx00:22 a=EUspDBNiAAAA:8 a=VwQbUJbxAAAA:8 a=qC_FGOx9AAAA:8 a=gEfo2CItAAAA:8 a=qoQE0mn3quF3izRY1IMA:9 a=QEXdDO2ut3YA:10 a=NFOGd7dJGGMPyQGDc5-O:22 a=fsdK_YakeE02zTmptMdW:22 a=sptkURWiP4Gy88Gu7hUp:22 X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwMTMwMDA3NSBTYWx0ZWRfX14dGXVuL8iXA eGFghrSMzLzK49Xpn+eiuHoETywW3O3ovsPcs8Rt1JY4fFskGEHuwOqBzGtwrDnnTcjgQpcim2F bVkGklnbIOmsXG3lgzYazoTuf7AZ6KZJpaogSEBVhB23kDZvmw98PFMp4YJLy5NDf/RC7CpYxOF 4RmNlZIFrodaM7yuoD7obpZmiWh1c87739r1vV3P/JI9ZazrMjjlIFOVoYTxOX4ZLV3kl/LoqXA lsRlN0Zp8e+QQHbGxtOgk/z3z5mWv2OfvLRHT5Zt1He3s3SXabliWI8oiT1auKSw/2rTz4UD3up 5s7rdY8GC1AqcAbOZYBxzkOAiPcIXxr4baIn7IL3xZhUyIIz8T+Ra7Ci9LX8z18xeN/1mqhwNdX 3w/EVR0gvLQdWpFXNNxuMLw8yF7NicX8E2ONByk3cyxOY2VPHryzVnM8lUrq0m09yFIkC9Ed/oQ uJrsW1KPSoZaQxbJKyA== X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.51,FMLib:17.12.100.49 definitions=2026-01-29_03,2026-01-29_01,2025-10-01_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 clxscore=1015 priorityscore=1501 bulkscore=0 lowpriorityscore=0 impostorscore=0 adultscore=0 phishscore=0 suspectscore=0 spamscore=0 malwarescore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2601150000 definitions=main-2601300075 On 1/29/26 5:32 PM, Manivannan Sadhasivam wrote: > On Thu, Jan 29, 2026 at 01:07:08PM +0100, Konrad Dybcio wrote: >> On 1/29/26 1:05 PM, Qiang Yu wrote: >>> On Wed, Jan 28, 2026 at 07:21:04PM -0600, Bjorn Andersson wrote: >>>> On Thu, Jan 22, 2026 at 08:53:57PM +0530, Pankaj Patil wrote: >>>>> Introduce dt-bindings and initial device tree support for Glymur, >>>>> Qualcomm's next-generation compute SoC and it's associated >>>>> Compute Reference Device (CRD) platform. >>>>> >>>>> https://www.qualcomm.com/products/mobile/snapdragon/laptops-and-tablets/snapdragon-x2-elite >>>>> https://www.qualcomm.com/news/releases/2025/09/new-snapdragon-x2-elite-extreme-and-snapdragon-x2-elite-are-the- >>>>> >>>>> The base support enables booting to shell with rootfs on NVMe, >>>>> demonstrating functionality for PCIe and NVMe subsystems. >>>>> DCVS is also enabled, allowing dynamic frequency scaling for the CPUs. >>>>> TSENS (Thermal Sensors) enabled for monitoring SoC temperature and >>>>> thermal management. The platform is capable of booting kernel at EL2 >>>>> with kvm-unit tests performed on it for sanity. >>>>> >>>>> Added dtsi files for the PMIC's enabled PMH0101, PMK8850, PMCX0102, >>>>> SMB2370, PMH0104, PMH0110 along with temp-alarm and GPIO nodeS. >>>>> >>>>> For CPU compatible naming, there is one discussion which is not specific >>>>> to Glymur, Kaanapali and Glymur use the same Oryon cores. >>>>> https://lore.kernel.org/all/20251119-oryon-binding-v1-1-f79a101b0391@oss.qualcomm.com/ >>>>> We've kept the "qcom,oryon" compatible >>>>> >>>>> Features enabled in this patchset: >>>>> 1. NVMe storage support >>>>> 2. PCIe controller and PCIe PHY >>>>> 3. RPMH Regulators >>>>> 4. Clocks and reset controllers - GCC, TCSRCC, DISPCC, RPMHCC >>>>> 5. Interrupt controller >>>>> 6. TLMM (Top-Level Mode Multiplexer) >>>>> 7. QUP Block >>>>> 8. Reserved memory regions >>>>> 9. PMIC support with regulators >>>>> 10. CPU Power Domains >>>>> 11. TSENS (Thermal Sensors) >>>>> 12. DCVS: CPU DCVS with scmi perf protocol >>>>> >>>>> Dependencies: >>>>> >>>>> dt-bindings: >>>>> 1. https://lore.kernel.org/all/20260121-glymur-pmic-mfd-v1-1-2aab4f21e79c@oss.qualcomm.com/ >>>>> 2. https://lore.kernel.org/all/20251215-knp-pmic-leds-v3-2-5e583f68b0e5@oss.qualcomm.com/ >>>>> 3. https://lore.kernel.org/all/20260121110828.2267061-1-pankaj.patil@oss.qualcomm.com/ >>>>> 4. https://lore.kernel.org/all/20260111155234.5829-1-pankaj.patil@oss.qualcomm.com/ >>>>> >>>>> Linux-next based tree with Glymur patches is available at: >>>>> https://git.codelinaro.org/clo/linux-kernel/kernel-qcom/-/tree/b4/v6_glymur_introduction >>>>> >>>> >>>> FWIW, I applied these patches onto next-20260128 to see if things has >>>> improved since Rob's report and I get: >>>> >>>> $ make qcom/glymur-crd.dtb CHECK_DTBS=1 >>>> DTC [C] arch/arm64/boot/dts/qcom/glymur-crd.dtb >>>> qcom/glymur-crd.dtb: dma-controller@800000 (qcom,glymur-gpi-dma): interrupts: [[0, 588, 4], [0, 589, 4], [0, 590, 4], [0, 591, 4], [0, 592, 4], [0, 593, 4], [0, 594, 4], [0, 595, 4], [0, 596, 4], [0, 597, 4], [0, 598, 4], [0, 599, 4], [2, 129, 4], [2, 130, 4], [2, 131, 4], [2, 132, 4]] is too long >>>> from schema $id: http://devicetree.org/schemas/dma/qcom,gpi.yaml# >>>> qcom/glymur-crd.dtb: dma-controller@a00000 (qcom,glymur-gpi-dma): interrupts: [[0, 279, 4], [0, 280, 4], [0, 281, 4], [0, 282, 4], [0, 283, 4], [0, 284, 4], [0, 293, 4], [0, 294, 4], [0, 295, 4], [0, 296, 4], [0, 297, 4], [0, 298, 4], [2, 124, 4], [2, 125, 4], [2, 126, 4], [2, 127, 4]] is too long >>>> from schema $id: http://devicetree.org/schemas/dma/qcom,gpi.yaml# >>>> qcom/glymur-crd.dtb: dma-controller@b00000 (qcom,glymur-gpi-dma): interrupts: [[2, 76, 4], [2, 77, 4], [2, 78, 4], [2, 79, 4], [2, 80, 4], [2, 81, 4], [2, 82, 4], [2, 83, 4], [2, 84, 4], [2, 85, 4], [2, 86, 4], [2, 87, 4], [2, 88, 4], [2, 89, 4], [2, 90, 4], [2, 91, 4]] is too long >>>> from schema $id: http://devicetree.org/schemas/dma/qcom,gpi.yaml# >>>> qcom/glymur-crd.dtb: pmic@1 (qcom,pmh0101): led-controller@ee00:compatible:0: 'qcom,pmh0101-flash-led' is not one of ['qcom,pm6150l-flash-led', 'qcom,pm660l-flash-led', 'qcom,pm7550-flash-led', 'qcom,pm8150c-flash-led', 'qcom,pm8150l-flash-led', 'qcom,pm8350c-flash-led', 'qcom,pm8550-flash-led', 'qcom,pmi8998-flash-led'] >>>> from schema $id: http://devicetree.org/schemas/mfd/qcom,spmi-pmic.yaml# >>>> qcom/glymur-crd.dtb: pmic@1 (qcom,pmh0101): pwm:compatible: 'oneOf' conditional failed, one must be fixed: >>>> ['qcom,pmh0101-pwm', 'qcom,pm8350c-pwm'] is too long >>>> 'qcom,pmh0101-pwm' is not one of ['qcom,pm660l-lpg', 'qcom,pm8150b-lpg', 'qcom,pm8150l-lpg', 'qcom,pm8350c-pwm', 'qcom,pm8916-pwm', 'qcom,pm8941-lpg', 'qcom,pm8994-lpg', 'qcom,pmc8180c-lpg', 'qcom,pmi632-lpg', 'qcom,pmi8950-pwm', 'qcom,pmi8994-lpg', 'qcom,pmi8998-lpg', 'qcom,pmk8550-pwm'] >>>> 'qcom,pmh0101-pwm' is not one of ['qcom,pm6150l-lpg'] >>>> 'qcom,pmh0101-pwm' is not one of ['qcom,pm8550-pwm'] >>>> 'qcom,pmh0101-pwm' is not one of ['qcom,pm8937-pwm'] >>>> 'qcom,pm8150l-lpg' was expected >>>> 'qcom,pm8916-pwm' was expected >>>> from schema $id: http://devicetree.org/schemas/mfd/qcom,spmi-pmic.yaml# >>>> qcom/glymur-crd.dtb: led-controller@ee00 (qcom,pmh0101-flash-led): compatible:0: 'qcom,pmh0101-flash-led' is not one of ['qcom,pm6150l-flash-led', 'qcom,pm660l-flash-led', 'qcom,pm7550-flash-led', 'qcom,pm8150c-flash-led', 'qcom,pm8150l-flash-led', 'qcom,pm8350c-flash-led', 'qcom,pm8550-flash-led', 'qcom,pmi8998-flash-led'] >>>> from schema $id: http://devicetree.org/schemas/leds/qcom,spmi-flash-led.yaml# >>>> qcom/glymur-crd.dtb: /soc@0/arbiter@c400000/spmi@c426000/pmic@1/led-controller@ee00: failed to match any schema with compatible: ['qcom,pmh0101-flash-led', 'qcom,spmi-flash-led'] >>>> qcom/glymur-crd.dtb: pwm (qcom,pmh0101-pwm): compatible: 'oneOf' conditional failed, one must be fixed: >>>> ['qcom,pmh0101-pwm', 'qcom,pm8350c-pwm'] is too long >>>> 'qcom,pmh0101-pwm' is not one of ['qcom,pm660l-lpg', 'qcom,pm8150b-lpg', 'qcom,pm8150l-lpg', 'qcom,pm8350c-pwm', 'qcom,pm8916-pwm', 'qcom,pm8941-lpg', 'qcom,pm8994-lpg', 'qcom,pmc8180c-lpg', 'qcom,pmi632-lpg', 'qcom,pmi8950-pwm', 'qcom,pmi8994-lpg', 'qcom,pmi8998-lpg', 'qcom,pmk8550-pwm'] >>>> 'qcom,pmh0101-pwm' is not one of ['qcom,pm6150l-lpg'] >>>> 'qcom,pmh0101-pwm' is not one of ['qcom,pm8550-pwm'] >>>> 'qcom,pmh0101-pwm' is not one of ['qcom,pm8937-pwm'] >>>> 'qcom,pm8150l-lpg' was expected >>>> 'qcom,pm8916-pwm' was expected >>>> from schema $id: http://devicetree.org/schemas/leds/leds-qcom-lpg.yaml# >>>> qcom/glymur-crd.dtb: /soc@0/arbiter@c400000/spmi@c426000/pmic@1/pwm: failed to match any schema with compatible: ['qcom,pmh0101-pwm', 'qcom,pm8350c-pwm'] >>>> >>>> So, we're still missing a few dependencies. >>>> >>>> >>>> Booting the system I get a ton of errors from PCIe in the kernel log: >>>> >>>> debugfs: 'opp:5000000' already exists in 'soc@0-1c00000.pci' >>>> >>>> # dmesg | grep -E 'debugfs: .+ already exists' |wc -l >>>> 508 >>>> >>>> The system does eventually boot, and I was happy to see that we do end >>>> up finding the PCIe devices after all. >>>> >>> I enabled dynamic debug logs and observed that each PCIe platform device >>> probe was deferred approximately 10 times. The probe deferrals resulted in >>> additional OPP debugfs warnings being printed. >>> >>> The PCIe platform device probe was deferred because the PHY driver was not >>> ready - either because the PHY driver was not yet loaded, or because the >>> PHY driver's own probe was also deferred due to its dependency (e.g., >>> 1fd5000.clock-controller) not being ready. This is normal behavior, >>> correct? I also observed that other driver probes were deferred. >>> >>> But I'm not sure why there are more than 300 times probe deferrals on >>> your setup. >> >> I think Bjorn is trying to say that the driver is wrong, because it >> effectively seems to call devm_pm_opp_of_add_table repeatedly >> > > We did try to avoid that by guarding it with dev_pm_opp_get_opp_count(). But > that doesn't seem to be helping. The error might be due to duplicate non-shared > opp entries, but I'm yet to confirm. What if you just move the devm_pm_opp_of_add_table() to after the calls that can return -EPROBE_DEFER? Konrad