From: Jianqun Xu <jay.xu@rock-chips.com>
To: heiko@sntech.de, linus.walleij@linaro.org,
andriy.shevchenko@linux.intel.com
Cc: brgl@bgdev.pl, linux-gpio@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Jianqun Xu <jay.xu@rock-chips.com>
Subject: [PATCH v5 0/6] gpio: rockchip: support acpi
Date: Fri, 9 Sep 2022 17:05:52 +0800 [thread overview]
Message-ID: <20220909090558.3609190-1-jay.xu@rock-chips.com> (raw)
This patch fix driver to support acpi.
Andy Shevchenko (1):
ACPI: utils: Add acpi_dev_uid_to_integer() helper to get _UID as
integer
Jianqun Xu (5):
ARM: dts: rockchip: add gpio alias for gpio dt nodes
ARM: dts: rockchip: add 'clock-names' for gpio dt nodes
arm64: dts: rockchip: add gpio alias for gpio dt nodes
arm64: dts: rockchip: add 'clock-names' for gpio dt nodes
gpio: rockchip: support acpi
arch/arm/boot/dts/rk3036.dtsi | 6 +
arch/arm/boot/dts/rk3066a.dtsi | 12 ++
arch/arm/boot/dts/rk3188.dtsi | 4 +
arch/arm/boot/dts/rk322x.dtsi | 8 +
arch/arm/boot/dts/rk3288.dtsi | 9 ++
arch/arm/boot/dts/rk3xxx.dtsi | 4 +
arch/arm64/boot/dts/rockchip/rk3308.dtsi | 10 ++
arch/arm64/boot/dts/rockchip/rk3328.dtsi | 8 +
arch/arm64/boot/dts/rockchip/rk3368.dtsi | 8 +
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 10 ++
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 5 +
drivers/acpi/utils.c | 24 +++
drivers/gpio/gpio-rockchip.c | 197 ++++++++++++++---------
include/acpi/acpi_bus.h | 1 +
include/linux/acpi.h | 5 +
15 files changed, 236 insertions(+), 75 deletions(-)
--
v5:
- add patches to add gpio alias and clock-names
- get clock by devm_clk_get()
- restore gpio range add comment
- other codingstyle
v4: suggested by Andy Shevchenko
- use dev_fwnode and to_of_node(fwnode) to replace dev->of_node
- split to a separate rockchip_gpio_get_clocks
- handle fail for clk_prepare_enable
- other codingstyle
v3: suggested by Andy Shevchenko
- fix irq size (32) to GPIO_MAX_PINS
- fix to use is_of_node or is_acpi_node
- use standard pattern for error handle
- remove redundant assignment
v2:
- fix rockchip_pin_output_deferred to rockchip_pin_deferred
2.25.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2022-09-09 9:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 9:05 Jianqun Xu [this message]
2022-09-09 9:05 ` [PATCH 1/6] ARM: dts: rockchip: add gpio alias for gpio dt nodes Jianqun Xu
2022-09-09 10:14 ` jay.xu
2022-09-10 21:09 ` kernel test robot
2022-09-09 9:05 ` [PATCH 2/6] ARM: dts: rockchip: add 'clock-names' " Jianqun Xu
2022-09-09 9:05 ` [PATCH 3/6] arm64: dts: rockchip: add gpio alias " Jianqun Xu
2022-09-09 9:05 ` [PATCH 4/6] arm64: dts: rockchip: add 'clock-names' " Jianqun Xu
2022-09-09 9:05 ` [PATCH 5/6] ACPI: utils: Add acpi_dev_uid_to_integer() helper to get _UID as integer Jianqun Xu
2022-09-09 9:05 ` [PATCH 6/6] gpio: rockchip: support acpi Jianqun Xu
2022-09-09 10:31 ` Andy Shevchenko
2022-09-13 1:07 ` jay.xu
2022-09-09 11:17 ` Johan Jonker
2022-09-13 1:12 ` jay.xu
2022-09-13 7:55 ` Johan Jonker
2022-09-13 1:14 ` jay.xu
2022-09-10 10:20 ` kernel test robot
2022-09-10 10:52 ` kernel test robot
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=20220909090558.3609190-1-jay.xu@rock-chips.com \
--to=jay.xu@rock-chips.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=heiko@sntech.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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).