From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/4] arm64: dts: rockchip: add GRF GPIO controller to rk3328
Date: Sat, 04 Aug 2018 15:16:01 +0200 [thread overview]
Message-ID: <4016409.aba6YNvtTb@phil> (raw)
In-Reply-To: <1533016762-5268-3-git-send-email-djw@t-chip.com.cn>
Hi Levin,
Am Dienstag, 31. Juli 2018, 07:59:20 CEST schrieb djw at t-chip.com.cn:
> From: Levin Du <djw@t-chip.com.cn>
>
> Adding a GRF GPIO controller labled "grf_gpio" to rk3328, currently
> providing access to the GPIO_MUTE pin, which is manupulated by the
> GRF_SOC_CON10 register.
>
> The GPIO_MUTE pin is referred to as <&grf_gpio 0>.
>
> Signed-off-by: Levin Du <djw@t-chip.com.cn>
applied to my dts64 branch, with 2 changes:
- reordered, please sort nodes without address alphabetically
- removed default disabled status
The controlled pin is always present on the soc, so doesn't need
to be enabled on a per-board level
Heiko
next prev parent reply other threads:[~2018-08-04 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 5:59 [PATCH v4 0/4] Add sdmmc UHS support to ROC-RK3328-CC board djw at t-chip.com.cn
2018-07-31 5:59 ` [PATCH v4 1/4] gpio: syscon: rockchip: add GRF GPIO support for rk3328 djw at t-chip.com.cn
2018-07-31 19:36 ` Rob Herring
2018-08-01 11:46 ` Heiko Stuebner
2018-08-03 17:13 ` Linus Walleij
2018-07-31 5:59 ` [PATCH v4 2/4] arm64: dts: rockchip: add GRF GPIO controller to rk3328 djw at t-chip.com.cn
2018-08-04 13:16 ` Heiko Stuebner [this message]
2018-07-31 5:59 ` [PATCH v4 3/4] arm64: dts: rockchip: add io-domain to roc-rk3328-cc djw at t-chip.com.cn
2018-08-02 12:54 ` Heiko Stuebner
2018-07-31 5:59 ` [PATCH v4 4/4] arm64: dts: rockchip: add sdmmc UHS support for roc-rk3328-cc djw at t-chip.com.cn
2018-08-04 13:18 ` 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=4016409.aba6YNvtTb@phil \
--to=heiko@sntech.de \
--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;
as well as URLs for NNTP newsgroup(s).