Message ID | 1416487023-25426-1-git-send-email-Vincent.Yang@tw.fujitsu.com |
---|---|
State | Rejected |
Headers | show |
On Thu, Nov 20, 2014 at 9:37 PM, Vincent Yang <vincent.yang.fujitsu@gmail.com> wrote: > Driver for Fujitsu MB86S7x SoCs that have a memory mapped GPIO controller. > > Signed-off-by: Andy Green <andy.green@linaro.org> > Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org> > Signed-off-by: Vincent Yang <Vincent.Yang@tw.fujitsu.com> > Signed-off-by: Tetsuya Nuriya <nuriya.tetsuya@jp.fujitsu.com> > --- > .../bindings/gpio/fujitsu,mb86s70-gpio.txt | 18 ++ > drivers/gpio/Kconfig | 6 + > drivers/gpio/Makefile | 1 + > drivers/gpio/gpio-mb86s7x.c | 211 +++++++++++++++++++++ > 4 files changed, 236 insertions(+) > create mode 100644 Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt > create mode 100644 drivers/gpio/gpio-mb86s7x.c > > diff --git a/Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt b/Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt > new file mode 100644 > index 0000000..38300ee > --- /dev/null > +++ b/Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt > @@ -0,0 +1,18 @@ > +Fujitsu MB86S7x GPIO Controller > +------------------------------- > + > +Required properties: > +- compatible: Should be "fujitsu,mb86s70-gpio" > +- gpio-controller: Marks the device node as a gpio controller. > +- #gpio-cells: Should be <2>. The first cell is the pin number and the > + second cell is used to specify optional parameters: > + - bit 0 specifies polarity (0 for normal, 1 for inverted). According to the example below and the code, "reg" and "clocks" are also required properties. > + > +Examples: > + gpio0: gpio@31000000 { > + compatible = "fujitsu,mb86s70-gpio"; > + reg = <0 0x31000000 0x10000>; > + gpio-controller; > + #gpio-cells = <2>; > + clocks = <&clk_alw_2_1>; Maybe add a "clocks-names" property so the clock can be given a meaningful name? > + }; > diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig > index 0959ca9..493b7fe 100644 > --- a/drivers/gpio/Kconfig > +++ b/drivers/gpio/Kconfig > @@ -181,6 +181,12 @@ config GPIO_F7188X > To compile this driver as a module, choose M here: the module will > be called f7188x-gpio. > > +config GPIO_MB86S7X > + bool "GPIO support for Fujitsu MB86S7x Platforms" > + depends on ARCH_MB86S7X > + help > + Say yes here to support the GPIO controller in LSI ZEVIO SoCs. > + > config GPIO_MOXART > bool "MOXART GPIO support" > depends on ARCH_MOXART > diff --git a/drivers/gpio/Makefile b/drivers/gpio/Makefile > index e5d346c..eec0664 100644 > --- a/drivers/gpio/Makefile > +++ b/drivers/gpio/Makefile > @@ -46,6 +46,7 @@ obj-$(CONFIG_GPIO_MAX730X) += gpio-max730x.o > obj-$(CONFIG_GPIO_MAX7300) += gpio-max7300.o > obj-$(CONFIG_GPIO_MAX7301) += gpio-max7301.o > obj-$(CONFIG_GPIO_MAX732X) += gpio-max732x.o > +obj-$(CONFIG_GPIO_MB86S7X) += gpio-mb86s7x.o > obj-$(CONFIG_GPIO_MC33880) += gpio-mc33880.o > obj-$(CONFIG_GPIO_MC9S08DZ60) += gpio-mc9s08dz60.o > obj-$(CONFIG_GPIO_MCP23S08) += gpio-mcp23s08.o > diff --git a/drivers/gpio/gpio-mb86s7x.c b/drivers/gpio/gpio-mb86s7x.c > new file mode 100644 > index 0000000..f0b2dc0 > --- /dev/null > +++ b/drivers/gpio/gpio-mb86s7x.c > @@ -0,0 +1,211 @@ > +/* > + * linux/drivers/gpio/gpio-mb86s7x.c > + * > + * Copyright (C) 2014 Fujitsu Semiconductor Limited > + * Copyright (C) 2014 Linaro Ltd. > + * > + * This program is free software: you can redistribute it and/or modify > + * it under the terms of the GNU General Public License as published by > + * the Free Software Foundation, version 2 of the License. > + * > + * This program is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > + * GNU General Public License for more details. > + */ > + > +#include <linux/io.h> > +#include <linux/init.h> > +#include <linux/clk.h> > +#include <linux/gpio.h> > +#include <linux/module.h> > +#include <linux/err.h> > +#include <linux/errno.h> > +#include <linux/ioport.h> > +#include <linux/of_device.h> > +#include <linux/platform_device.h> > +#include <linux/spinlock.h> > +#include <linux/slab.h> > + > +#define PDR(x) (0x0 + x) > +#define DDR(x) (0x10 + x) > +#define PFR(x) (0x20 + x) Everytime these macros are used in the code, they are called in the form PFR(offset / 8 * 4). How about doing this operation in the macros instead of repeating it at every call? > + > +struct mb86s70_gpio_chip { > + spinlock_t lock; > + struct clk *clk; > + void __iomem *base; > + struct gpio_chip gc; > +}; > + > +static int mb86s70_gpio_request(struct gpio_chip *gc, unsigned offset) > +{ > + struct mb86s70_gpio_chip *gchip = container_of(gc, > + struct mb86s70_gpio_chip, gc); Please have a chip_to_mb86s70() macro to avoid that cumbersome call to container_of in every function. Also I suggest you move the gpio_chip to the top of your mb86s70_gpio_chip structure so the container_of translates to a simple recast without any arithmetic. > + unsigned long flags; > + u32 val; > + > + spin_lock_irqsave(&gchip->lock, flags); > + val = readl(gchip->base + PFR(offset / 8 * 4)); Same, having mb86s70_readl()/mb86s70_writel() functions would prevent you from explicitly doing pointer arithmetic every time you write a register. > + val &= ~(1 << (offset % 8)); /* as gpio-port */ val &= ~BIT(offset % 8); ? Same everywhere it applies. > + writel(val, gchip->base + PFR(offset / 8 * 4)); > + spin_unlock_irqrestore(&gchip->lock, flags); > + > + return 0; > +} > + > +static void mb86s70_gpio_free(struct gpio_chip *gc, unsigned offset) > +{ > + struct mb86s70_gpio_chip *gchip = container_of(gc, > + struct mb86s70_gpio_chip, gc); > + unsigned long flags; > + u32 val; > + > + spin_lock_irqsave(&gchip->lock, flags); > + val = readl(gchip->base + PFR(offset / 8 * 4)); > + val |= (1 << (offset % 8)); /* as peri-port */ > + writel(val, gchip->base + PFR(offset / 8 * 4)); > + spin_unlock_irqrestore(&gchip->lock, flags); > +} > + > +static int mb86s70_gpio_direction_input(struct gpio_chip *gc, unsigned offset) > +{ > + struct mb86s70_gpio_chip *gchip = > + container_of(gc, struct mb86s70_gpio_chip, gc); > + unsigned long flags; > + unsigned char val; > + > + spin_lock_irqsave(&gchip->lock, flags); > + val = readl(gchip->base + DDR(offset / 8 * 4)); > + val &= ~(1 << (offset % 8)); > + writel(val, gchip->base + DDR(offset / 8 * 4)); > + spin_unlock_irqrestore(&gchip->lock, flags); > + > + return 0; > +} > + > +static int mb86s70_gpio_direction_output(struct gpio_chip *gc, > + unsigned offset, int value) > +{ > + struct mb86s70_gpio_chip *gchip = > + container_of(gc, struct mb86s70_gpio_chip, gc); > + unsigned long flags; > + unsigned char val; > + > + spin_lock_irqsave(&gchip->lock, flags); > + > + val = readl(gchip->base + PDR(offset / 8 * 4)); > + if (value) > + val |= (1 << (offset % 8)); > + else > + val &= ~(1 << (offset % 8)); > + writel(val, gchip->base + PDR(offset / 8 * 4)); > + > + val = readl(gchip->base + DDR(offset / 8 * 4)); > + val |= (1 << (offset % 8)); > + writel(val, gchip->base + DDR(offset / 8 * 4)); > + > + spin_unlock_irqrestore(&gchip->lock, flags); > + > + return 0; > +} > + > +static int mb86s70_gpio_get(struct gpio_chip *gc, unsigned offset) > +{ > + struct mb86s70_gpio_chip *gchip = > + container_of(gc, struct mb86s70_gpio_chip, gc); > + unsigned char val; > + > + val = readl(gchip->base + PDR(offset / 8 * 4)); > + val &= (1 << (offset % 8)); > + return val ? 1 : 0; Shouldn't this function be protected by the spin lock as well? These minor comments aside, the driver looks nice and simple. -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Nov 20, 2014 at 1:37 PM, Vincent Yang <vincent.yang.fujitsu@gmail.com> wrote: > Driver for Fujitsu MB86S7x SoCs that have a memory mapped GPIO controller. > > Signed-off-by: Andy Green <andy.green@linaro.org> > Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org> > Signed-off-by: Vincent Yang <Vincent.Yang@tw.fujitsu.com> > Signed-off-by: Tetsuya Nuriya <nuriya.tetsuya@jp.fujitsu.com> This is a very simple MMIO GPIO controller. Why can this *not* just select GPIO_GENERIC and use drivers/gpio/gpio-generic.c? You need a smallish driver making use of the generic MMIO library, see for example drivers/gpio/gpio-74xx-mmio.c or any other driver selecting GPIO_GENERIC. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 27 November 2014 at 13:03, Alexandre Courbot <gnurou@gmail.com> wrote: > On Thu, Nov 20, 2014 at 9:37 PM, Vincent Yang > <vincent.yang.fujitsu@gmail.com> wrote: >> Driver for Fujitsu MB86S7x SoCs that have a memory mapped GPIO controller. >> >> Signed-off-by: Andy Green <andy.green@linaro.org> >> Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org> >> Signed-off-by: Vincent Yang <Vincent.Yang@tw.fujitsu.com> >> Signed-off-by: Tetsuya Nuriya <nuriya.tetsuya@jp.fujitsu.com> >> --- >> .../bindings/gpio/fujitsu,mb86s70-gpio.txt | 18 ++ >> drivers/gpio/Kconfig | 6 + >> drivers/gpio/Makefile | 1 + >> drivers/gpio/gpio-mb86s7x.c | 211 +++++++++++++++++++++ >> 4 files changed, 236 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt >> create mode 100644 drivers/gpio/gpio-mb86s7x.c >> >> diff --git a/Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt b/Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt >> new file mode 100644 >> index 0000000..38300ee >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt >> @@ -0,0 +1,18 @@ >> +Fujitsu MB86S7x GPIO Controller >> +------------------------------- >> + >> +Required properties: >> +- compatible: Should be "fujitsu,mb86s70-gpio" >> +- gpio-controller: Marks the device node as a gpio controller. >> +- #gpio-cells: Should be <2>. The first cell is the pin number and the >> + second cell is used to specify optional parameters: >> + - bit 0 specifies polarity (0 for normal, 1 for inverted). > > According to the example below and the code, "reg" and "clocks" are > also required properties. > OK, will add them as well. >> + >> +Examples: >> + gpio0: gpio@31000000 { >> + compatible = "fujitsu,mb86s70-gpio"; >> + reg = <0 0x31000000 0x10000>; >> + gpio-controller; >> + #gpio-cells = <2>; >> + clocks = <&clk_alw_2_1>; > > Maybe add a "clocks-names" property so the clock can be given a meaningful name? > Other mb86s7x drivers don't use that either and we do just fine :) >> + >> +#define PDR(x) (0x0 + x) >> +#define DDR(x) (0x10 + x) >> +#define PFR(x) (0x20 + x) > > Everytime these macros are used in the code, they are called in the > form PFR(offset / 8 * 4). How about doing this operation in the macros > instead of repeating it at every call? > OK >> + >> +struct mb86s70_gpio_chip { >> + spinlock_t lock; >> + struct clk *clk; >> + void __iomem *base; >> + struct gpio_chip gc; >> +}; >> + >> +static int mb86s70_gpio_request(struct gpio_chip *gc, unsigned offset) >> +{ >> + struct mb86s70_gpio_chip *gchip = container_of(gc, >> + struct mb86s70_gpio_chip, gc); > > Please have a chip_to_mb86s70() macro to avoid that cumbersome call to > container_of in every function. Also I suggest you move the gpio_chip > to the top of your mb86s70_gpio_chip structure so the container_of > translates to a simple recast without any arithmetic. > OK >> + unsigned long flags; >> + u32 val; >> + >> + spin_lock_irqsave(&gchip->lock, flags); >> + val = readl(gchip->base + PFR(offset / 8 * 4)); > > Same, having mb86s70_readl()/mb86s70_writel() functions would prevent > you from explicitly doing pointer arithmetic every time you write a > register. > This becomes trivial after updating macros. >> + val &= ~(1 << (offset % 8)); /* as gpio-port */ > > val &= ~BIT(offset % 8); ? Same everywhere it applies. > OK >> + >> +static int mb86s70_gpio_get(struct gpio_chip *gc, unsigned offset) >> +{ >> + struct mb86s70_gpio_chip *gchip = >> + container_of(gc, struct mb86s70_gpio_chip, gc); >> + unsigned char val; >> + >> + val = readl(gchip->base + PDR(offset / 8 * 4)); >> + val &= (1 << (offset % 8)); >> + return val ? 1 : 0; > > Shouldn't this function be protected by the spin lock as well? > hmm... then we need to fix most other drivers as well :) > These minor comments aside, the driver looks nice and simple. Thanks for the review. -Jassi -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 3 December 2014 at 19:02, Linus Walleij <linus.walleij@linaro.org> wrote: > On Thu, Nov 20, 2014 at 1:37 PM, Vincent Yang > <vincent.yang.fujitsu@gmail.com> wrote: > >> Driver for Fujitsu MB86S7x SoCs that have a memory mapped GPIO controller. >> >> Signed-off-by: Andy Green <andy.green@linaro.org> >> Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org> >> Signed-off-by: Vincent Yang <Vincent.Yang@tw.fujitsu.com> >> Signed-off-by: Tetsuya Nuriya <nuriya.tetsuya@jp.fujitsu.com> > > This is a very simple MMIO GPIO controller. > > Why can this *not* just select GPIO_GENERIC and > use drivers/gpio/gpio-generic.c? > The math isn't the simple shift operation that the gpio-generic.c assumes. -jassi -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt b/Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt new file mode 100644 index 0000000..38300ee --- /dev/null +++ b/Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt @@ -0,0 +1,18 @@ +Fujitsu MB86S7x GPIO Controller +------------------------------- + +Required properties: +- compatible: Should be "fujitsu,mb86s70-gpio" +- gpio-controller: Marks the device node as a gpio controller. +- #gpio-cells: Should be <2>. The first cell is the pin number and the + second cell is used to specify optional parameters: + - bit 0 specifies polarity (0 for normal, 1 for inverted). + +Examples: + gpio0: gpio@31000000 { + compatible = "fujitsu,mb86s70-gpio"; + reg = <0 0x31000000 0x10000>; + gpio-controller; + #gpio-cells = <2>; + clocks = <&clk_alw_2_1>; + }; diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig index 0959ca9..493b7fe 100644 --- a/drivers/gpio/Kconfig +++ b/drivers/gpio/Kconfig @@ -181,6 +181,12 @@ config GPIO_F7188X To compile this driver as a module, choose M here: the module will be called f7188x-gpio. +config GPIO_MB86S7X + bool "GPIO support for Fujitsu MB86S7x Platforms" + depends on ARCH_MB86S7X + help + Say yes here to support the GPIO controller in LSI ZEVIO SoCs. + config GPIO_MOXART bool "MOXART GPIO support" depends on ARCH_MOXART diff --git a/drivers/gpio/Makefile b/drivers/gpio/Makefile index e5d346c..eec0664 100644 --- a/drivers/gpio/Makefile +++ b/drivers/gpio/Makefile @@ -46,6 +46,7 @@ obj-$(CONFIG_GPIO_MAX730X) += gpio-max730x.o obj-$(CONFIG_GPIO_MAX7300) += gpio-max7300.o obj-$(CONFIG_GPIO_MAX7301) += gpio-max7301.o obj-$(CONFIG_GPIO_MAX732X) += gpio-max732x.o +obj-$(CONFIG_GPIO_MB86S7X) += gpio-mb86s7x.o obj-$(CONFIG_GPIO_MC33880) += gpio-mc33880.o obj-$(CONFIG_GPIO_MC9S08DZ60) += gpio-mc9s08dz60.o obj-$(CONFIG_GPIO_MCP23S08) += gpio-mcp23s08.o diff --git a/drivers/gpio/gpio-mb86s7x.c b/drivers/gpio/gpio-mb86s7x.c new file mode 100644 index 0000000..f0b2dc0 --- /dev/null +++ b/drivers/gpio/gpio-mb86s7x.c @@ -0,0 +1,211 @@ +/* + * linux/drivers/gpio/gpio-mb86s7x.c + * + * Copyright (C) 2014 Fujitsu Semiconductor Limited + * Copyright (C) 2014 Linaro Ltd. + * + * This program is free software: you can redistribute it and/or modify + * it under the terms of the GNU General Public License as published by + * the Free Software Foundation, version 2 of the License. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + */ + +#include <linux/io.h> +#include <linux/init.h> +#include <linux/clk.h> +#include <linux/gpio.h> +#include <linux/module.h> +#include <linux/err.h> +#include <linux/errno.h> +#include <linux/ioport.h> +#include <linux/of_device.h> +#include <linux/platform_device.h> +#include <linux/spinlock.h> +#include <linux/slab.h> + +#define PDR(x) (0x0 + x) +#define DDR(x) (0x10 + x) +#define PFR(x) (0x20 + x) + +struct mb86s70_gpio_chip { + spinlock_t lock; + struct clk *clk; + void __iomem *base; + struct gpio_chip gc; +}; + +static int mb86s70_gpio_request(struct gpio_chip *gc, unsigned offset) +{ + struct mb86s70_gpio_chip *gchip = container_of(gc, + struct mb86s70_gpio_chip, gc); + unsigned long flags; + u32 val; + + spin_lock_irqsave(&gchip->lock, flags); + val = readl(gchip->base + PFR(offset / 8 * 4)); + val &= ~(1 << (offset % 8)); /* as gpio-port */ + writel(val, gchip->base + PFR(offset / 8 * 4)); + spin_unlock_irqrestore(&gchip->lock, flags); + + return 0; +} + +static void mb86s70_gpio_free(struct gpio_chip *gc, unsigned offset) +{ + struct mb86s70_gpio_chip *gchip = container_of(gc, + struct mb86s70_gpio_chip, gc); + unsigned long flags; + u32 val; + + spin_lock_irqsave(&gchip->lock, flags); + val = readl(gchip->base + PFR(offset / 8 * 4)); + val |= (1 << (offset % 8)); /* as peri-port */ + writel(val, gchip->base + PFR(offset / 8 * 4)); + spin_unlock_irqrestore(&gchip->lock, flags); +} + +static int mb86s70_gpio_direction_input(struct gpio_chip *gc, unsigned offset) +{ + struct mb86s70_gpio_chip *gchip = + container_of(gc, struct mb86s70_gpio_chip, gc); + unsigned long flags; + unsigned char val; + + spin_lock_irqsave(&gchip->lock, flags); + val = readl(gchip->base + DDR(offset / 8 * 4)); + val &= ~(1 << (offset % 8)); + writel(val, gchip->base + DDR(offset / 8 * 4)); + spin_unlock_irqrestore(&gchip->lock, flags); + + return 0; +} + +static int mb86s70_gpio_direction_output(struct gpio_chip *gc, + unsigned offset, int value) +{ + struct mb86s70_gpio_chip *gchip = + container_of(gc, struct mb86s70_gpio_chip, gc); + unsigned long flags; + unsigned char val; + + spin_lock_irqsave(&gchip->lock, flags); + + val = readl(gchip->base + PDR(offset / 8 * 4)); + if (value) + val |= (1 << (offset % 8)); + else + val &= ~(1 << (offset % 8)); + writel(val, gchip->base + PDR(offset / 8 * 4)); + + val = readl(gchip->base + DDR(offset / 8 * 4)); + val |= (1 << (offset % 8)); + writel(val, gchip->base + DDR(offset / 8 * 4)); + + spin_unlock_irqrestore(&gchip->lock, flags); + + return 0; +} + +static int mb86s70_gpio_get(struct gpio_chip *gc, unsigned offset) +{ + struct mb86s70_gpio_chip *gchip = + container_of(gc, struct mb86s70_gpio_chip, gc); + unsigned char val; + + val = readl(gchip->base + PDR(offset / 8 * 4)); + val &= (1 << (offset % 8)); + return val ? 1 : 0; +} + +static void mb86s70_gpio_set(struct gpio_chip *gc, unsigned offset, int value) +{ + struct mb86s70_gpio_chip *gchip = + container_of(gc, struct mb86s70_gpio_chip, gc); + unsigned long flags; + unsigned char val; + + spin_lock_irqsave(&gchip->lock, flags); + + val = readl(gchip->base + PDR(offset / 8 * 4)); + if (value) + val |= (1 << (offset % 8)); + else + val &= ~(1 << (offset % 8)); + writel(val, gchip->base + PDR(offset / 8 * 4)); + + spin_unlock_irqrestore(&gchip->lock, flags); +} + +static int mb86s70_gpio_probe(struct platform_device *pdev) +{ + struct mb86s70_gpio_chip *gchip; + struct resource *res; + int ret; + + gchip = devm_kzalloc(&pdev->dev, sizeof(*gchip), GFP_KERNEL); + if (gchip == NULL) + return -ENOMEM; + + platform_set_drvdata(pdev, gchip); + + res = platform_get_resource(pdev, IORESOURCE_MEM, 0); + gchip->base = devm_ioremap_resource(&pdev->dev, res); + if (IS_ERR(gchip->base)) + return PTR_ERR(gchip->base); + + gchip->clk = devm_clk_get(&pdev->dev, NULL); + if (IS_ERR(gchip->clk)) + return PTR_ERR(gchip->clk); + + clk_prepare_enable(gchip->clk); + + spin_lock_init(&gchip->lock); + + gchip->gc.direction_output = mb86s70_gpio_direction_output; + gchip->gc.direction_input = mb86s70_gpio_direction_input; + gchip->gc.request = mb86s70_gpio_request; + gchip->gc.free = mb86s70_gpio_free; + gchip->gc.get = mb86s70_gpio_get; + gchip->gc.set = mb86s70_gpio_set; + gchip->gc.label = dev_name(&pdev->dev); + gchip->gc.ngpio = 32; + gchip->gc.owner = THIS_MODULE; + gchip->gc.dev = &pdev->dev; + gchip->gc.base = -1; + + ret = gpiochip_add(&gchip->gc); + if (ret) { + dev_err(&pdev->dev, "couldn't register gpio driver\n"); + clk_disable_unprepare(gchip->clk); + } + + return ret; +} + +static const struct of_device_id mb86s70_gpio_dt_ids[] = { + { .compatible = "fujitsu,mb86s70-gpio" }, + { /* sentinel */ } +}; +MODULE_DEVICE_TABLE(of, mb86s70_gpio_dt_ids); + +static struct platform_driver mb86s70_gpio_driver = { + .probe = mb86s70_gpio_probe, + .driver = { + .name = "mb86s70-gpio", + .of_match_table = mb86s70_gpio_dt_ids, + }, +}; + +static int __init mb86s70_gpio_init(void) +{ + return platform_driver_register(&mb86s70_gpio_driver); +} +subsys_initcall(mb86s70_gpio_init); + +MODULE_DESCRIPTION("MB86S7x GPIO Driver"); +MODULE_ALIAS("platform:mb86s70-gpio"); +MODULE_LICENSE("GPL");