From: Heiko Stuebner <heiko@sntech.de>
To: rjw@rjwysocki.net
Cc: khilman@kernel.org, linux-pm@vger.kernel.org,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 4/5] arm64: dts: rockchip: make rk3368 grf syscons simple-mfds as well
Date: Sat, 21 May 2016 15:55:06 +0200 [thread overview]
Message-ID: <2597247.kfueRAYi3v@phil> (raw)
In-Reply-To: <1459432126-6395-5-git-send-email-heiko@sntech.de>
Am Donnerstag, 31. März 2016, 15:48:45 schrieb Heiko Stuebner:
> The general register files do contain a lot of separate functions and
> while some really are only registers with a lot of different 1-bit
> settings, there are also a lot of them containing some bigger function
> blocks. To be able to define these as sub-devices, make them simple-mfds.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> Tested-by: David Wu <david.wu@rock-chips.com>
applied for 4.8
next prev parent reply other threads:[~2016-05-21 13:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 13:48 [PATCH v2 0/5] ARM: rockchip: move io-domains under GRF Heiko Stuebner
2016-03-31 13:48 ` [PATCH v2 1/5] PM / AVS: rockchip-io: make io-domains a child of the GRF Heiko Stuebner
2016-04-12 2:23 ` Heiko Stuebner
2016-04-13 4:55 ` Rafael J. Wysocki
2016-04-26 16:25 ` Heiko Stübner
2016-04-26 17:13 ` Rafael J. Wysocki
2016-03-31 13:48 ` [PATCH v2 2/5] ARM: dts: rockchip: make rk3288-grf a simple-mfd Heiko Stuebner
2016-04-15 21:21 ` Heiko Stübner
2016-03-31 13:48 ` [PATCH v2 3/5] ARM: dts: rockchip: move rk3288 io-domain nodes to the grf Heiko Stuebner
2016-05-21 13:40 ` Heiko Stuebner
2016-03-31 13:48 ` [PATCH v2 4/5] arm64: dts: rockchip: make rk3368 grf syscons simple-mfds as well Heiko Stuebner
2016-05-21 13:55 ` Heiko Stuebner [this message]
2016-03-31 13:48 ` [PATCH v2 5/5] arm64: dts: rockchip: add rk3368-r88 iodomains Heiko Stuebner
2016-04-03 3:45 ` kbuild test robot
2016-05-21 16:52 ` 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=2597247.kfueRAYi3v@phil \
--to=heiko@sntech.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=rjw@rjwysocki.net \
/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).