From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: myungjoo.ham@samsung.com, kyungmin.park@samsung.com,
k.kozlowski@samsung.com, tomasz.figa@gmail.com,
s.nawrocki@samsung.com, kgene@kernel.org, robh@kernel.org,
rjw@rjwysocki.net, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, linux@arm.linux.org.uk,
linux.amoon@gmail.com, m.reichl@fivetechno.de,
tjakobi@math.uni-bielefeld.de, inki.dae@samsung.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/8] PM / devfreq: Add NoCP devfreq-event and support busfreq on exyno5422-odroidxu3
Date: Tue, 3 May 2016 12:29:22 +0200 [thread overview]
Message-ID: <20160503102922.GD3956@kozik-lap> (raw)
In-Reply-To: <1460701975-24178-1-git-send-email-cw00.choi@samsung.com>
On Fri, Apr 15, 2016 at 03:32:47PM +0900, Chanwoo Choi wrote:
> This patchset support the AMBA bus frequency scaling on Exynos5422-based
> Odroid-XU3 board. But, this series only support the bus frequency scaling
> for INT (Internal) block using VDD_INT power line.
>
> Also, to support the bus frequency scaling for Exynos542x SoC,
> Exynos542x SoC has the specific 'NoC (Network on Chip) Probe' device
> to measure the transfered data traffic on NoC (Network on Chip)
> instead of PPMU (Platform Performance Monitoring Unit). NoC Probe device
> provide the utilization for INT block of Exynos542x SoC.
>
> The generic exynos-bus frequency driver uses the 'NoC Probe' devfreq-event
> device (drivers/devfreq/event/exynos-nocp.c) without any modification.
> Just add the phandle of 'NoC Probe' dt node to bus dt node.
>
> Depend on:
> This patchset depends on patch[1] which support the generic exynos-bus
> frequency driver.
> [1] http://www.spinics.net/lists/arm-kernel/msg495976.html
> - [PATCH v9 00/20] PM / devferq: Add generic exynos bus frequency driver and new passive governor
>
>
> Changse from v1:
> (https://lkml.org/lkml/2016/4/8/28)
> - Simplify the documentation of exynos-nocp.txt
> - Check the return value of regmap function
> - Modify Device Tree node name using general device name
> : nocp_memX_X@ nocp_memX_X -> nocp_memX_X@ nocp
> - Fix wrong node name about nocp device tree node
> - Drop the CLK_SET_RATE_PARENT flag
> - Reorder bus device tree node alpabetically
> - Add the tested-by tag from Anand Moon and Markus Reichl
> - Add the reviewed-by tag to patch5/7 from Exynos SoC Maintainer
> - Add patch2 to modify the devfreq_event_get_edev_by_phandle()
> to get the instance of devfreq-event device by using the phandle
>
> Chanwoo Choi (8):
> PM / devfreq: event: Add new Exynos NoC probe driver
> PM / devfreq: event: Find the instance of devfreq-event device by using phandle
> PM / devfreq: exynos: Add the detailed correlation for Exynos5422 bus
> ARM: dts: Add NoC Probe dt node for Exynos542x SoC
> dt-bindings: clock: Add the clock id for ACLK clock of Exynos542x SoC
> clk: samsung: exynos542x: Add the clock id for ACLK
> ARM: dts: Add bus nodes using VDD_INT for Exynos542x SoC
> ARM: dts: Add support of Bus frequency using VDD_INT for exynos5422-odroidxu3
Applied DTS patches for late v4.7 (hopefully).
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-05-03 10:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 6:32 [PATCH v2 0/8] PM / devfreq: Add NoCP devfreq-event and support busfreq on exyno5422-odroidxu3 Chanwoo Choi
2016-04-15 6:32 ` [PATCH v2 1/8] PM / devfreq: event: Add new Exynos NoC probe driver Chanwoo Choi
2016-04-15 8:37 ` Krzysztof Kozlowski
2016-04-15 6:32 ` [PATCH v2 2/8] PM / devfreq: event: Find the instance of devfreq-event device by using phandle Chanwoo Choi
2016-04-15 6:32 ` [PATCH v2 3/8] PM / devfreq: exynos: Add the detailed correlation for Exynos5422 bus Chanwoo Choi
2016-04-15 6:32 ` [PATCH v2 4/8] ARM: dts: Add NoC Probe dt node for Exynos542x SoC Chanwoo Choi
2016-04-15 9:04 ` Krzysztof Kozlowski
2016-04-15 6:32 ` [PATCH v2 5/8] dt-bindings: clock: Add the clock id for ACLK clock of " Chanwoo Choi
2016-04-15 6:32 ` [PATCH v2 6/8] clk: samsung: exynos542x: Add the clock id for ACLK Chanwoo Choi
2016-04-15 9:05 ` Krzysztof Kozlowski
2016-04-15 16:34 ` Sylwester Nawrocki
2016-04-15 6:32 ` [PATCH v2 7/8] ARM: dts: Add bus nodes using VDD_INT for Exynos542x SoC Chanwoo Choi
2016-04-15 6:32 ` [PATCH v2 8/8] ARM: dts: Add support of Bus frequency using VDD_INT for exynos5422-odroidxu3 Chanwoo Choi
2016-04-15 9:07 ` Krzysztof Kozlowski
2016-05-03 10:29 ` Krzysztof Kozlowski [this message]
2016-05-03 10:48 ` [PATCH v2 0/8] PM / devfreq: Add NoCP devfreq-event and support busfreq on exyno5422-odroidxu3 Chanwoo Choi
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=20160503102922.GD3956@kozik-lap \
--to=k.kozlowski@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=inki.dae@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=linux@arm.linux.org.uk \
--cc=m.reichl@fivetechno.de \
--cc=mark.rutland@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=pawel.moll@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=tjakobi@math.uni-bielefeld.de \
--cc=tomasz.figa@gmail.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