From: Daniel Lezcano <daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Caesar Wang <wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Cc: huangtao-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>,
Xing Zheng <zhengxing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
Masahiro Yamada
<yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
Shawn Lin <shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
Brian Norris
<briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
smbarber-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
cf-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
briannorris-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Jianqun Xu <jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v2 0/4] clocksource: rockchip/timer: Support rktimer for rk3399
Date: Mon, 13 Jun 2016 15:06:25 +0200 [thread overview]
Message-ID: <20160613130625.GC10634@linaro.org> (raw)
In-Reply-To: <1465275273-22076-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
On Tue, Jun 07, 2016 at 12:54:29PM +0800, Caesar Wang wrote:
> This series patches had been tested on rockchip inside kernel.
> In order to support the rk3399 SoC timer and turn off interrupts and IPIs to
> save power in idle.
For my personnal information, are the arch_timer in the same power domain
than the CPU ? IOW, what is the 'always-on' property in the DT ?
> Okay, it still works bootup on rk3288/other SoCs, even though many socs
> hasn't used
> the broadcast timer.
Yes, unfortunately the SoC design on rk3288 and the previous ones do not
allow to use a cpuidle driver with cpu/cluster power down, so obviously the
broadcast timer is pointless on these boards :)
> History version:
> v1:
> https://lkml.org/lkml/2016/5/25/186
>
> Easy to test for my borad.
> localhost / # cat /proc/interrupts
> CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
> 1: 0 0 0 0 0 0 GICv3 29 Edge arch_timer
> ...
> 5: 0 0 0 0 0 0 GICv3 113 Level rk_timer
> ..
>
> localhost / # cat /proc/timer_list | grep event_handler
> get "event_handler: hrtimer_interrupt"
> event_handler: tick_handle_oneshot_broadcast
> event_handler: hrtimer_interrupt
What are you trying to demonstrate here ? There are no interrupts for both
arch_timer and rk_timer.
> That should work for my board.
What do you mean ?
WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] clocksource: rockchip/timer: Support rktimer for rk3399
Date: Mon, 13 Jun 2016 15:06:25 +0200 [thread overview]
Message-ID: <20160613130625.GC10634@linaro.org> (raw)
In-Reply-To: <1465275273-22076-1-git-send-email-wxt@rock-chips.com>
On Tue, Jun 07, 2016 at 12:54:29PM +0800, Caesar Wang wrote:
> This series patches had been tested on rockchip inside kernel.
> In order to support the rk3399 SoC timer and turn off interrupts and IPIs to
> save power in idle.
For my personnal information, are the arch_timer in the same power domain
than the CPU ? IOW, what is the 'always-on' property in the DT ?
> Okay, it still works bootup on rk3288/other SoCs, even though many socs
> hasn't used
> the broadcast timer.
Yes, unfortunately the SoC design on rk3288 and the previous ones do not
allow to use a cpuidle driver with cpu/cluster power down, so obviously the
broadcast timer is pointless on these boards :)
> History version:
> v1:
> https://lkml.org/lkml/2016/5/25/186
>
> Easy to test for my borad.
> localhost / # cat /proc/interrupts
> CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
> 1: 0 0 0 0 0 0 GICv3 29 Edge arch_timer
> ...
> 5: 0 0 0 0 0 0 GICv3 113 Level rk_timer
> ..
>
> localhost / # cat /proc/timer_list | grep event_handler
> get "event_handler: hrtimer_interrupt"
> event_handler: tick_handle_oneshot_broadcast
> event_handler: hrtimer_interrupt
What are you trying to demonstrate here ? There are no interrupts for both
arch_timer and rk_timer.
> That should work for my board.
What do you mean ?
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Caesar Wang <wxt@rock-chips.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
dianders@chromium.org, briannorris@google.com,
smbarber@google.com, linux-rockchip@lists.infradead.org,
Thomas Gleixner <tglx@linutronix.de>,
cf@rock-chips.com, huangtao@rock-chips.com,
devicetree@vger.kernel.org, Xing Zheng <zhengxing@rock-chips.com>,
Jianqun Xu <jay.xu@rock-chips.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Brian Norris <briannorris@chromium.org>,
linux-kernel@vger.kernel.org,
Shawn Lin <shawn.lin@rock-chips.com>,
Rob Herring <robh+dt@kernel.org>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] clocksource: rockchip/timer: Support rktimer for rk3399
Date: Mon, 13 Jun 2016 15:06:25 +0200 [thread overview]
Message-ID: <20160613130625.GC10634@linaro.org> (raw)
In-Reply-To: <1465275273-22076-1-git-send-email-wxt@rock-chips.com>
On Tue, Jun 07, 2016 at 12:54:29PM +0800, Caesar Wang wrote:
> This series patches had been tested on rockchip inside kernel.
> In order to support the rk3399 SoC timer and turn off interrupts and IPIs to
> save power in idle.
For my personnal information, are the arch_timer in the same power domain
than the CPU ? IOW, what is the 'always-on' property in the DT ?
> Okay, it still works bootup on rk3288/other SoCs, even though many socs
> hasn't used
> the broadcast timer.
Yes, unfortunately the SoC design on rk3288 and the previous ones do not
allow to use a cpuidle driver with cpu/cluster power down, so obviously the
broadcast timer is pointless on these boards :)
> History version:
> v1:
> https://lkml.org/lkml/2016/5/25/186
>
> Easy to test for my borad.
> localhost / # cat /proc/interrupts
> CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
> 1: 0 0 0 0 0 0 GICv3 29 Edge arch_timer
> ...
> 5: 0 0 0 0 0 0 GICv3 113 Level rk_timer
> ..
>
> localhost / # cat /proc/timer_list | grep event_handler
> get "event_handler: hrtimer_interrupt"
> event_handler: tick_handle_oneshot_broadcast
> event_handler: hrtimer_interrupt
What are you trying to demonstrate here ? There are no interrupts for both
arch_timer and rk_timer.
> That should work for my board.
What do you mean ?
next prev parent reply other threads:[~2016-06-13 13:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 4:54 [PATCH v2 0/4] clocksource: rockchip/timer: Support rktimer for rk3399 Caesar Wang
2016-06-07 4:54 ` Caesar Wang
2016-06-07 4:54 ` [PATCH v2 1/4] dt-bindings: document rk3399 rk-timer bindings Caesar Wang
2016-06-07 4:54 ` Caesar Wang
2016-06-07 4:54 ` [PATCH v2 2/4] clocksource: rockchip: add dynamic irq flag to the timer Caesar Wang
2016-06-07 4:54 ` Caesar Wang
2016-06-07 4:54 ` [PATCH v2 3/4] clocksource: rockchip: add support for rk3399 SoC Caesar Wang
2016-06-07 4:54 ` Caesar Wang
2016-06-07 4:54 ` [PATCH v2 4/4] arm64: dts: rockchip: add rktimer device node for rk3399 Caesar Wang
2016-06-07 4:54 ` Caesar Wang
[not found] ` <1465275273-22076-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-13 13:06 ` Daniel Lezcano [this message]
2016-06-13 13:06 ` [PATCH v2 0/4] clocksource: rockchip/timer: Support rktimer " Daniel Lezcano
2016-06-13 13:06 ` Daniel Lezcano
2016-06-14 4:00 ` Huang, Tao
2016-06-14 4:00 ` Huang, Tao
2016-06-14 9:12 ` Caesar Wang
2016-06-14 9:12 ` Caesar Wang
2016-06-16 14:26 ` Daniel Lezcano
2016-06-16 14:26 ` Daniel Lezcano
2016-06-17 1:08 ` Caesar Wang
2016-06-17 1:08 ` 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=20160613130625.GC10634@linaro.org \
--to=daniel.lezcano-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=briannorris-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=cf-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=huangtao-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=smbarber-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.org \
--cc=wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org \
--cc=zhengxing-TNX95d0MmH7DzftRWevZcw@public.gmane.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 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.