From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/2] dt-bindings: modify document of Rockchip power domains
Date: Tue, 12 Apr 2016 04:00:10 +0200 [thread overview]
Message-ID: <1560475.Omi7ovI7oB@phil> (raw)
In-Reply-To: <21140203.EjVS0MZtuq@phil>
Hi Kevin,
Am Freitag, 18. M?rz 2016, 23:16:55 schrieb Heiko Stuebner:
> Am Freitag, 18. M?rz 2016, 09:18:51 schrieb Kevin Hilman:
> > Elaine Zhang <zhangqing@rock-chips.com> writes:
> > > Add qos example for power domain which found on Rockchip SoCs.
> > > These qos register description in TRMs
> > > (rk3036, rk3228, rk3288, rk3366, rk3368, rk3399) looks the same.
> >
> > This should describe in more detail what "qos" is in this context. At
> > first glance, it's just a range of registers that lose context that need
> > to be saved/restored.
>
> I guess that should be something like
>
> ---- 8< ----
> Rockchip SoCs contain quality of service (qos) blocks managing priority,
> bandwidth, etc of the connection of each domain to the interconnect.
> These blocks loose state when their domain gets disabled and therefore
> need to be saved when disabling and restored when enabling a power-domain.
>
> These qos blocks also are similar over all currently available Rockchip
> SoCs.
> ---- 8< ----
does this look sane to you in terms of description, or do we need something
more?
Heiko
next prev parent reply other threads:[~2016-04-12 2:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 7:17 [PATCH v1 0/2] rockchip: power-domain: support qos save and restore Elaine Zhang
2016-03-18 7:17 ` [PATCH v1 1/2] dt-bindings: modify document of Rockchip power domains Elaine Zhang
2016-03-18 16:18 ` Kevin Hilman
2016-03-18 22:16 ` Heiko Stuebner
2016-04-12 2:00 ` Heiko Stuebner [this message]
2016-03-18 7:17 ` [PATCH v1 2/2] rockchip: power-domain: support qos save and restore Elaine Zhang
2016-03-31 16:31 ` Heiko Stuebner
2016-04-01 2:33 ` Elaine Zhang
2016-04-01 16:19 ` Heiko Stuebner
2016-04-05 1:57 ` Elaine Zhang
2016-04-05 17:26 ` 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=1560475.Omi7ovI7oB@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).