From: "Duje Mihanović" <duje.mihanovic@skole.hr>
To: Robert Jarzmik <robert.jarzmik@free.fr>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andy@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, afaerber@suse.com,
"Duje Mihanović" <duje.mihanovic@skole.hr>
Subject: [PATCH v2 2/9] gpio: pxa: use dynamic allocation of base
Date: Thu, 27 Jul 2023 18:29:00 +0200 [thread overview]
Message-ID: <20230727162909.6031-3-duje.mihanovic@skole.hr> (raw)
In-Reply-To: <20230727162909.6031-1-duje.mihanovic@skole.hr>
Fixes the warning in dmesg that static allocation of the base is
deprecated.
This will break some older PXA boards (such as Spitz) as they still
seem to rely on fixed GPIO numbers with gpio_request and such.
Signed-off-by: Duje Mihanović <duje.mihanovic@skole.hr>
---
drivers/gpio/gpio-pxa.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpio/gpio-pxa.c b/drivers/gpio/gpio-pxa.c
index d92650aecb06..b48d142b736d 100644
--- a/drivers/gpio/gpio-pxa.c
+++ b/drivers/gpio/gpio-pxa.c
@@ -351,6 +351,7 @@ static int pxa_init_gpio_chip(struct pxa_gpio_chip *pchip, int ngpio, void __iom
pchip->chip.parent = pchip->dev;
pchip->chip.label = "gpio-pxa";
+ pchip->chip.base = -1;
pchip->chip.direction_input = pxa_gpio_direction_input;
pchip->chip.direction_output = pxa_gpio_direction_output;
pchip->chip.get = pxa_gpio_get;
--
2.41.0
next prev parent reply other threads:[~2023-07-27 16:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 16:28 [PATCH v2 0/9] Initial Marvell PXA1908 support Duje Mihanović
2023-07-27 16:28 ` [PATCH v2 1/9] gpio: pxa: disable pinctrl calls for MMP_GPIO Duje Mihanović
2023-07-27 16:39 ` Andy Shevchenko
2023-07-27 16:29 ` Duje Mihanović [this message]
2023-07-27 16:40 ` [PATCH v2 2/9] gpio: pxa: use dynamic allocation of base Andy Shevchenko
2023-07-30 21:18 ` Duje Mihanović
2023-08-07 13:31 ` Linus Walleij
2023-08-07 13:49 ` Andy Shevchenko
2023-08-07 15:19 ` Duje Mihanović
2023-07-27 16:29 ` [PATCH v2 3/9] clk: mmp: Switch to use struct u32_fract instead of custom one Duje Mihanović
2023-07-27 16:42 ` Andy Shevchenko
2023-07-27 16:29 ` [PATCH v2 4/9] dt-bindings: clock: Add Marvell PXA1908 clock bindings Duje Mihanović
2023-07-28 7:18 ` Krzysztof Kozlowski
2023-07-30 21:18 ` Duje Mihanović
2023-07-31 7:08 ` Krzysztof Kozlowski
2023-07-27 16:29 ` [PATCH v2 5/9] clk: mmp: Add Marvell PXA1908 clock driver Duje Mihanović
2023-07-27 16:29 ` [PATCH v2 6/9] dt-bindings: marvell: Document PXA1908 SoC Duje Mihanović
2023-07-28 7:19 ` Krzysztof Kozlowski
2023-07-30 21:18 ` Duje Mihanović
2023-07-31 7:09 ` Krzysztof Kozlowski
2023-07-27 16:29 ` [PATCH v2 7/9] arm64: Kconfig.platforms: Add config for Marvell PXA1908 platform Duje Mihanović
2023-07-27 16:29 ` [PATCH v2 8/9] arm64: dts: Add DTS for Marvell PXA1908 and samsung,coreprimevelte Duje Mihanović
2023-07-27 16:29 ` [PATCH v2 9/9] MAINTAINERS: add myself as Marvell PXA1908 maintainer Duje Mihanović
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=20230727162909.6031-3-duje.mihanovic@skole.hr \
--to=duje.mihanovic@skole.hr \
--cc=afaerber@suse.com \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).