On Thu, Sep 4, 2014 at 7:00 PM, Kevin Hilman wrote:
> Thomas Abraham writes:
>
>> On Thu, Sep 4, 2014 at 4:45 AM, Kevin Hilman wrote:
>>> Hi Thomas,
>>>
>>> Thomas Abraham writes:
>>>
>>> [...]
>>>
A new branch [1] has been created using commits from exynos5-v3.17-rc1
branch + cpufreq
Thomas Abraham writes:
> On Thu, Sep 4, 2014 at 4:45 AM, Kevin Hilman wrote:
>> Hi Thomas,
>>
>> Thomas Abraham writes:
>>
>> [...]
>>
>>> A new branch [1] has been created using commits from exynos5-v3.17-rc1
>>> branch + cpufreq + regulator + temp fixes. I have tested this branch
>>> on Exyno
On Thu, Sep 4, 2014 at 4:45 AM, Kevin Hilman wrote:
> Hi Thomas,
>
> Thomas Abraham writes:
>
> [...]
>
>> A new branch [1] has been created using commits from exynos5-v3.17-rc1
>> branch + cpufreq + regulator + temp fixes. I have tested this branch
>> on Exynos5800 Chromebook2 and cpufreq works
Hi Thomas,
Thomas Abraham writes:
[...]
> A new branch [1] has been created using commits from exynos5-v3.17-rc1
> branch + cpufreq + regulator + temp fixes. I have tested this branch
> on Exynos5800 Chromebook2 and cpufreq works fine with both ondemand
> and performance governors. Please let m
On Wed, Sep 3, 2014 at 9:56 AM, Thomas Abraham wrote:
> Hi Kevin,
>
> On Wed, Sep 3, 2014 at 1:02 AM, Kevin Hilman wrote:
>> HI Thomas,
>>
>> Thomas Abraham writes:
>>
>>> On Fri, Aug 29, 2014 at 8:33 PM, Kevin Hilman wrote:
Hi Thomas,
On Fri, Aug 29, 2014 at 5:52 AM, Thomas Abra
Hi Kevin,
On Wed, Sep 3, 2014 at 1:02 AM, Kevin Hilman wrote:
> HI Thomas,
>
> Thomas Abraham writes:
>
>> On Fri, Aug 29, 2014 at 8:33 PM, Kevin Hilman wrote:
>>> Hi Thomas,
>>>
>>> On Fri, Aug 29, 2014 at 5:52 AM, Thomas Abraham wrote:
Hi Kevin,
On Wed, Aug 27, 2014 at 3:55 AM
HI Thomas,
Thomas Abraham writes:
> On Fri, Aug 29, 2014 at 8:33 PM, Kevin Hilman wrote:
>> Hi Thomas,
>>
>> On Fri, Aug 29, 2014 at 5:52 AM, Thomas Abraham wrote:
>>> Hi Kevin,
>>>
>>> On Wed, Aug 27, 2014 at 3:55 AM, Kevin Hilman wrote:
On Tue, Aug 26, 2014 at 8:15 AM, Kevin Hilman wr
Hi Kevin,
On Fri, Aug 29, 2014 at 8:33 PM, Kevin Hilman wrote:
> Hi Thomas,
>
> On Fri, Aug 29, 2014 at 5:52 AM, Thomas Abraham wrote:
>> Hi Kevin,
>>
>> On Wed, Aug 27, 2014 at 3:55 AM, Kevin Hilman wrote:
>>> On Tue, Aug 26, 2014 at 8:15 AM, Kevin Hilman wrote:
On Mon, Aug 25, 2014 at
Hi Thomas,
On Fri, Aug 29, 2014 at 5:52 AM, Thomas Abraham wrote:
> Hi Kevin,
>
> On Wed, Aug 27, 2014 at 3:55 AM, Kevin Hilman wrote:
>> On Tue, Aug 26, 2014 at 8:15 AM, Kevin Hilman wrote:
>>> On Mon, Aug 25, 2014 at 10:25 PM, Chander Kashyap
>>> wrote:
>>
>> [...]
>>
>
> Can you cl
Hi Kevin,
On Wed, Aug 27, 2014 at 3:55 AM, Kevin Hilman wrote:
> On Tue, Aug 26, 2014 at 8:15 AM, Kevin Hilman wrote:
>> On Mon, Aug 25, 2014 at 10:25 PM, Chander Kashyap
>> wrote:
>
> [...]
>
Can you clarify how you're setting the voltages to ensure stability?
>>>
>>> below is the d
On Tue, Aug 26, 2014 at 8:15 AM, Kevin Hilman wrote:
> On Mon, Aug 25, 2014 at 10:25 PM, Chander Kashyap
> wrote:
[...]
>>>
>>> Can you clarify how you're setting the voltages to ensure stability?
>>
>> below is the diff : wip/exynos/integ
>
> Thanks.
>
> I've applied your patch, and bootup s
On Mon, Aug 25, 2014 at 10:25 PM, Chander Kashyap wrote:
> Hi Kevin,
>
> On Mon, Aug 25, 2014 at 9:02 PM, Kevin Hilman wrote:
>> Hi Chander,
>>
>> Chander Kashyap writes:
>>
>> [...]
>>
> I'm trying it on the 5800/Chromebook2 and it's not terribly stable. I'm
> testing along with CPUidl
Hi Kevin,
On Mon, Aug 25, 2014 at 9:02 PM, Kevin Hilman wrote:
> Hi Chander,
>
> Chander Kashyap writes:
>
> [...]
>
I'm trying it on the 5800/Chromebook2 and it's not terribly stable. I'm
testing along with CPUidle, so there may be some untested interactions
there as it seems a
On 25 August 2014 21:26, Tomasz Figa wrote:
> Kukjin, Viresh, how would you want to proceed with merging it? It
Me and Rafael has agreed earlier that Kukjin can take these through
ARM-Soc tree..
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a messa
On 25.08.2014 17:32, Kevin Hilman wrote:
> Hi Chander,
>
> Chander Kashyap writes:
>
> [...]
>
I'm trying it on the 5800/Chromebook2 and it's not terribly stable. I'm
testing along with CPUidle, so there may be some untested interactions
there as it seems a bit more stable witho
Hi Chander,
Chander Kashyap writes:
[...]
>>> I'm trying it on the 5800/Chromebook2 and it's not terribly stable. I'm
>>> testing along with CPUidle, so there may be some untested interactions
>>> there as it seems a bit more stable without CPUidle enabled.
>>>
>>> I'd love to hear from anyone
Hi Kevin, Tomasz,
On Sat, Aug 23, 2014 at 5:32 AM, Tomasz Figa wrote:
> Hi Kevin,
>
> Thanks for taking a look at this.
>
> On 23.08.2014 01:54, Kevin Hilman wrote:
>> Tomasz Figa writes:
>>
>>> Kukjin,
>>>
>>> On 31.07.2014 20:32, Kukjin Kim wrote:
On 07/30/14 17:07, Thomas Abraham wrote:
Hey,
On Fri, 2014-08-22 at 16:54 -0700, Kevin Hilman wrote:
> Tomasz Figa writes:
>
> > Kukjin,
> >
> > On 31.07.2014 20:32, Kukjin Kim wrote:
> >> On 07/30/14 17:07, Thomas Abraham wrote:
> >>> The new CPU clock type allows the use of generic CPUfreq drivers. So for
> >>> Exynos4210/5250, switc
Hi Tomasz,
> Hi Kevin,
>
> Thanks for taking a look at this.
>
> On 23.08.2014 01:54, Kevin Hilman wrote:
> > Tomasz Figa writes:
> >
> >> Kukjin,
> >>
> >> On 31.07.2014 20:32, Kukjin Kim wrote:
> >>> On 07/30/14 17:07, Thomas Abraham wrote:
> The new CPU clock type allows the use of gen
Hi Kevin,
Thanks for taking a look at this.
On 23.08.2014 01:54, Kevin Hilman wrote:
> Tomasz Figa writes:
>
>> Kukjin,
>>
>> On 31.07.2014 20:32, Kukjin Kim wrote:
>>> On 07/30/14 17:07, Thomas Abraham wrote:
The new CPU clock type allows the use of generic CPUfreq drivers. So for
Ex
Tomasz Figa writes:
> Kukjin,
>
> On 31.07.2014 20:32, Kukjin Kim wrote:
>> On 07/30/14 17:07, Thomas Abraham wrote:
>>> The new CPU clock type allows the use of generic CPUfreq drivers. So for
>>> Exynos4210/5250, switch to using generic cpufreq driver. For Exynos5420,
>>> which did not have CPU
Hi Tomasz,
On Fri, Aug 1, 2014 at 1:00 AM, Tomasz Figa wrote:
> On 31.07.2014 21:25, Thomas Abraham wrote:
>> On Fri, Aug 1, 2014 at 12:24 AM, Tomasz Figa wrote:
>>>
>>>
>>> On 31.07.2014 20:40, Tomasz Figa wrote:
Kukjin,
On 31.07.2014 20:32, Kukjin Kim wrote:
> On 07/30/14 17
On 31.07.2014 21:25, Thomas Abraham wrote:
> On Fri, Aug 1, 2014 at 12:24 AM, Tomasz Figa wrote:
>>
>>
>> On 31.07.2014 20:40, Tomasz Figa wrote:
>>> Kukjin,
>>>
>>> On 31.07.2014 20:32, Kukjin Kim wrote:
On 07/30/14 17:07, Thomas Abraham wrote:
> The new CPU clock type allows the use of
On Fri, Aug 1, 2014 at 12:24 AM, Tomasz Figa wrote:
>
>
> On 31.07.2014 20:40, Tomasz Figa wrote:
>> Kukjin,
>>
>> On 31.07.2014 20:32, Kukjin Kim wrote:
>>> On 07/30/14 17:07, Thomas Abraham wrote:
The new CPU clock type allows the use of generic CPUfreq drivers. So for
Exynos4210/5250,
On 31.07.2014 20:40, Tomasz Figa wrote:
> Kukjin,
>
> On 31.07.2014 20:32, Kukjin Kim wrote:
>> On 07/30/14 17:07, Thomas Abraham wrote:
>>> The new CPU clock type allows the use of generic CPUfreq drivers. So for
>>> Exynos4210/5250, switch to using generic cpufreq driver. For Exynos5420,
>>> w
Kukjin,
On 31.07.2014 20:32, Kukjin Kim wrote:
> On 07/30/14 17:07, Thomas Abraham wrote:
>> The new CPU clock type allows the use of generic CPUfreq drivers. So for
>> Exynos4210/5250, switch to using generic cpufreq driver. For Exynos5420,
>> which did not have CPUfreq driver support, enable the
On 07/30/14 17:07, Thomas Abraham wrote:
The new CPU clock type allows the use of generic CPUfreq drivers. So for
Exynos4210/5250, switch to using generic cpufreq driver. For Exynos5420,
which did not have CPUfreq driver support, enable the use of generic
CPUfreq driver.
Suggested-by: Tomasz Fig
The new CPU clock type allows the use of generic CPUfreq drivers. So for
Exynos4210/5250, switch to using generic cpufreq driver. For Exynos5420,
which did not have CPUfreq driver support, enable the use of generic
CPUfreq driver.
Suggested-by: Tomasz Figa
Cc: Kukjin Kim
Signed-off-by: Thomas Ab
28 matches
Mail list logo
