From: Fabio Estevam <festevam@gmail.com>
To: shawnguo@kernel.org
Cc: marex@denx.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, conor+dt@kernel.org,
bhelgaas@google.com, Fabio Estevam <festevam@denx.de>
Subject: [PATCH v6 1/5] PCI: imx6: Use a more specific i.MX6SX GPR compatible
Date: Mon, 22 May 2023 17:14:00 -0300 [thread overview]
Message-ID: <20230522201404.660242-1-festevam@gmail.com> (raw)
From: Fabio Estevam <festevam@denx.de>
On the i.MX6SX case, the more specific GPR (General Purpose
Register) compatible, "fsl,imx6sx-iomuxc-gpr", can be used instead
of the more generic "fsl,imx6q-iomuxc-gpr" one.
Switch to using the more specific i.MX6SX GPR compatible.
The motivation for this change is to allow the introduction of
i.MX6SX GPR driver that will be used to control the i.MX6SX LDB bridge.
Old DTBs are unaffected by this change.
Suggested-by: Marek Vasut <marex@denx.de>
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
Changes since v5:
- Newly introduced.
drivers/pci/controller/dwc/pci-imx6.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/controller/dwc/pci-imx6.c b/drivers/pci/controller/dwc/pci-imx6.c
index 52906f999f2b..4803e3c9ee37 100644
--- a/drivers/pci/controller/dwc/pci-imx6.c
+++ b/drivers/pci/controller/dwc/pci-imx6.c
@@ -1460,7 +1460,7 @@ static const struct imx6_pcie_drvdata drvdata[] = {
.flags = IMX6_PCIE_FLAG_IMX6_PHY |
IMX6_PCIE_FLAG_IMX6_SPEED_CHANGE |
IMX6_PCIE_FLAG_SUPPORTS_SUSPEND,
- .gpr = "fsl,imx6q-iomuxc-gpr",
+ .gpr = "fsl,imx6sx-iomuxc-gpr",
},
[IMX6QP] = {
.variant = IMX6QP,
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-05-22 20:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 20:14 Fabio Estevam [this message]
2023-05-22 20:14 ` [PATCH v6 2/5] dt-bindings: display: bridge: ldb: Adjust imx6sx entries Fabio Estevam
2023-05-22 22:06 ` Conor Dooley
2023-05-23 2:27 ` Marek Vasut
2023-05-22 20:14 ` [PATCH v6 3/5] dt-bindings: soc: Add i.MX6SX General Purpose Register Fabio Estevam
2023-05-22 21:32 ` Rob Herring
2023-05-22 21:53 ` Fabio Estevam
2023-06-07 20:31 ` Rob Herring
2023-06-07 21:07 ` Fabio Estevam
2023-05-22 22:10 ` Conor Dooley
2023-05-23 2:28 ` Marek Vasut
2023-05-22 20:14 ` [PATCH v6 4/5] ARM: dts: imx6sx: Add LDB support Fabio Estevam
2023-05-23 2:29 ` Marek Vasut
2023-05-23 11:34 ` Fabio Estevam
2023-05-23 12:56 ` Marek Vasut
2023-05-22 20:14 ` [PATCH v6 5/5] soc: imx: imx6sx-gpr: Introduce a GPR driver Fabio Estevam
2023-05-23 2:30 ` Marek Vasut
2023-05-23 11:44 ` Fabio Estevam
2023-05-23 12:57 ` Marek Vasut
2023-05-23 21:13 ` Fabio Estevam
2023-05-23 23:30 ` Marek Vasut
2023-05-23 23:41 ` Fabio Estevam
2023-05-23 2:27 ` [PATCH v6 1/5] PCI: imx6: Use a more specific i.MX6SX GPR compatible Marek Vasut
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=20230522201404.660242-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).