From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: rafael@kernel.org, info@metux.net, linus.walleij@linaro.org,
bgolaszewski@baylibre.com, robh+dt@kernel.org,
frowand.list@gmail.com, pantelis.antoniou@konsulko.com,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org
Subject: [RFC PATCH 07/12] gpio: amd-fch: add oftree probing support
Date: Mon, 8 Feb 2021 23:21:58 +0100 [thread overview]
Message-ID: <20210208222203.22335-8-info@metux.net> (raw)
In-Reply-To: <20210208222203.22335-1-info@metux.net>
Add support for probing via device tree.
---
drivers/gpio/gpio-amd-fch.c | 58 +++++++++++++++++++++++++
include/dt-bindings/gpio/amd-fch-gpio.h | 36 +++++++++++++++
include/linux/platform_data/gpio/gpio-amd-fch.h | 24 ++--------
3 files changed, 98 insertions(+), 20 deletions(-)
create mode 100644 include/dt-bindings/gpio/amd-fch-gpio.h
diff --git a/drivers/gpio/gpio-amd-fch.c b/drivers/gpio/gpio-amd-fch.c
index 2a21354ed6a0..32024f99dae5 100644
--- a/drivers/gpio/gpio-amd-fch.c
+++ b/drivers/gpio/gpio-amd-fch.c
@@ -136,12 +136,61 @@ static int amd_fch_gpio_request(struct gpio_chip *chip,
return 0;
}
+static struct amd_fch_gpio_pdata *load_pdata(struct device *dev)
+{
+ struct amd_fch_gpio_pdata *pdata;
+ int ret;
+
+ pdata = devm_kzalloc(dev, sizeof(struct amd_fch_gpio_pdata),
+ GFP_KERNEL);
+ if (!pdata)
+ goto nomem;
+
+ pdata->gpio_num = of_property_count_elems_of_size(dev->of_node,
+ "gpio-regs",
+ sizeof(u32));
+ pdata->gpio_reg = devm_kzalloc(dev, sizeof(int)*pdata->gpio_num,
+ GFP_KERNEL);
+ if (!pdata->gpio_reg)
+ goto nomem;
+
+ pdata->gpio_names = devm_kzalloc(dev, sizeof(char*)*pdata->gpio_num,
+ GFP_KERNEL);
+ if (!pdata->gpio_names)
+ goto nomem;
+
+ ret = of_property_read_variable_u32_array(dev->of_node, "gpio-regs",
+ pdata->gpio_reg,
+ pdata->gpio_num,
+ pdata->gpio_num);
+ if (ret != pdata->gpio_num) {
+ dev_err(dev, "failed reading gpio-regs from DT: %d\n", ret);
+ return NULL;
+ }
+
+ ret = of_property_read_string_array(dev->of_node, "gpio-line-names",
+ pdata->gpio_names, pdata->gpio_num);
+ if (ret != pdata->gpio_num) {
+ dev_err(dev, "failed reading gpio-names from DT: %d\n", ret);
+ return NULL;
+ }
+
+ return pdata;
+
+nomem:
+ dev_err(dev, "load_pdata: failed allocating memory\n");
+ return NULL;
+}
+
static int amd_fch_gpio_probe(struct platform_device *pdev)
{
struct amd_fch_gpio_priv *priv;
struct amd_fch_gpio_pdata *pdata;
pdata = dev_get_platdata(&pdev->dev);
+ if (!pdata)
+ pdata = load_pdata(&pdev->dev);
+
if (!pdata) {
dev_err(&pdev->dev, "no platform_data\n");
return -ENOENT;
@@ -165,6 +214,9 @@ static int amd_fch_gpio_probe(struct platform_device *pdev)
priv->gc.get_direction = amd_fch_gpio_get_direction;
priv->gc.get = amd_fch_gpio_get;
priv->gc.set = amd_fch_gpio_set;
+#ifdef CONFIG_OF_GPIO
+ priv->gc.of_node = pdev->dev.of_node;
+#endif
spin_lock_init(&priv->lock);
@@ -177,9 +229,15 @@ static int amd_fch_gpio_probe(struct platform_device *pdev)
return devm_gpiochip_add_data(&pdev->dev, &priv->gc, priv);
}
+static const struct of_device_id amd_fch_gpio_of_match[] = {
+ { .compatible = "amd,fch-gpio" },
+ {}
+};
+
static struct platform_driver amd_fch_gpio_driver = {
.driver = {
.name = AMD_FCH_GPIO_DRIVER_NAME,
+ .of_match_table = amd_fch_gpio_of_match,
},
.probe = amd_fch_gpio_probe,
};
diff --git a/include/dt-bindings/gpio/amd-fch-gpio.h b/include/dt-bindings/gpio/amd-fch-gpio.h
new file mode 100644
index 000000000000..7a47e6debcdb
--- /dev/null
+++ b/include/dt-bindings/gpio/amd-fch-gpio.h
@@ -0,0 +1,36 @@
+/* SPDX-License-Identifier: GPL-2.0+ */
+
+/*
+ * AMD FCH gpio platform data definitions
+ *
+ * Copyright (C) 2020 metux IT consult
+ * Author: Enrico Weigelt <info@metux.net>
+ *
+ */
+
+#ifndef __DT_BINDINGS_GPIO_AMD_FCH_REGS_H
+#define __DT_BINDINGS_GPIO_AMD_FCH_REGS_H
+
+/*
+ * gpio registers addresses
+ *
+ * these regs need to be assigned by board setup, since they're wired
+ * in very board specifici was, rarely documented, this should not be
+ * available to users.
+ */
+#define AMD_FCH_GPIO_REG_GPIO49 0x40
+#define AMD_FCH_GPIO_REG_GPIO50 0x41
+#define AMD_FCH_GPIO_REG_GPIO51 0x42
+#define AMD_FCH_GPIO_REG_GPIO55_DEVSLP0 0x43
+#define AMD_FCH_GPIO_REG_GPIO57 0x44
+#define AMD_FCH_GPIO_REG_GPIO58 0x45
+#define AMD_FCH_GPIO_REG_GPIO59_DEVSLP1 0x46
+#define AMD_FCH_GPIO_REG_GPIO64 0x47
+#define AMD_FCH_GPIO_REG_GPIO68 0x48
+#define AMD_FCH_GPIO_REG_GPIO66_SPKR 0x5B
+#define AMD_FCH_GPIO_REG_GPIO71 0x4D
+#define AMD_FCH_GPIO_REG_GPIO32_GE1 0x59
+#define AMD_FCH_GPIO_REG_GPIO33_GE2 0x5A
+#define AMT_FCH_GPIO_REG_GEVT22 0x09
+
+#endif /* __DT_BINDINGS_GPIO_AMD_FCH_REGS_H */
diff --git a/include/linux/platform_data/gpio/gpio-amd-fch.h b/include/linux/platform_data/gpio/gpio-amd-fch.h
index 255d51c9d36d..336f7387e82c 100644
--- a/include/linux/platform_data/gpio/gpio-amd-fch.h
+++ b/include/linux/platform_data/gpio/gpio-amd-fch.h
@@ -11,25 +11,9 @@
#ifndef __LINUX_PLATFORM_DATA_GPIO_AMD_FCH_H
#define __LINUX_PLATFORM_DATA_GPIO_AMD_FCH_H
-#define AMD_FCH_GPIO_DRIVER_NAME "gpio_amd_fch"
+#include <dt-bindings/gpio/amd-fch-gpio.h>
-/*
- * gpio register index definitions
- */
-#define AMD_FCH_GPIO_REG_GPIO49 0x40
-#define AMD_FCH_GPIO_REG_GPIO50 0x41
-#define AMD_FCH_GPIO_REG_GPIO51 0x42
-#define AMD_FCH_GPIO_REG_GPIO55_DEVSLP0 0x43
-#define AMD_FCH_GPIO_REG_GPIO57 0x44
-#define AMD_FCH_GPIO_REG_GPIO58 0x45
-#define AMD_FCH_GPIO_REG_GPIO59_DEVSLP1 0x46
-#define AMD_FCH_GPIO_REG_GPIO64 0x47
-#define AMD_FCH_GPIO_REG_GPIO68 0x48
-#define AMD_FCH_GPIO_REG_GPIO66_SPKR 0x5B
-#define AMD_FCH_GPIO_REG_GPIO71 0x4D
-#define AMD_FCH_GPIO_REG_GPIO32_GE1 0x59
-#define AMD_FCH_GPIO_REG_GPIO33_GE2 0x5A
-#define AMT_FCH_GPIO_REG_GEVT22 0x09
+#define AMD_FCH_GPIO_DRIVER_NAME "gpio_amd_fch"
/*
* struct amd_fch_gpio_pdata - GPIO chip platform data
@@ -39,8 +23,8 @@
*/
struct amd_fch_gpio_pdata {
int gpio_num;
- int *gpio_reg;
- const char * const *gpio_names;
+ u32 *gpio_reg;
+ const char * *gpio_names;
};
#endif /* __LINUX_PLATFORM_DATA_GPIO_AMD_FCH_H */
--
2.11.0
next prev parent reply other threads:[~2021-02-08 22:25 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 22:21 RFC: oftree based setup of composite board devices Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` [RFC PATCH 01/12] of: base: improve error message in of_phandle_iterator_next() Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` [RFC PATCH 02/12] of: base: introduce of_find_node_by_phandle_from() Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` [RFC PATCH 03/12] of: base: record root node in interator and use it for phandle lookup Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` [RFC PATCH 04/12] of: base: introduce of_match_string() Enrico Weigelt, metux IT consult
2021-02-08 23:52 ` Rob Herring
2021-02-08 22:21 ` [RFC PATCH 05/12] of: kobj: __of_attach_node_sysfs(): add optional basename parameter Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` [RFC PATCH 06/12] of: kobj: introduce of_attach_tree_sysfs() Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` Enrico Weigelt, metux IT consult [this message]
2021-02-11 9:57 ` [RFC PATCH 07/12] gpio: amd-fch: add oftree probing support Bartosz Golaszewski
2021-03-01 14:51 ` Linus Walleij
2021-03-11 10:17 ` Enrico Weigelt, metux IT consult
2021-03-11 10:42 ` Andy Shevchenko
2021-03-18 8:00 ` Enrico Weigelt, metux IT consult
2021-03-25 9:09 ` Linus Walleij
2021-02-08 22:21 ` [RFC PATCH 08/12] drivers: base: introduce bus_remove_device_by_name() Enrico Weigelt, metux IT consult
2021-02-08 22:22 ` [RFC PATCH 09/12] drivers: base: reintroduce find_bus() Enrico Weigelt, metux IT consult
2021-02-13 10:20 ` Greg KH
2021-02-23 20:13 ` Enrico Weigelt, metux IT consult
2021-02-24 8:00 ` Greg KH
2021-02-24 15:30 ` Enrico Weigelt, metux IT consult
2021-02-24 16:28 ` Greg KH
2021-02-08 22:22 ` [RFC PATCH 10/12] export bus_get() / bus_put() Enrico Weigelt, metux IT consult
2021-02-08 22:22 ` [RFC PATCH 11/12] platform/x86: skeleton for oftree based board device initialization Enrico Weigelt, metux IT consult
2021-02-10 10:32 ` Andy Shevchenko
2021-02-12 9:58 ` Linus Walleij
2021-02-12 11:54 ` Enrico Weigelt, metux IT consult
2021-02-15 1:18 ` Frank Rowand
2021-02-23 20:41 ` Enrico Weigelt, metux IT consult
2021-03-02 13:33 ` Linus Walleij
2021-02-08 22:22 ` [RFC PATCH 12/12] platform/x86/of: add support for PC Engines APU v2/3/4 boards Enrico Weigelt, metux IT consult
2021-02-09 0:06 ` Rob Herring
2021-02-11 13:15 ` Enrico Weigelt, metux IT consult
2021-03-01 14:55 ` Linus Walleij
2021-02-08 23:48 ` RFC: oftree based setup of composite board devices Rob Herring
2021-02-10 22:13 ` Enrico Weigelt, metux IT consult
2021-02-15 1:12 ` Frank Rowand
2021-02-15 15:35 ` Andy Shevchenko
2021-02-24 13:00 ` Enrico Weigelt, metux IT consult
2021-02-24 23:14 ` Frank Rowand
2021-03-05 18:29 ` Rob Herring
2021-02-10 10:30 ` Andy Shevchenko
2021-02-11 11:08 ` Enrico Weigelt, metux IT consult
2021-02-11 11:41 ` Andy Shevchenko
2021-02-11 17:01 ` Enrico Weigelt, metux IT consult
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=20210208222203.22335-8-info@metux.net \
--to=info@metux.net \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=rafael@kernel.org \
--cc=robh+dt@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).