[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linaro-kernel
Subject:    [Question] Status For big.LITTLE's IKS
From:       david.rusling () linaro ! org (David Rusling)
Date:       2013-04-29 10:44:25
Message-ID: 517E4F09.3030305 () linaro ! org
[Download RAW message or body]

Leo et al,

> Nicolas Pitre <mailto:nicolas.pitre at linaro.org>
> 29 April 2013 00:41
> On Sun, 28 Apr 2013, Leo Yan wrote:
>
>> hi Nico&  all,
>>
>> Per Samsung has released their big.LITTLE phone, and the IKS code has been
>> release in its kernel's source code; so may be now it's good time for us to
>> know status of IKS from Linaro side:
>
> One thing to note is the released IKS code from Samsung is based on very
> old code from a Linaro perspective i.e. dating from last August or so.
>
>> 1. What's the plan for Lianro to release iks related patches?
>>
>> Due now mcpm related patches are pending for mainline's merge, unfortunately
>> iks is based on the mcpm patches; so when will u send iks patches to open
>> source's mailing list?
>
> The MCPM patches have been accepted by Russell and will be merged into
> mainline during the next merge window.
>
> There is a process in progress within Linaro for getting permission to
> publish the latest IKS code. I'll publish the code as soon as I have the
> green light.

The Technical Steering Committee (TSC) is voting on it.  The vote closes 
Wednesday.

Dave
>
>> On the other hand, do u have plan to merge iks related patches firstly to
>> Lianro ARM landing team's branch? if so, then it will not depend on mainline
>> and can be much more efficient.
>
> The IKS patches are maintained on top of the ARM LT tree already.
>
>> 2. Looked into Samsung's code, there have the cluster switching which is based
>> on iks (named ikcs); so now in your code base, do u have implemented related
>> functionality?
>
> No.  That is not a feature you should be wishing for either.  I hope you
> won't need it.
>
> This is rather unfortunate that Samsung had to do that due to hardware
> limitations.  And the way they implemented it is not optimal.
>
>
> Nicolas
>
> _______________________________________________
> linaro-kernel mailing list
> linaro-kernel at lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-kernel
> Leo Yan <mailto:leoy at marvell.com>
> 28 April 2013 02:07
> hi Nico & all,
>
> Per Samsung has released their big.LITTLE phone, and the IKS code has 
> been release in its kernel's source code; so may be now it's good time 
> for us to know status of IKS from Linaro side:
>
> 1. What's the plan for Lianro to release iks related patches?
>
> Due now mcpm related patches are pending for mainline's merge, 
> unfortunately iks is based on the mcpm patches; so when will u send 
> iks patches to open source's mailing list?
>
> On the other hand, do u have plan to merge iks related patches firstly 
> to Lianro ARM landing team's branch? if so, then it will not depend on 
> mainline and can be much more efficient.
>
> 2. Looked into Samsung's code, there have the cluster switching which 
> is based on iks (named ikcs); so now in your code base, do u have 
> implemented related functionality?
>

-- 
David Rusling
CTO
Linaro Ltd
e.  david.rusling at linaro.org
w.  http://www.linaro.org
Linaro: The future of Linux on ARM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linaro.org/pipermail/linaro-kernel/attachments/20130429/e832b006/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
URL: <http://lists.linaro.org/pipermail/linaro-kernel/attachments/20130429/e832b006/attachment-0001.jpg>

[prev in list] [next in list] [prev in thread] [next in thread]