From: andy.yan@rock-chips.com (Andy Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Use macros to describe gpios on rockchip platform
Date: Sat, 22 Oct 2016 20:51:46 +0800 [thread overview]
Message-ID: <1477140706-6886-1-git-send-email-andy.yan@rock-chips.com> (raw)
As patch 150696e2e3a4("Add GPIO pin index definition for rockchip pinctrl") has
been applied, now we can use these macros to describe the corresponding gpio
ranther than hard code numbers, this will make the dts easier to read and
write.
Some ideas from Krzysztof's patch on EXYNOS[0].
[0]https://lkml.org/lkml/2016/9/4/71
Andy Yan (2):
ARM: dts: rockchip: use pin constants to describe gpios
ARM64: dts: rockchip: use pin constants to describe gpios
arch/arm/boot/dts/rk3036-evb.dts | 2 +-
arch/arm/boot/dts/rk3036-kylin.dts | 10 ++++-----
arch/arm/boot/dts/rk3066a-bqcurie2.dts | 6 +++---
arch/arm/boot/dts/rk3066a-marsboard.dts | 2 +-
arch/arm/boot/dts/rk3066a-mk808.dts | 10 ++++-----
arch/arm/boot/dts/rk3066a-rayeager.dts | 12 +++++------
arch/arm/boot/dts/rk3188-px3-evb.dts | 4 ++--
arch/arm/boot/dts/rk3188-radxarock.dts | 16 +++++++--------
arch/arm/boot/dts/rk3229-evb.dts | 2 +-
arch/arm/boot/dts/rk3288-evb-act8846.dts | 4 ++--
arch/arm/boot/dts/rk3288-evb.dtsi | 14 ++++++-------
arch/arm/boot/dts/rk3288-fennec.dts | 4 ++--
arch/arm/boot/dts/rk3288-firefly-beta.dts | 2 +-
arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi | 2 +-
arch/arm/boot/dts/rk3288-firefly-reload.dts | 24 +++++++++++-----------
arch/arm/boot/dts/rk3288-firefly.dts | 2 +-
arch/arm/boot/dts/rk3288-firefly.dtsi | 16 +++++++--------
arch/arm/boot/dts/rk3288-miqi.dts | 8 ++++----
arch/arm/boot/dts/rk3288-popmetal.dts | 2 +-
arch/arm/boot/dts/rk3288-r89.dts | 12 +++++------
arch/arm/boot/dts/rk3288-rock2-som.dtsi | 4 ++--
arch/arm/boot/dts/rk3288-rock2-square.dts | 12 +++++------
arch/arm/boot/dts/rk3288-veyron-analog-audio.dtsi | 4 ++--
arch/arm/boot/dts/rk3288-veyron-brain.dts | 8 ++++----
arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi | 10 ++++-----
arch/arm/boot/dts/rk3288-veyron-jaq.dts | 14 ++++++-------
arch/arm/boot/dts/rk3288-veyron-jerry.dts | 10 ++++-----
arch/arm/boot/dts/rk3288-veyron-mickey.dts | 6 +++---
arch/arm/boot/dts/rk3288-veyron-minnie.dts | 16 +++++++--------
arch/arm/boot/dts/rk3288-veyron-pinky.dts | 4 ++--
arch/arm/boot/dts/rk3288-veyron-sdmmc.dtsi | 2 +-
arch/arm/boot/dts/rk3288-veyron-speedy.dts | 10 ++++-----
arch/arm/boot/dts/rk3288-veyron.dtsi | 8 ++++----
arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi | 10 ++++-----
arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts | 8 ++++----
.../boot/dts/rockchip/rk3368-orion-r68-meta.dts | 14 ++++++-------
arch/arm64/boot/dts/rockchip/rk3368-px5-evb.dts | 4 ++--
arch/arm64/boot/dts/rockchip/rk3368-r88.dts | 16 +++++++--------
arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 6 +++---
39 files changed, 160 insertions(+), 160 deletions(-)
--
2.7.4
next reply other threads:[~2016-10-22 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 12:51 Andy Yan [this message]
2016-10-22 12:54 ` [PATCH 1/2] ARM: dts: rockchip: use pin constants to describe gpios Andy Yan
2016-10-22 12:59 ` [PATCH 2/2] ARM64: " Andy Yan
2016-12-30 12:31 ` [PATCH 0/2] Use macros to describe gpios on rockchip platform Heiko Stuebner
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=1477140706-6886-1-git-send-email-andy.yan@rock-chips.com \
--to=andy.yan@rock-chips.com \
--cc=linux-arm-kernel@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