Dear Myungjoo, On 2016년 05월 02일 14:48, MyungJoo Ham wrote: > Sender : 최찬우<cw00.choi@xxxxxxxxxxx> S5(책임)/Change Agent/Tizen Platform Lab(S/W센터)/삼성전자 > Date : 2016-04-15 15:32 (GMT+09:00) >> >> 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. > > Along with Devfreq/Passive patchset, the patchset is merged in > devfreq for-4.7 tree. > > https://git.kernel.org/cgit/linux/kernel/git/mzx/devfreq.git/log/?h=for-4.7 > > @Chanwoo: If there are commits to be merged by a tree other than Linux/PM, > please let me know. I'll send out pull-request soon. On Krzysztof Kozlowski's reply, dts patches will be merged on samsung-soc tree. and then the clock patches about exynos5420 was already merged to samsung-clk tree by Sylwester. Only devfreq patches should be merged on devfreq tree. We already discussed this topic on offline. I expect that you will again handle this patchset according to reply of both Krzysztof and me. Best Regards, Chanwoo Choi > > > Cheers, > MyungJoo > >> >> 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 >> >> -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |