From: Florian Eckert <fe@dev.tdt.de>
To: linus.walleij@linaro.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, andy.shevchenko@gmail.com, joe@perches.com,
chunkeey@gmail.com, piotr.krol@3mdeb.com, dvhart@infradead.org
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: [PATCH v3 0/2] Add device driver for APU2/APU3 GPIOs
Date: Wed, 14 Nov 2018 08:26:56 +0100 [thread overview]
Message-ID: <20181114072658.11457-1-fe@dev.tdt.de> (raw)
Changes v2:
- Update SPDX short identifier
- Remove gpio-keys-polled device moved to arch/x86/platform
- Fix styling
- Use spinnlock only there where it is useful
- Removed useless output on driver load
- Do bit manipulation later not on IO
- Add additional GPIOs handling mpci2_reset and mpcie3_reset.
- Add name to GPIOs exported via sysfs
Changes v3:
- Add a new platform device for the frontpanel push button.
- Get global variables from the heap
- Fix errors/warnings generated by ./scripts/checkpatch.pl
Until now it was not possible to get more information to detect the
MMIO_BASE address from the ACPI subsystem.
Florian Eckert (2):
gpio: Add driver for PC Engines APU2/APU3 GPIOs
kernel: Add reset button platform device for APU2/APU3
arch/x86/Kconfig | 14 ++
arch/x86/platform/Makefile | 1 +
arch/x86/platform/amd/Makefile | 1 +
arch/x86/platform/amd/apu.c | 72 ++++++++++
drivers/gpio/Kconfig | 8 ++
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-apu.c | 316 +++++++++++++++++++++++++++++++++++++++++
7 files changed, 413 insertions(+)
create mode 100644 arch/x86/platform/amd/Makefile
create mode 100644 arch/x86/platform/amd/apu.c
create mode 100644 drivers/gpio/gpio-apu.c
--
2.11.0
next reply other threads:[~2018-11-14 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 7:26 Florian Eckert [this message]
2018-11-14 7:26 ` [PATCH v3 1/2] gpio: Add driver for PC Engines APU2/APU3 GPIOs Florian Eckert
2018-11-14 8:53 ` Andy Shevchenko
2018-11-14 7:26 ` [PATCH v3 2/2] kernel: Add reset button platform device for APU2/APU3 Florian Eckert
2018-11-14 9:00 ` Andy Shevchenko
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=20181114072658.11457-1-fe@dev.tdt.de \
--to=fe@dev.tdt.de \
--cc=andy.shevchenko@gmail.com \
--cc=bp@alien8.de \
--cc=chunkeey@gmail.com \
--cc=dvhart@infradead.org \
--cc=joe@perches.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=piotr.krol@3mdeb.com \
--cc=tglx@linutronix.de \
/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).