From: Johan Jonker <jbx6244@gmail.com>
To: linus.walleij@linaro.org, brgl@bgdev.pl
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
heiko@sntech.de, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
kever.yang@rock-chips.com, sjg@chromium.org,
philipp.tomsich@vrull.eu
Subject: [PATCH v1 2/4] gpio: gpio-rockchip: add compatible string per SoC
Date: Wed, 18 Jan 2023 13:14:47 +0100 [thread overview]
Message-ID: <1510c02c-f640-9924-e42e-fa34e28a580f@gmail.com> (raw)
In-Reply-To: <08de3f4b-e33f-95c8-3297-814ea107272a@gmail.com>
Currently all Rockchip gpio nodes have the same compatible.
Replace all the compatibles in gpio nodes to be able to
give them a consistent ID independent from probe order or alias.
Signed-off-by: Johan Jonker <jbx6244@gmail.com>
---
For now only add new compatibles.
No changes to rockchip_gpio_probe() function yet.
---
drivers/gpio/gpio-rockchip.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/drivers/gpio/gpio-rockchip.c b/drivers/gpio/gpio-rockchip.c
index e5de15a2a..493207de1 100644
--- a/drivers/gpio/gpio-rockchip.c
+++ b/drivers/gpio/gpio-rockchip.c
@@ -790,7 +790,22 @@ static int rockchip_gpio_remove(struct platform_device *pdev)
static const struct of_device_id rockchip_gpio_match[] = {
{ .compatible = "rockchip,gpio-bank", },
+ { .compatible = "rockchip,px30-gpio-bank", },
+ { .compatible = "rockchip,rk3036-gpio-bank", },
+ { .compatible = "rockchip,rk3066a-gpio-bank", },
+ { .compatible = "rockchip,rk3128-gpio-bank", },
+ { .compatible = "rockchip,rk3188-gpio-bank", },
{ .compatible = "rockchip,rk3188-gpio-bank0" },
+ { .compatible = "rockchip,rk3228-gpio-bank", },
+ { .compatible = "rockchip,rk3288-gpio-bank", },
+ { .compatible = "rockchip,rk3328-gpio-bank", },
+ { .compatible = "rockchip,rk3308-gpio-bank", },
+ { .compatible = "rockchip,rk3368-gpio-bank", },
+ { .compatible = "rockchip,rk3399-gpio-bank", },
+ { .compatible = "rockchip,rk3568-gpio-bank", },
+ { .compatible = "rockchip,rk3588-gpio-bank", },
+ { .compatible = "rockchip,rv1108-gpio-bank", },
+ { .compatible = "rockchip,rv1126-gpio-bank", },
{ },
};
--
2.20.1
next prev parent reply other threads:[~2023-01-18 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 12:13 [PATCH v1 1/4] dt-bindings: gpio: rockchip,gpio-bank: add compatible string per SoC Johan Jonker
2023-01-18 12:14 ` Johan Jonker [this message]
2023-01-18 14:14 ` [PATCH v1 2/4] gpio: gpio-rockchip: " Bartosz Golaszewski
2023-01-18 15:35 ` Krzysztof Kozlowski
2023-01-18 12:15 ` [PATCH v1 3/4] ARM: dts: rockchip: replace compatible gpio nodes Johan Jonker
2023-01-18 12:15 ` [PATCH v1 4/4] arm64: " Johan Jonker
2023-01-18 15:32 ` [PATCH v1 1/4] dt-bindings: gpio: rockchip,gpio-bank: add compatible string per SoC Rob Herring
2023-01-18 17:12 ` Johan Jonker
2023-01-18 18:32 ` Krzysztof Kozlowski
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=1510c02c-f640-9924-e42e-fa34e28a580f@gmail.com \
--to=jbx6244@gmail.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=philipp.tomsich@vrull.eu \
--cc=robh+dt@kernel.org \
--cc=sjg@chromium.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).