Message ID | 20240131112342.1300893-1-s-vadapalli@ti.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel+bounces-46340-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7301:2087:b0:106:209c:c626 with SMTP id gs7csp1817925dyb; Wed, 31 Jan 2024 03:24:12 -0800 (PST) X-Google-Smtp-Source: AGHT+IEF2UoYwL8CD0wbAxLwNM+yIncz+1z4WL6MEk0/KtGbgYxDwS1rJs9csiSug8fiF69AeNsU X-Received: by 2002:a05:622a:2cc:b0:42a:67ed:21c4 with SMTP id a12-20020a05622a02cc00b0042a67ed21c4mr1299178qtx.31.1706700252154; Wed, 31 Jan 2024 03:24:12 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1706700252; cv=pass; d=google.com; s=arc-20160816; b=0/QeeeP7V2bdArxCVH9yvZfKuulIDudFrPOdT8fGRFRjJRwGAD64YpnmRMdo25EeS9 EuaOrAGf5a7Ipk1lxRkD5MSH6NUrlYitz+d9kNGvTLHq0TZ+qleQ/nIrusGXYze4MqY+ HbmAA/tGALbFQC+ncM8msuVQWjG72XpuIKRiuPrstInwngn727lsFkYauq7vBo0w00bZ uIBhJe1noWcKp7jKsNoJLPRioHGftqbYmMRVsg8G4M0r2cGfpyPSCn5xGrvaSsSnH2T9 mjtKGcxGMkqkdvT0/+KmLUT5W5GlN8vFf+dH+OzwXe6TZMDkB5cJJUsn7bx5Bu5VNhUU PbnQ== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:message-id:date:subject:cc:to :from:dkim-signature; bh=QHkI07X0GJZUyie1k7oMk2KLJoEEG+8fx6H0YqKqWqI=; fh=Fm76OJNftybUCoyzuVwJhX6i+B2deU7KabFozuQF06M=; b=QCmx8WiS4uQll1/7zCci7kb9L2mJZDRgiWNDcBfyQEhp2Sx/iHeeRuTblYTb8ZXdc6 mJ+UJPpxly1i6OigUQOlazYQGOE1fS1a+x7gR/qETMMb+yVs8eCqWrJ27mcURc+XXT0X R6SjU947lPxfO1m7cYNfiELf3bUy2VfjLkWlSqRqHmzn3I2f48d/mTquDNMbifBeZ6wd oFGn5mWikrKLCUAJynk/6B1FIzbiSvRIwVBFzqU4Tyo9bxu/fhTZum5oLx9ekA+CcYOu FNnYAhhzLawPMz8KZadht2lT1qMH9OWMWj97JHGH9UMOvxR1+mU6wVmGUOLmQR+Ve+Hl bEvQ==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=hoEfERqh; arc=pass (i=1 spf=pass spfdomain=ti.com dkim=pass dkdomain=ti.com dmarc=pass fromdomain=ti.com); spf=pass (google.com: domain of linux-kernel+bounces-46340-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-46340-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com X-Forwarded-Encrypted: i=1; AJvYcCUZ1mnqT4yWAp0r+8nskS+yoB/UAtZfwe2ecPp00BEfTMvNKsGyo/x7iRWZfmXwKLV31VO64wqnm22YJ6G40A2PUOP2MQ== Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [147.75.199.223]) by mx.google.com with ESMTPS id q14-20020a05622a030e00b0042bedcc7d40si287389qtw.269.2024.01.31.03.24.12 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 31 Jan 2024 03:24:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-46340-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=hoEfERqh; arc=pass (i=1 spf=pass spfdomain=ti.com dkim=pass dkdomain=ti.com dmarc=pass fromdomain=ti.com); spf=pass (google.com: domain of linux-kernel+bounces-46340-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-46340-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id E43B21C21B45 for <ouuuleilei@gmail.com>; Wed, 31 Jan 2024 11:24:11 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 8834876040; Wed, 31 Jan 2024 11:23:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="hoEfERqh" Received: from lelv0143.ext.ti.com (lelv0143.ext.ti.com [198.47.23.248]) (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 09DFB6D1C3; Wed, 31 Jan 2024 11:23:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.47.23.248 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706700235; cv=none; b=hOtDdQ+1OXkc7tULcHtveqZsAcTgeNWTU4HOALZVjSWnJnYmzlDTb3w4hFycpOa4segDTzpRcOOZ+w07Brs5t3JHmca81X+UJThRdUuEzN/gpY8y07y5cMyHYfEMbwgbyOxAjo6PlJ3KJVqHvxPyk0rk8wfp9DiPJx2BitqPbuQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706700235; c=relaxed/simple; bh=5P2zxSLURVbZ7HV4GWIOUHTQn5EE9g7rJ053+yGyBdI=; h=From:To:CC:Subject:Date:Message-ID:MIME-Version:Content-Type; b=CZlh5IIX/hdn1441+F/Ei7USsAX59MNRnnNwhAe+ObsmCkr4cZLeSRNwu1lHBBVadmyKkH4wa/PpqCKjPdCCrJETiqpErksFdxjyiu003sIwNvRRPpJZ4TRXr4d+PZtJ4jMdryzHUGlXsRw8LrT+yqmBe0nhrKPpGfGDLHqEGiQ= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com; spf=pass smtp.mailfrom=ti.com; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b=hoEfERqh; arc=none smtp.client-ip=198.47.23.248 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ti.com Received: from fllv0035.itg.ti.com ([10.64.41.0]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 40VBNkai084617; Wed, 31 Jan 2024 05:23:46 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1706700226; bh=QHkI07X0GJZUyie1k7oMk2KLJoEEG+8fx6H0YqKqWqI=; h=From:To:CC:Subject:Date; b=hoEfERqhykt3Lls/Zt5JVcFdMdmwA14AHjntS+IAi4BtrT0o1+iNLG+5x+yDn7zjt hI4CquO0gvbOc4LcsdI/9QY83oHsdgVlNQEjLDXZHeQiLBED5nlh/y6U19DFex6bfr mhUOvof5aaHYTJTr6cvKt0mnyW0AIMLF3AuXkyCo= Received: from DFLE115.ent.ti.com (dfle115.ent.ti.com [10.64.6.36]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 40VBNkT9075512 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 31 Jan 2024 05:23:46 -0600 Received: from DFLE106.ent.ti.com (10.64.6.27) by DFLE115.ent.ti.com (10.64.6.36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Wed, 31 Jan 2024 05:23:46 -0600 Received: from lelvsmtp5.itg.ti.com (10.180.75.250) by DFLE106.ent.ti.com (10.64.6.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Wed, 31 Jan 2024 05:23:46 -0600 Received: from uda0492258.dhcp.ti.com (uda0492258.dhcp.ti.com [172.24.227.9]) by lelvsmtp5.itg.ti.com (8.15.2/8.15.2) with ESMTP id 40VBNh0F066660; Wed, 31 Jan 2024 05:23:43 -0600 From: Siddharth Vadapalli <s-vadapalli@ti.com> To: <lee@kernel.org>, <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org> CC: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <afd@ti.com>, <srk@ti.com>, <s-vadapalli@ti.com> Subject: [PATCH] dt-bindings: mfd: syscon: Add ti,k3-pcie-ctrl compatible Date: Wed, 31 Jan 2024 16:53:42 +0530 Message-ID: <20240131112342.1300893-1-s-vadapalli@ti.com> X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1789604923472913409 X-GMAIL-MSGID: 1789604923472913409 |
Series |
dt-bindings: mfd: syscon: Add ti,k3-pcie-ctrl compatible
|
|
Commit Message
Siddharth Vadapalli
Jan. 31, 2024, 11:23 a.m. UTC
The PCIE_CTRL registers within the CTRL_MMR space of TI's K3 SoCs are
used to configure the link speed, lane count and mode of operation of
the respective PCIe instance. Add compatible for allowing the PCIe
driver to obtain a regmap for the PCIE_CTRL register within the System
Controller device-tree node in order to configure the PCIe instance
accordingly.
Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
---
This patch is based on linux-next tagged next-20240131.
Documentation/devicetree/bindings/mfd/syscon.yaml | 1 +
1 file changed, 1 insertion(+)
Comments
On 1/31/24 5:23 AM, Siddharth Vadapalli wrote: > The PCIE_CTRL registers within the CTRL_MMR space of TI's K3 SoCs are > used to configure the link speed, lane count and mode of operation of > the respective PCIe instance. Add compatible for allowing the PCIe > driver to obtain a regmap for the PCIE_CTRL register within the System > Controller device-tree node in order to configure the PCIe instance > accordingly. > > Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com> > --- > > This patch is based on linux-next tagged next-20240131. > > Documentation/devicetree/bindings/mfd/syscon.yaml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml > index 084b5c2a2a3c..da571a24e21f 100644 > --- a/Documentation/devicetree/bindings/mfd/syscon.yaml > +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml > @@ -73,6 +73,7 @@ properties: > - rockchip,rv1126-qos > - starfive,jh7100-sysmain > - ti,am654-dss-oldi-io-ctrl > + - ti,k3-pcie-ctrl This might not be the same for all K3 devices, you should use the name of the first device which uses this, so: ti,j721e-pcie-ctrl Andrew > > - const: syscon >
Hello Andrew, On 31/01/24 21:43, Andrew Davis wrote: > On 1/31/24 5:23 AM, Siddharth Vadapalli wrote: >> The PCIE_CTRL registers within the CTRL_MMR space of TI's K3 SoCs are >> used to configure the link speed, lane count and mode of operation of >> the respective PCIe instance. Add compatible for allowing the PCIe >> driver to obtain a regmap for the PCIE_CTRL register within the System >> Controller device-tree node in order to configure the PCIe instance >> accordingly. >> >> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com> >> --- >> >> This patch is based on linux-next tagged next-20240131. >> >> Documentation/devicetree/bindings/mfd/syscon.yaml | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml >> b/Documentation/devicetree/bindings/mfd/syscon.yaml >> index 084b5c2a2a3c..da571a24e21f 100644 >> --- a/Documentation/devicetree/bindings/mfd/syscon.yaml >> +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml >> @@ -73,6 +73,7 @@ properties: >> - rockchip,rv1126-qos >> - starfive,jh7100-sysmain >> - ti,am654-dss-oldi-io-ctrl >> + - ti,k3-pcie-ctrl > > This might not be the same for all K3 devices, you should use > the name of the first device which uses this, so: > > ti,j721e-pcie-ctrl It is the same for all K3 devices so far. However, since the convention appears to be the first device that it is applicable to as you pointed out, I will post the v2 patch for this accordingly.
On 01/02/2024 05:48, Siddharth Vadapalli wrote: > Hello Andrew, > > On 31/01/24 21:43, Andrew Davis wrote: >> On 1/31/24 5:23 AM, Siddharth Vadapalli wrote: >>> The PCIE_CTRL registers within the CTRL_MMR space of TI's K3 SoCs are >>> used to configure the link speed, lane count and mode of operation of >>> the respective PCIe instance. Add compatible for allowing the PCIe >>> driver to obtain a regmap for the PCIE_CTRL register within the System >>> Controller device-tree node in order to configure the PCIe instance >>> accordingly. >>> >>> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com> >>> --- >>> >>> This patch is based on linux-next tagged next-20240131. >>> >>> Documentation/devicetree/bindings/mfd/syscon.yaml | 1 + >>> 1 file changed, 1 insertion(+) >>> >>> diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml >>> b/Documentation/devicetree/bindings/mfd/syscon.yaml >>> index 084b5c2a2a3c..da571a24e21f 100644 >>> --- a/Documentation/devicetree/bindings/mfd/syscon.yaml >>> +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml >>> @@ -73,6 +73,7 @@ properties: >>> - rockchip,rv1126-qos >>> - starfive,jh7100-sysmain >>> - ti,am654-dss-oldi-io-ctrl >>> + - ti,k3-pcie-ctrl >> >> This might not be the same for all K3 devices, you should use >> the name of the first device which uses this, so: >> >> ti,j721e-pcie-ctrl > > It is the same for all K3 devices so far. However, since the convention appears > to be the first device that it is applicable to as you pointed out, I will post > the v2 patch for this accordingly. This was repeated so many times... so one more. Compatibles are specific to SoC, not to family. https://elixir.bootlin.com/linux/v6.1-rc1/source/Documentation/devicetree/bindings/writing-bindings.rst#L42 Best regards, Krzysztof
Hello Krzysztof, On 01/02/24 13:01, Krzysztof Kozlowski wrote: > On 01/02/2024 05:48, Siddharth Vadapalli wrote: >> Hello Andrew, >> >> On 31/01/24 21:43, Andrew Davis wrote: >>> On 1/31/24 5:23 AM, Siddharth Vadapalli wrote: >>>> The PCIE_CTRL registers within the CTRL_MMR space of TI's K3 SoCs are >>>> used to configure the link speed, lane count and mode of operation of >>>> the respective PCIe instance. Add compatible for allowing the PCIe >>>> driver to obtain a regmap for the PCIE_CTRL register within the System >>>> Controller device-tree node in order to configure the PCIe instance >>>> accordingly. >>>> >>>> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com> >>>> --- >>>> >>>> This patch is based on linux-next tagged next-20240131. >>>> >>>> Documentation/devicetree/bindings/mfd/syscon.yaml | 1 + >>>> 1 file changed, 1 insertion(+) >>>> >>>> diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml >>>> b/Documentation/devicetree/bindings/mfd/syscon.yaml >>>> index 084b5c2a2a3c..da571a24e21f 100644 >>>> --- a/Documentation/devicetree/bindings/mfd/syscon.yaml >>>> +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml >>>> @@ -73,6 +73,7 @@ properties: >>>> - rockchip,rv1126-qos >>>> - starfive,jh7100-sysmain >>>> - ti,am654-dss-oldi-io-ctrl >>>> + - ti,k3-pcie-ctrl >>> >>> This might not be the same for all K3 devices, you should use >>> the name of the first device which uses this, so: >>> >>> ti,j721e-pcie-ctrl >> >> It is the same for all K3 devices so far. However, since the convention appears >> to be the first device that it is applicable to as you pointed out, I will post >> the v2 patch for this accordingly. > > This was repeated so many times... so one more. Compatibles are specific > to SoC, not to family. > > https://elixir.bootlin.com/linux/v6.1-rc1/source/Documentation/devicetree/bindings/writing-bindings.rst#L42 Thank you for reviewing the patch and sharing your feedback. I will make sure not to repeat this in my future patches.
diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml index 084b5c2a2a3c..da571a24e21f 100644 --- a/Documentation/devicetree/bindings/mfd/syscon.yaml +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml @@ -73,6 +73,7 @@ properties: - rockchip,rv1126-qos - starfive,jh7100-sysmain - ti,am654-dss-oldi-io-ctrl + - ti,k3-pcie-ctrl - const: syscon