From: Daniel Palmer <daniel@0x0f.com>
To: soc@kernel.org, linux-gpio@vger.kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
robh@kernel.org, w@1wt.eu, daniel@0x0f.com
Subject: [PATCH v4 0/5] Add GPIO support for MStar/SigmaStar ARMv7
Date: Sun, 29 Nov 2020 20:07:57 +0900 [thread overview]
Message-ID: <20201129110803.2461700-1-daniel@0x0f.com> (raw)
At the moment the MStar/SigmaStar support is only really
capable of shell from an initramfs and not much else.
Most of the interesting drivers are blocked on clock and pinctrl
drivers and those are going to take me a little while to get cleaned
up.
Clock and pinctrl aren't needed for basic GPIO to work (all pins
start off as GPIOs..) and it makes it possible to actually do something
so this series adds everything that is needed for the main GPIO
block in these chips.
Changes since v3:
- Remove unneeded "gpio-ranges-group-names" property from binding yaml.
Changes since v2:
- Numerous style and code cleanups as suggested by Andy Shevchenko,
Linus Walleij, Marc Zyngier and Rob Herring.
- Pad names moved out of the binding header because they are no longer
needed there. The pin/pad numbers are still there as I couldn't think
of a better way to do this. meson8b-gpio.h seems to be similar.
Changes since v1:
- Moves the binding header commit before the yaml commit
- Fixes the license on the binding header to include BSD-2-Clause
- The driver has been reworked to use the gpiolib irqchip functionality
as suggested by Linus[0]. I think I got this right. The gpio controller
doesn't actually do anything with interrupts itself.. It just happens
to have 4 lines that are also wired to lines on one of the interrupt
controllers.
- Now that the driver is an interrupt controller in it's own right for
the gpio lines that have associated interrupts the binding description
has been updated to add the interrupt-controller bits and remove the
description of the interrupt-names that described how the interrupts
used to be passed in.
Daniel Palmer (5):
dt-bindings: gpio: Add a binding header for the MSC313 GPIO driver
dt-bindings: gpio: Binding for MStar MSC313 GPIO controller
gpio: msc313: MStar MSC313 GPIO driver
ARM: mstar: Add gpio controller to MStar base dtsi
ARM: mstar: Fill in GPIO controller properties for infinity
.../bindings/gpio/mstar,msc313-gpio.yaml | 59 +++
MAINTAINERS | 3 +
arch/arm/boot/dts/mstar-infinity.dtsi | 7 +
arch/arm/boot/dts/mstar-v7.dtsi | 10 +
drivers/gpio/Kconfig | 11 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-msc313.c | 460 ++++++++++++++++++
include/dt-bindings/gpio/msc313-gpio.h | 53 ++
8 files changed, 604 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/mstar,msc313-gpio.yaml
create mode 100644 drivers/gpio/gpio-msc313.c
create mode 100644 include/dt-bindings/gpio/msc313-gpio.h
--
2.29.2
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Palmer <daniel@0x0f.com>
To: soc@kernel.org, linux-gpio@vger.kernel.org
Cc: devicetree@vger.kernel.org, robh@kernel.org,
linus.walleij@linaro.org, daniel@0x0f.com,
linux-kernel@vger.kernel.org, w@1wt.eu,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] Add GPIO support for MStar/SigmaStar ARMv7
Date: Sun, 29 Nov 2020 20:07:57 +0900 [thread overview]
Message-ID: <20201129110803.2461700-1-daniel@0x0f.com> (raw)
Message-ID: <20201129110757.sAxrgpJrS0L2RCgSWkG2swrTFI5ueLmhUIg6rK40RDQ@z> (raw)
At the moment the MStar/SigmaStar support is only really
capable of shell from an initramfs and not much else.
Most of the interesting drivers are blocked on clock and pinctrl
drivers and those are going to take me a little while to get cleaned
up.
Clock and pinctrl aren't needed for basic GPIO to work (all pins
start off as GPIOs..) and it makes it possible to actually do something
so this series adds everything that is needed for the main GPIO
block in these chips.
Changes since v3:
- Remove unneeded "gpio-ranges-group-names" property from binding yaml.
Changes since v2:
- Numerous style and code cleanups as suggested by Andy Shevchenko,
Linus Walleij, Marc Zyngier and Rob Herring.
- Pad names moved out of the binding header because they are no longer
needed there. The pin/pad numbers are still there as I couldn't think
of a better way to do this. meson8b-gpio.h seems to be similar.
Changes since v1:
- Moves the binding header commit before the yaml commit
- Fixes the license on the binding header to include BSD-2-Clause
- The driver has been reworked to use the gpiolib irqchip functionality
as suggested by Linus[0]. I think I got this right. The gpio controller
doesn't actually do anything with interrupts itself.. It just happens
to have 4 lines that are also wired to lines on one of the interrupt
controllers.
- Now that the driver is an interrupt controller in it's own right for
the gpio lines that have associated interrupts the binding description
has been updated to add the interrupt-controller bits and remove the
description of the interrupt-names that described how the interrupts
used to be passed in.
Daniel Palmer (5):
dt-bindings: gpio: Add a binding header for the MSC313 GPIO driver
dt-bindings: gpio: Binding for MStar MSC313 GPIO controller
gpio: msc313: MStar MSC313 GPIO driver
ARM: mstar: Add gpio controller to MStar base dtsi
ARM: mstar: Fill in GPIO controller properties for infinity
.../bindings/gpio/mstar,msc313-gpio.yaml | 59 +++
MAINTAINERS | 3 +
arch/arm/boot/dts/mstar-infinity.dtsi | 7 +
arch/arm/boot/dts/mstar-v7.dtsi | 10 +
drivers/gpio/Kconfig | 11 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-msc313.c | 460 ++++++++++++++++++
include/dt-bindings/gpio/msc313-gpio.h | 53 ++
8 files changed, 604 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/mstar,msc313-gpio.yaml
create mode 100644 drivers/gpio/gpio-msc313.c
create mode 100644 include/dt-bindings/gpio/msc313-gpio.h
--
2.29.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-11-29 11:08 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 11:07 Daniel Palmer [this message]
2020-11-29 11:07 ` [PATCH v4 0/5] Add GPIO support for MStar/SigmaStar ARMv7 Daniel Palmer
2020-11-29 11:07 ` [PATCH v4 1/5] dt-bindings: gpio: Add a binding header for the MSC313 GPIO driver Daniel Palmer
2020-11-29 11:07 ` Daniel Palmer
2020-11-29 11:07 ` [PATCH v4 2/5] dt-bindings: gpio: Binding for MStar MSC313 GPIO controller Daniel Palmer
2020-11-29 11:07 ` Daniel Palmer
2020-12-01 2:02 ` Rob Herring
2020-12-01 2:02 ` Rob Herring
2020-11-29 11:08 ` [PATCH v4 3/5] gpio: msc313: MStar MSC313 GPIO driver Daniel Palmer
2020-11-29 11:08 ` Daniel Palmer
2020-12-09 21:58 ` Arnd Bergmann
2020-12-09 21:58 ` Arnd Bergmann
2020-12-10 10:29 ` Daniel Palmer
2020-12-10 10:29 ` Daniel Palmer
2020-12-10 10:29 ` Daniel Palmer
2020-12-10 14:27 ` Arnd Bergmann
2020-12-10 14:27 ` Arnd Bergmann
2020-12-10 15:49 ` Daniel Palmer
2020-12-10 15:49 ` Daniel Palmer
2020-12-10 15:49 ` Daniel Palmer
2020-12-10 20:22 ` Arnd Bergmann
2020-12-10 20:22 ` Arnd Bergmann
2020-12-10 14:23 ` Andy Shevchenko
2020-12-10 14:23 ` Andy Shevchenko
2020-12-10 14:23 ` Andy Shevchenko
2020-12-10 15:21 ` Daniel Palmer
2020-12-10 15:21 ` Daniel Palmer
2020-12-10 15:21 ` Daniel Palmer
2020-11-29 11:08 ` [PATCH v4 4/5] ARM: mstar: Add gpio controller to MStar base dtsi Daniel Palmer
2020-11-29 11:08 ` Daniel Palmer
2020-11-29 11:08 ` [PATCH v4 5/5] ARM: mstar: Fill in GPIO controller properties for infinity Daniel Palmer
2020-11-29 11:08 ` Daniel Palmer
2020-12-05 21:42 ` [PATCH v4 0/5] Add GPIO support for MStar/SigmaStar ARMv7 Linus Walleij
2020-12-05 21:42 ` Linus Walleij
2020-12-05 21:42 ` Linus Walleij
2020-12-07 10:55 ` Daniel Palmer
2020-12-07 10:55 ` Daniel Palmer
2020-12-07 10:55 ` Daniel Palmer
2020-12-09 16:47 ` Arnd Bergmann
2020-12-09 16:47 ` Arnd Bergmann
2020-12-09 21:40 ` Arnd Bergmann
2020-12-09 21:40 ` Arnd Bergmann
2020-12-09 20:30 ` Arnd Bergmann
2020-12-09 20:30 ` Arnd Bergmann
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=20201129110803.2461700-1-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=devicetree@vger.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=robh@kernel.org \
--cc=soc@kernel.org \
--cc=w@1wt.eu \
/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