linux-kernel - Re: [PATCH 4/6] ARM: dts: Exynos4210: add CPU OPP and regulator supply property

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 23 Jun 2015 08:46:33 +0900
From:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
To:	Michael Turquette <mturquette@...libre.com>,
	Kukjin Kim <kgene@...nel.org>
Cc:	linux-arm-kernel@...ts.infradead.org,
	'Lukasz Majewski' <l.majewski@...sung.com>,
	'Heiko Stuebner' <heiko@...ech.de>,
	'Kevin Hilman' <khilman@...aro.org>,
	'Bartlomiej Zolnierkiewicz' <b.zolnierkie@...sung.com>,
	'Sachin Kamat' <sachin.kamat@...aro.org>,
	'Viresh Kumar' <viresh.kumar@...aro.org>,
	linux-pm@...r.kernel.org, 'Tomasz Figa' <tomasz.figa@...il.com>,
	linux-kernel@...r.kernel.org,
	'Chanwoo Choi' <cw00.choi@...sung.com>,
	'Thomas Abraham' <thomas.ab@...sung.com>,
	'Sylwester Nawrocki' <s.nawrocki@...sung.com>,
	'Andreas Faerber' <afaerber@...e.de>,
	'Doug Anderson' <dianders@...omium.org>,
	'Javier Martinez Canillas' <javier.martinez@...labora.co.uk>,
	linux-samsung-soc@...r.kernel.org
Subject: Re: [PATCH 4/6] ARM: dts: Exynos4210: add CPU OPP and regulator supply
 property

On 23.06.2015 00:04, Michael Turquette wrote:
> Quoting Kukjin Kim (2015-06-21 18:46:26)
>> Krzysztof Kozlowski wrote:
>>>
>>> On 22.06.2015 10:38, Kukjin Kim wrote:
>>>> Krzysztof Kozlowski wrote:
>>>>> 2015-05-08 9:18 GMT+09:00 Krzysztof Kozlowski <k.kozlowski@...sung.com>:
>>>>>> 2015-04-04 1:43 GMT+09:00 Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>:
>>>>>>> From: Thomas Abraham <thomas.ab@...sung.com>
>>>>>>>
>>>>>>> For Exynos4210 platforms, add CPU operating points and CPU
>>>>>>> regulator supply properties for migrating from Exynos specific
>>>>>>> cpufreq driver to using generic cpufreq driver.
>>>>>>>
>>>>>>> Changes by Bartlomiej:
>>>>>>> - removed Exynos5250 and Exynos5420 support for now
>>>>>>>
>>>>>>> Cc: Kukjin Kim <kgene.kim@...sung.com>
>>>>>>> Cc: Doug Anderson <dianders@...omium.org>
>>>>>>> Cc: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
>>>>>>> Cc: Andreas Faerber <afaerber@...e.de>
>>>>>>> Cc: Sachin Kamat <sachin.kamat@...aro.org>
>>>>>>> Cc: Andreas Farber <afaerber@...e.de>
>>>>>>> Cc: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
>>>>>>> Signed-off-by: Thomas Abraham <thomas.ab@...sung.com>
>>>>>>> Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
>>>>>>
>>>>>> Acked-by: Krzysztof Kozlowski <k.kozlowski@...sung.com>
>>>>>
>>>>> Rebased and applied to my tree, I'll sent it later to Kukjin unless he
>>>>> picks it by himself from LKML.
>>>>>
>>>> Hi, as far as I know, this is for v4.2 not v4.1 so it will be applied based on
>>>> v4.2-rc1 after v4.2-rc1 release.
>>>
>>> You mean it is for v4.3, not v4.2?
>>>
>> Oops, yes v4.3.
>>
>> Thanks for the correction.
> 
> Kukjin & Krzysztof,
> 
> I'm confused on this point. I was planning to take patches 1, 2, 3, 5
> and 6 towards 4.2 (e.g. in the pull request that I'll send out this
> week).
> 
> Is patch 4 going out for 4.2 or 4.3?

It is quite late for sending pull request to arm-soc for 4.2.
For example SoCFPGA pull request from last week was rejected:
http://comments.gmane.org/gmane.linux.ports.arm.kernel/417980

If you want to take it for 4.2 then I am fine with it but this will
cause some easy but annoying conflicts. There aren't difficult - just
most of nodes in board DTS changed their place.

Example of resolution (target file after merge, with cpu nodes reordered
alphabetically):
https://github.com/krzk/linux/commit/2cec3cb48abaf44848c62f1c0836b772eb4680dd

Best regards,
Krzysztof


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/