linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Caesar Wang <caesar.upstream@gmail.com>
To: Mark Rutland <mark.rutland@arm.com>, Heiko Stuebner <heiko@sntech.de>
Cc: Caesar Wang <wxt@rock-chips.com>,
	Will Deacon <will.deacon@arm.com>,
	Marc Zyngier <marc.zyngier@arm.com>,
	huangtao@rock-chips.com, devicetree@vger.kernel.org,
	Xing Zheng <zhengxing@rock-chips.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Brian Norris <briannorris@chromium.org>,
	dianders@chromium.org, linux-kernel@vger.kernel.org,
	linux-rockchip@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	David Wu <david.wu@rock-chips.com>,
	cf@rock-chips.com, Jianqun Xu <jay.xu@rock-chips.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] arm64: dts: rockchip: Support PMU for rk3399 SoCs
Date: Thu, 14 Jul 2016 09:14:57 +0800	[thread overview]
Message-ID: <5786E791.1010906@gmail.com> (raw)
In-Reply-To: <20160706112444.GB14657@leverpostej>

Hi,

On 2016年07月06日 19:24, Mark Rutland wrote:
> On Wed, Jul 06, 2016 at 04:05:55PM +0800, Caesar Wang wrote:
>> Hello Heiko, Marc & ARM guys
> Hi,
>
> These patches themselves look fine, so FWIW:
>
> Acked-by: Mark Rutland <mark.rutland@arm.com>

Thanks your ack.

>
> The prerequisite patch from Marc [1] also largely looks fine, but there
> are some minor details to sort out [2], so at this point in time I'm
> guesssing this is all v4.9 material.
>
> Thanks,
> Mark.
>
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-July/440647.html
> [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-July/441495.html

Okay, I saw the Marc's patch had been merged on next kernel.:-)


-Caesar
>
>> When Jay first submitted the rk3399.dtsi upstream
>> <https://patchwork.kernel.org/patch/8885821/> he had the PMU node in there,
>> but then took it out because the upstream binding wasn't done yet.
>> It looks as if the upstream stuff has landed, since in linux/master I see:
>> 287e9357abcc DT/arm,gic-v3: Documment PPI partition support
>> e3825ba1af3a irqchip/gic-v3: Add support for partitioned PPIs
>> 9e2c986cb460 irqchip: Add per-cpu interrupt partitioning library
>> 222df54fd8b7 genirq: Allow the affinity of a percpu interrupt to be set/retrieved
>> 651e8b54abde irqdomain: Allow domain matching on irq_fwspec
>>
>> This series patches add to support the rk3399 SoCs PMU.
>> I pick up the https://patchwork.kernel.org/patch/9209369/.
>>
>> As do some tests with ChromeOs for my rk3399 board.
>> Tested with linus master 4.7-rc6 kernel on rk3399 board.
>> https://github.com/Caesar-github/rockchip/tree/rk3399/pmu-upstream
>>
>> localhost / # perf list
>>
>> List of pre-defined events (to be used in -e):
>> cpu-cycles OR cycles [Hardware event]
>> instructions [Hardware event]
>> cache-references [Hardware event]
>> cache-misses [Hardware event]
>> branch-instructions OR branches [Hardware event]
>> branch-misses [Hardware event]
>> bus-cycles [Hardware event]
>> ...
>>
>> perf stat --cpu 0/1/2/3..... to minitor
>> e.g. cpu0;
>>
>> localhost / # perf stat --cpu 0
>>
>> Performance counter stats for 'CPU(s) 0':
>>
>> 3374.917571 task-clock (msec) # 1.001 CPUs utilized [100.00%]
>> 20 context-switches # 0.006 K/sec [100.00%]
>> 2 cpu-migrations # 0.001 K/sec [100.00%]
>> 55 page-faults # 0.016 K/sec
>> 7151843 cycles # 0.002 GHz [100.00%]
>> <not supported> stalled-cycles-frontend
>> <not supported> stalled-cycles-backend
>> 4272536 instructions # 0.60 insns per cycle [100.00%]
>> 568406 branches # 0.168 M/sec [100.00%]
>> 65652 branch-misses # 11.55% of all branches
>>
>> Also, 'perf top' to monitor the PMU interrupts from cpus
>>
>> -Caesar
>>
>>
>> Changes in v2:
>> - AS Mark comments on https://patchwork.kernel.org/patch/9209369/
>>    remove the interrupt-affinity property, we need depend on Marc' perf
>>    code on https://patchwork.kernel.org/patch/9209369/.
>>
>> Caesar Wang (2):
>>    arm64: dts: rockchip: change all interrupts cells for 4 on rk3399 SoCs
>>    arm64: dts: rockchip: support the pmu node for rk3399
>>
>>   arch/arm64/boot/dts/rockchip/rk3399.dtsi | 118 ++++++++++++++++++-------------
>>   1 file changed, 69 insertions(+), 49 deletions(-)
>>
>> -- 
>> 1.9.1
>>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2016-07-14  1:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  8:05 [PATCH v2 0/2] arm64: dts: rockchip: Support PMU for rk3399 SoCs Caesar Wang
2016-07-06  8:05 ` [PATCH v2 1/2] arm64: dts: rockchip: change all interrupts cells for 4 on " Caesar Wang
2016-07-06  8:05 ` [PATCH v2 2/2] arm64: dts: rockchip: support the pmu node for rk3399 Caesar Wang
2016-07-06 11:24 ` [PATCH v2 0/2] arm64: dts: rockchip: Support PMU for rk3399 SoCs Mark Rutland
2016-07-14  1:14   ` Caesar Wang [this message]
2016-09-03  0:13 ` Caesar Wang
2016-09-04 22:09   ` Heiko Stuebner
2016-09-04 22:47     ` 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=5786E791.1010906@gmail.com \
    --to=caesar.upstream@gmail.com \
    --cc=briannorris@chromium.org \
    --cc=catalin.marinas@arm.com \
    --cc=cf@rock-chips.com \
    --cc=david.wu@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --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=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=will.deacon@arm.com \
    --cc=wxt@rock-chips.com \
    --cc=yamada.masahiro@socionext.com \
    --cc=zhengxing@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 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).