From: Janusz Krzysztofik <jmkrzyszt@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>, Lee Jones <lee@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Tony Lindgren <tony@atomide.com>,
Russell King <linux@armlinux.org.uk>,
Krzysztof Kozlowski <krzk@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
patches@opensource.cirrus.com, linux-samsung-soc@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH RFT v2 4/6] ARM: omap1: ams-delta: use generic device properties for gpio-mmio
Date: Wed, 02 Jul 2025 19:31:18 +0200 [thread overview]
Message-ID: <12693741.O9o76ZdvQC@dell> (raw)
In-Reply-To: <20250701-gpio-mmio-pdata-v2-4-ebf34d273497@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 3983 bytes --]
On Tuesday, 1 July 2025 13:49:38 CEST Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> The two latch GPIO devices in ams-delta are registered with struct
> bgpio_pdata passed as platform_data to the gpio-mmio driver. We want to
> remove the bgpio_pdata from the kernel and the gpio-mmio driver is now
> also able to get the relevant values from the software node. Set up
> device properties and switch to using platform_device_info to register
> the devices as platform_add_devices() doesn't allow us to pass device
> properties to the driver model.
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Acked-by: Janusz Krzysztofik <jmkrzyszt@gmail.com>
> ---
> arch/arm/mach-omap1/board-ams-delta.c | 42 +++++++++++++++++------------------
> 1 file changed, 20 insertions(+), 22 deletions(-)
>
> diff --git a/arch/arm/mach-omap1/board-ams-delta.c b/arch/arm/mach-omap1/board-ams-delta.c
> index 0daf6c5b5c1cbcfd5bd15203cad119d39aa95f19..16392720296cd224732450c85419c35bbab506f6 100644
> --- a/arch/arm/mach-omap1/board-ams-delta.c
> +++ b/arch/arm/mach-omap1/board-ams-delta.c
> @@ -19,6 +19,7 @@
> #include <linux/mtd/nand-gpio.h>
> #include <linux/mtd/partitions.h>
> #include <linux/platform_device.h>
> +#include <linux/property.h>
> #include <linux/regulator/consumer.h>
> #include <linux/regulator/fixed.h>
> #include <linux/regulator/machine.h>
> @@ -175,20 +176,18 @@ static struct resource latch1_resources[] = {
>
> #define LATCH1_LABEL "latch1"
>
> -static struct bgpio_pdata latch1_pdata = {
> - .label = LATCH1_LABEL,
> - .base = -1,
> - .ngpio = LATCH1_NGPIO,
> +static const struct property_entry latch1_gpio_props[] = {
> + PROPERTY_ENTRY_STRING("label", LATCH1_LABEL),
> + PROPERTY_ENTRY_U32("ngpios", LATCH1_NGPIO),
> + { }
> };
>
> -static struct platform_device latch1_gpio_device = {
> +static const struct platform_device_info latch1_gpio_devinfo = {
> .name = "basic-mmio-gpio",
> .id = 0,
> - .resource = latch1_resources,
> - .num_resources = ARRAY_SIZE(latch1_resources),
> - .dev = {
> - .platform_data = &latch1_pdata,
> - },
> + .res = latch1_resources,
> + .num_res = ARRAY_SIZE(latch1_resources),
> + .properties = latch1_gpio_props,
> };
>
> #define LATCH1_PIN_LED_CAMERA 0
> @@ -213,20 +212,18 @@ static struct resource latch2_resources[] = {
>
> #define LATCH2_LABEL "latch2"
>
> -static struct bgpio_pdata latch2_pdata = {
> - .label = LATCH2_LABEL,
> - .base = -1,
> - .ngpio = LATCH2_NGPIO,
> +static const struct property_entry latch2_gpio_props[] = {
> + PROPERTY_ENTRY_STRING("label", LATCH2_LABEL),
> + PROPERTY_ENTRY_U32("ngpios", LATCH2_NGPIO),
> + { }
> };
>
> -static struct platform_device latch2_gpio_device = {
> +static struct platform_device_info latch2_gpio_devinfo = {
> .name = "basic-mmio-gpio",
> .id = 1,
> - .resource = latch2_resources,
> - .num_resources = ARRAY_SIZE(latch2_resources),
> - .dev = {
> - .platform_data = &latch2_pdata,
> - },
> + .res = latch2_resources,
> + .num_res = ARRAY_SIZE(latch2_resources),
> + .properties = latch2_gpio_props,
> };
>
> #define LATCH2_PIN_LCD_VBLEN 0
> @@ -542,8 +539,6 @@ static struct gpiod_lookup_table keybrd_pwr_gpio_table = {
> };
>
> static struct platform_device *ams_delta_devices[] __initdata = {
> - &latch1_gpio_device,
> - &latch2_gpio_device,
> &ams_delta_kp_device,
> &ams_delta_audio_device,
> &ams_delta_serio_device,
> @@ -697,6 +692,9 @@ static void __init ams_delta_init(void)
> omap1_usb_init(&ams_delta_usb_config);
> platform_add_devices(ams_delta_devices, ARRAY_SIZE(ams_delta_devices));
>
> + platform_device_register_full(&latch1_gpio_devinfo);
> + platform_device_register_full(&latch2_gpio_devinfo);
> +
> /*
> * As soon as regulator consumers have been registered, assign their
> * dev_names to consumer supply entries of respective regulators.
>
>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-07-02 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 11:49 [PATCH RFT v2 0/6] gpio: mmio: remove struct bgpio_pdata Bartosz Golaszewski
2025-07-01 11:49 ` [PATCH RFT v2 1/6] gpio: mmio: drop the big-endian platform device variant Bartosz Golaszewski
2025-07-01 11:49 ` [PATCH RFT v2 2/6] gpio: mmio: get chip label and GPIO base from device properties Bartosz Golaszewski
2025-07-01 11:49 ` [PATCH RFT v2 3/6] mfd: vexpress-sysreg: set-up software nodes for gpio-mmio Bartosz Golaszewski
2025-07-01 11:49 ` [PATCH RFT v2 4/6] ARM: omap1: ams-delta: use generic device properties " Bartosz Golaszewski
2025-07-02 17:31 ` Janusz Krzysztofik [this message]
2025-07-01 11:49 ` [PATCH RFT v2 5/6] ARM: s3c: crag6410: " Bartosz Golaszewski
2025-07-01 11:49 ` [PATCH RFT v2 6/6] gpio: mmio: remove struct bgpio_pdata Bartosz Golaszewski
2025-07-07 7:42 ` [PATCH RFT v2 0/6] " Bartosz Golaszewski
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=12693741.O9o76ZdvQC@dell \
--to=jmkrzyszt@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=alim.akhtar@samsung.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=krzk@kernel.org \
--cc=lee@kernel.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-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liviu.dudau@arm.com \
--cc=lpieralisi@kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=sudeep.holla@arm.com \
--cc=tony@atomide.com \
/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).