From: Kevin Hilman <khilman@kernel.org> To: Caesar Wang <wxt@rock-chips.com> Cc: heiko@sntech.de, ulf.hansson@linaro.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, dianders@chromium.org, tomasz.figa@gmail.com, dmitry.torokhov@gmail.com, linux-kernel@vger.kernel.org, galak@codeaurora.org, linux@arm.linux.org.uk, robh+dt@kernel.org, arnd@arndb.de, linus.walleij@linaro.org, ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org, "jinkun.hong" <jinkun.hong@rock-chips.com> Subject: Re: [RESEND PATCH v16 4/4] ARM: dts: add the support power-domain node on RK3288 SoCs Date: Tue, 25 Aug 2015 14:07:04 -0700 [thread overview] Message-ID: <7hfv37axhj.fsf@deeprootsystems.com> (raw) In-Reply-To: <1440487486-6154-5-git-send-email-wxt@rock-chips.com> (Caesar Wang's message of "Tue, 25 Aug 2015 15:24:46 +0800") Caesar Wang <wxt@rock-chips.com> writes: > We can add more domains node in the future. > This patch add the needed clocks into power-controller. > As the discuess about all the device clocks being listed in > the power-domains itself. > > There are several reasons as follows: > > Firstly, the clocks need be turned off to save power when > the system enter the suspend state. So we need to enumerate > the clocks in the dts. In order to power domain can turn on and off. Yes, but this is the job of device drivers which are runtime PM adapted to gate their own clocks. I agree these clocks need to be enumerated in the DTS, but they should be in the device nodes. > Secondly, the reset-circuit should reset be synchronous on RK3288, > then sync revoked. So we need to enable clocks of all devices. > In other words, we have to enable the clocks before you operate them > if all the device clocks are included in someone domians. Yes, this is pretty common for reset. > Someone wish was to get the clocks by reading the clocks from the > device nodes, We can do that but we can solve the above issues. I don't follow this sentence. Are you saying doing that will not solve the above issues? Why not? Please explain. If there are non-device clocks that also need to be enabled before asserting reset, then those are candidates for the power-domain node, but not device clocks. > Anyway, the best ideas we can fix it in the future SoCs. I don't think this is an SoC design issue as this is needed when you have synchronous reset. My concern is primarily around how to describe this in the DT. Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@kernel.org (Kevin Hilman) To: linux-arm-kernel@lists.infradead.org Subject: [RESEND PATCH v16 4/4] ARM: dts: add the support power-domain node on RK3288 SoCs Date: Tue, 25 Aug 2015 14:07:04 -0700 [thread overview] Message-ID: <7hfv37axhj.fsf@deeprootsystems.com> (raw) In-Reply-To: <1440487486-6154-5-git-send-email-wxt@rock-chips.com> (Caesar Wang's message of "Tue, 25 Aug 2015 15:24:46 +0800") Caesar Wang <wxt@rock-chips.com> writes: > We can add more domains node in the future. > This patch add the needed clocks into power-controller. > As the discuess about all the device clocks being listed in > the power-domains itself. > > There are several reasons as follows: > > Firstly, the clocks need be turned off to save power when > the system enter the suspend state. So we need to enumerate > the clocks in the dts. In order to power domain can turn on and off. Yes, but this is the job of device drivers which are runtime PM adapted to gate their own clocks. I agree these clocks need to be enumerated in the DTS, but they should be in the device nodes. > Secondly, the reset-circuit should reset be synchronous on RK3288, > then sync revoked. So we need to enable clocks of all devices. > In other words, we have to enable the clocks before you operate them > if all the device clocks are included in someone domians. Yes, this is pretty common for reset. > Someone wish was to get the clocks by reading the clocks from the > device nodes, We can do that but we can solve the above issues. I don't follow this sentence. Are you saying doing that will not solve the above issues? Why not? Please explain. If there are non-device clocks that also need to be enabled before asserting reset, then those are candidates for the power-domain node, but not device clocks. > Anyway, the best ideas we can fix it in the future SoCs. I don't think this is an SoC design issue as this is needed when you have synchronous reset. My concern is primarily around how to describe this in the DT. Kevin
next prev parent reply other threads:[~2015-08-25 21:07 UTC|newest] Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-25 7:24 [RESEND PATCH v16 0/4] ARM: rk3288: Add PM Domain support Caesar Wang 2015-08-25 7:24 ` Caesar Wang 2015-08-25 7:24 ` Caesar Wang 2015-08-25 7:24 ` [RESEND PATCH v16 1/4] dt-bindings: add document of Rockchip power domain Caesar Wang 2015-08-25 7:24 ` Caesar Wang 2015-08-25 7:24 ` Caesar Wang 2015-08-25 7:24 ` [RESEND PATCH v16 2/4] ARM: power-domain: rockchip: add all the domain type on RK3288 SoCs Caesar Wang 2015-08-25 7:24 ` Caesar Wang 2015-08-25 7:24 ` Caesar Wang 2015-08-25 7:24 ` [RESEND PATCH v16 3/4] soc: rockchip: power-domain: Add power domain driver Caesar Wang 2015-08-25 7:24 ` Caesar Wang 2015-08-25 7:24 ` Caesar Wang 2015-08-25 20:57 ` Kevin Hilman 2015-08-25 20:57 ` Kevin Hilman 2015-08-25 20:57 ` Kevin Hilman 2015-08-26 9:27 ` Caesar Wang 2015-08-26 9:27 ` Caesar Wang 2015-08-25 7:24 ` [RESEND PATCH v16 4/4] ARM: dts: add the support power-domain node on RK3288 SoCs Caesar Wang 2015-08-25 7:24 ` Caesar Wang 2015-08-25 7:24 ` Caesar Wang 2015-08-25 21:07 ` Kevin Hilman [this message] 2015-08-25 21:07 ` Kevin Hilman 2015-08-25 21:48 ` Doug Anderson 2015-08-25 21:48 ` Doug Anderson 2015-08-25 21:48 ` Doug Anderson 2015-08-25 22:45 ` Kevin Hilman 2015-08-25 22:45 ` Kevin Hilman 2015-08-25 22:45 ` Kevin Hilman 2015-08-25 23:47 ` Dmitry Torokhov 2015-08-25 23:47 ` Dmitry Torokhov 2015-08-25 23:47 ` Dmitry Torokhov 2015-08-28 0:24 ` Kevin Hilman 2015-08-28 0:24 ` Kevin Hilman 2015-08-28 0:24 ` Kevin Hilman 2015-08-28 2:03 ` Doug Anderson 2015-08-28 2:03 ` Doug Anderson 2015-08-28 20:02 ` Michael Turquette 2015-08-28 20:02 ` Michael Turquette 2015-08-28 20:02 ` Michael Turquette 2015-08-28 21:08 ` Doug Anderson 2015-08-28 21:08 ` Doug Anderson 2015-08-28 22:53 ` Michael Turquette 2015-08-28 22:53 ` Michael Turquette 2015-08-28 22:53 ` Michael Turquette 2015-08-28 21:28 ` Kevin Hilman 2015-08-28 21:28 ` Kevin Hilman 2015-08-25 23:55 ` Doug Anderson 2015-08-25 23:55 ` Doug Anderson 2015-08-25 23:55 ` Doug Anderson 2015-08-26 9:24 ` Caesar Wang 2015-08-26 9:24 ` Caesar Wang
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=7hfv37axhj.fsf@deeprootsystems.com \ --to=khilman@kernel.org \ --cc=arnd@arndb.de \ --cc=devicetree@vger.kernel.org \ --cc=dianders@chromium.org \ --cc=dmitry.torokhov@gmail.com \ --cc=galak@codeaurora.org \ --cc=heiko@sntech.de \ --cc=ijc+devicetree@hellion.org.uk \ --cc=jinkun.hong@rock-chips.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=linux@arm.linux.org.uk \ --cc=robh+dt@kernel.org \ --cc=tomasz.figa@gmail.com \ --cc=ulf.hansson@linaro.org \ --cc=wxt@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: linkBe 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.