From: Kevin Hilman <khilman@baylibre.com>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: heiko@sntech.de, xf@rock-chips.com, wxt@rock-chips.com,
linux-arm-kernel@lists.infradead.org, huangtao@rock-chips.com,
zyw@rock-chips.com, xxx@rock-chips.com, jay.xu@rock-chips.com,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: modify document of Rockchip power domains
Date: Fri, 18 Mar 2016 09:18:51 -0700 [thread overview]
Message-ID: <7hshznsqs4.fsf@baylibre.com> (raw)
In-Reply-To: <1458285444-31129-2-git-send-email-zhangqing@rock-chips.com> (Elaine Zhang's message of "Fri, 18 Mar 2016 15:17:23 +0800")
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.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/2] dt-bindings: modify document of Rockchip power domains
Date: Fri, 18 Mar 2016 09:18:51 -0700 [thread overview]
Message-ID: <7hshznsqs4.fsf@baylibre.com> (raw)
In-Reply-To: <1458285444-31129-2-git-send-email-zhangqing@rock-chips.com> (Elaine Zhang's message of "Fri, 18 Mar 2016 15:17:23 +0800")
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.
Kevin
next prev parent reply other threads:[~2016-03-18 16:18 UTC|newest]
Thread overview: 23+ 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 ` Elaine Zhang
2016-03-18 7:17 ` [PATCH v1 1/2] dt-bindings: modify document of Rockchip power domains Elaine Zhang
2016-03-18 7:17 ` Elaine Zhang
2016-03-18 16:18 ` Kevin Hilman [this message]
2016-03-18 16:18 ` Kevin Hilman
2016-03-18 22:16 ` Heiko Stuebner
2016-03-18 22:16 ` Heiko Stuebner
2016-04-12 2:00 ` Heiko Stuebner
2016-04-12 2:00 ` Heiko Stuebner
2016-03-18 7:17 ` [PATCH v1 2/2] rockchip: power-domain: support qos save and restore Elaine Zhang
2016-03-18 7:17 ` Elaine Zhang
2016-03-31 16:31 ` Heiko Stuebner
2016-03-31 16:31 ` Heiko Stuebner
2016-04-01 2:33 ` Elaine Zhang
2016-04-01 2:33 ` Elaine Zhang
2016-04-01 16:19 ` Heiko Stuebner
2016-04-01 16:19 ` Heiko Stuebner
2016-04-05 1:57 ` Elaine Zhang
2016-04-05 1:57 ` Elaine Zhang
2016-04-05 1:57 ` Elaine Zhang
2016-04-05 17:26 ` Heiko Stuebner
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=7hshznsqs4.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=wxt@rock-chips.com \
--cc=xf@rock-chips.com \
--cc=xxx@rock-chips.com \
--cc=zhangqing@rock-chips.com \
--cc=zyw@rock-chips.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.