From: Lukasz Majewski <l.majewski@samsung.com> To: Tomasz Figa <tomasz.figa@gmail.com> Cc: Kevin Hilman <khilman@linaro.org>, Kukjin Kim <kgene.kim@samsung.com>, mturquette@linaro.org, heiko@sntech.de, linux-pm@vger.kernel.org, viresh.kumar@linaro.org, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, amit.kucheria@linaro.org, cw00.choi@samsung.com, Thomas Abraham <thomas.ab@samsung.com>, linux-samsung-soc@vger.kernel.org, linaro-kernel@lists.linaro.org, linux-arm-kernel@lists.infradead.org, Marek Szyprowski <m.szyprowski@samsung.com>, Lukasz Majewski <l.majewski@majess.pl> Subject: Re: [PATCH v9 4/6] ARM: Exynos: switch to using generic cpufreq driver for Exynos4210/5250/5420 Date: Mon, 25 Aug 2014 08:53:52 +0200 [thread overview] Message-ID: <20140825085352.14290508@amdc2363> (raw) In-Reply-To: <53F7DA13.6090305@gmail.com> Hi Tomasz, > Hi Kevin, > > Thanks for taking a look at this. > > On 23.08.2014 01:54, Kevin Hilman wrote: > > Tomasz Figa <tomasz.figa@gmail.com> 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 CPUfreq driver > >>>> support, enable the use of generic CPUfreq driver. > >>>> > >>>> Suggested-by: Tomasz Figa<t.figa@samsung.com> > >>>> Cc: Kukjin Kim<kgene.kim@samsung.com> > >>> > >>> Looks good to me, > >>> > >>> Acked-by: Kukjin Kim <kgene.kim@samsung.com> > >>> > >>> BTW, who will handle this series? I hope see this series in 3.17. > >> > >> This series consists mostly of clock changes and it likely depends > >> on patches already in my for-next, so I would be inclined toward > >> taking it through samsung-clk tree. > > > > So has this series been picked up anywhere? I don't see it in your > > samsung-clk tree, nor in Kukjin's for-next. > > No, it has not. In general it was already too late in the release > cycle when the last version was posted. > > I had a plan to take it through clock tree with Kukjin's and Viresh's > cooperation, but now as you say it... > > > > > Also, I'm curious whether or how this is has been tested on > > big.LITTLE SoCs. > > > > 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 else that's testing CPUidle and CPUfreq > > together big.LITTLE 5420/5800, with or without the switcher. > > I'd definitely like to see a clarification on this issues, before this > series hits mainline or at least its parts related to affected SoCs. It is a huge step forward - to be honest it is a serious rework of cpufreq subsystem for Exynos SoCs. > Also I'd like to hear some confirmation from Samsung Poland R&D Center > guys (on CC), whether this code works stable on their target boards > (Universal C210, Trats, Trats2). > Since we have missed the merge window with this code, I can declare that I will provide code, which means that I will do the cleanup for excluded from this series Exynos4 SoCs, to test the cpufreq-cpu0. However, I'm concerned with Exynos4412, which supports BOOST. It might not be trivial to provide support for it. I think, that we shall not drop behind any functionality during clean up. > > > > Also, the patch below[2] is needed for 5800. > > > > FWIW, I have a temporary branch[1] based on the v3.17-rc branch of > > the exynos-reference tree where I've added the DT patch needed for > > CPUidle, this series (and it's dependencies) which is what I'm > > using for testing. > > The patch looks fine to me (well, it's trivial :)), thanks. > > Best regards, > Tomasz > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- Best regards, Lukasz Majewski Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
WARNING: multiple messages have this Message-ID (diff)
From: l.majewski@samsung.com (Lukasz Majewski) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v9 4/6] ARM: Exynos: switch to using generic cpufreq driver for Exynos4210/5250/5420 Date: Mon, 25 Aug 2014 08:53:52 +0200 [thread overview] Message-ID: <20140825085352.14290508@amdc2363> (raw) In-Reply-To: <53F7DA13.6090305@gmail.com> Hi Tomasz, > Hi Kevin, > > Thanks for taking a look at this. > > On 23.08.2014 01:54, Kevin Hilman wrote: > > Tomasz Figa <tomasz.figa@gmail.com> 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 CPUfreq driver > >>>> support, enable the use of generic CPUfreq driver. > >>>> > >>>> Suggested-by: Tomasz Figa<t.figa@samsung.com> > >>>> Cc: Kukjin Kim<kgene.kim@samsung.com> > >>> > >>> Looks good to me, > >>> > >>> Acked-by: Kukjin Kim <kgene.kim@samsung.com> > >>> > >>> BTW, who will handle this series? I hope see this series in 3.17. > >> > >> This series consists mostly of clock changes and it likely depends > >> on patches already in my for-next, so I would be inclined toward > >> taking it through samsung-clk tree. > > > > So has this series been picked up anywhere? I don't see it in your > > samsung-clk tree, nor in Kukjin's for-next. > > No, it has not. In general it was already too late in the release > cycle when the last version was posted. > > I had a plan to take it through clock tree with Kukjin's and Viresh's > cooperation, but now as you say it... > > > > > Also, I'm curious whether or how this is has been tested on > > big.LITTLE SoCs. > > > > 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 else that's testing CPUidle and CPUfreq > > together big.LITTLE 5420/5800, with or without the switcher. > > I'd definitely like to see a clarification on this issues, before this > series hits mainline or at least its parts related to affected SoCs. It is a huge step forward - to be honest it is a serious rework of cpufreq subsystem for Exynos SoCs. > Also I'd like to hear some confirmation from Samsung Poland R&D Center > guys (on CC), whether this code works stable on their target boards > (Universal C210, Trats, Trats2). > Since we have missed the merge window with this code, I can declare that I will provide code, which means that I will do the cleanup for excluded from this series Exynos4 SoCs, to test the cpufreq-cpu0. However, I'm concerned with Exynos4412, which supports BOOST. It might not be trivial to provide support for it. I think, that we shall not drop behind any functionality during clean up. > > > > Also, the patch below[2] is needed for 5800. > > > > FWIW, I have a temporary branch[1] based on the v3.17-rc branch of > > the exynos-reference tree where I've added the DT patch needed for > > CPUidle, this series (and it's dependencies) which is what I'm > > using for testing. > > The patch looks fine to me (well, it's trivial :)), thanks. > > Best regards, > Tomasz > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- Best regards, Lukasz Majewski Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
next prev parent reply other threads:[~2014-08-25 6:53 UTC|newest] Thread overview: 121+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-30 8:07 [PATCH v9 0/6] cpufreq: use generic cpufreq drivers for exynos platforms Thomas Abraham 2014-07-30 8:07 ` Thomas Abraham 2014-07-30 8:07 ` [PATCH v9 1/6] clk: samsung: add infrastructure to register cpu clocks Thomas Abraham 2014-07-30 8:07 ` Thomas Abraham 2014-09-01 22:29 ` Mike Turquette 2014-09-01 22:29 ` Mike Turquette 2014-09-02 13:53 ` Thomas Abraham 2014-09-02 13:53 ` Thomas Abraham 2014-07-30 8:07 ` [PATCH v9 2/6] clk: samsung: add cpu clock configuration data and instantiate cpu clock Thomas Abraham 2014-07-30 8:07 ` Thomas Abraham 2014-09-01 22:29 ` Mike Turquette 2014-09-01 22:29 ` Mike Turquette 2014-07-30 8:07 ` [PATCH v9 3/6] ARM: dts: Exynos: add CPU OPP and regulator supply property Thomas Abraham 2014-07-30 8:07 ` Thomas Abraham 2014-07-30 11:28 ` Andreas Färber 2014-07-30 11:28 ` Andreas Färber 2014-07-31 2:55 ` Thomas Abraham 2014-07-31 2:55 ` Thomas Abraham 2014-07-31 0:37 ` Doug Anderson 2014-07-31 0:37 ` Doug Anderson 2014-07-31 3:21 ` Thomas Abraham 2014-07-31 3:21 ` Thomas Abraham 2014-07-31 3:53 ` Doug Anderson 2014-07-31 3:53 ` Doug Anderson 2014-07-31 4:06 ` Thomas Abraham 2014-07-31 4:06 ` Thomas Abraham 2014-07-31 4:08 ` Doug Anderson 2014-07-31 4:08 ` Doug Anderson 2014-07-31 4:18 ` Thomas Abraham 2014-07-31 4:18 ` Thomas Abraham 2014-08-02 3:49 ` Javier Martinez Canillas 2014-08-02 3:49 ` Javier Martinez Canillas 2014-08-04 3:00 ` Thomas Abraham 2014-08-04 3:00 ` Thomas Abraham 2014-07-30 8:07 ` [PATCH v9 4/6] ARM: Exynos: switch to using generic cpufreq driver for Exynos4210/5250/5420 Thomas Abraham 2014-07-30 8:07 ` Thomas Abraham 2014-07-31 18:32 ` Kukjin Kim 2014-07-31 18:32 ` Kukjin Kim 2014-07-31 18:40 ` Tomasz Figa 2014-07-31 18:40 ` Tomasz Figa 2014-07-31 18:54 ` Tomasz Figa 2014-07-31 18:54 ` Tomasz Figa 2014-07-31 19:25 ` Thomas Abraham 2014-07-31 19:25 ` Thomas Abraham 2014-07-31 19:30 ` Tomasz Figa 2014-07-31 19:30 ` Tomasz Figa 2014-08-04 3:24 ` Thomas Abraham 2014-08-04 3:24 ` Thomas Abraham 2014-08-22 23:54 ` Kevin Hilman 2014-08-22 23:54 ` Kevin Hilman 2014-08-23 0:02 ` Tomasz Figa 2014-08-23 0:02 ` Tomasz Figa 2014-08-25 6:53 ` Lukasz Majewski [this message] 2014-08-25 6:53 ` Lukasz Majewski 2014-08-25 12:15 ` Chander Kashyap 2014-08-25 12:15 ` Chander Kashyap 2014-08-25 15:32 ` Kevin Hilman 2014-08-25 15:32 ` Kevin Hilman 2014-08-25 15:56 ` Tomasz Figa 2014-08-25 15:56 ` Tomasz Figa 2014-08-26 4:54 ` Viresh Kumar 2014-08-26 4:54 ` Viresh Kumar 2014-08-26 5:25 ` Chander Kashyap 2014-08-26 5:25 ` Chander Kashyap 2014-08-26 15:15 ` Kevin Hilman 2014-08-26 15:15 ` Kevin Hilman 2014-08-26 22:25 ` Kevin Hilman 2014-08-26 22:25 ` Kevin Hilman 2014-08-29 12:52 ` Thomas Abraham 2014-08-29 12:52 ` Thomas Abraham 2014-08-29 15:03 ` Kevin Hilman 2014-08-29 15:03 ` Kevin Hilman 2014-09-01 8:47 ` Thomas Abraham 2014-09-01 8:47 ` Thomas Abraham 2014-09-02 19:32 ` Kevin Hilman 2014-09-02 19:32 ` Kevin Hilman 2014-09-03 4:26 ` Thomas Abraham 2014-09-03 4:26 ` Thomas Abraham 2014-09-03 13:18 ` Thomas Abraham 2014-09-03 13:18 ` Thomas Abraham 2014-09-03 23:15 ` Kevin Hilman 2014-09-03 23:15 ` Kevin Hilman 2014-09-04 10:22 ` Thomas Abraham 2014-09-04 13:30 ` Kevin Hilman 2014-09-04 13:30 ` Kevin Hilman 2014-09-05 13:41 ` Thomas Abraham 2014-09-05 13:41 ` Thomas Abraham 2014-08-25 8:11 ` Sjoerd Simons 2014-08-25 8:11 ` Sjoerd Simons 2014-07-30 8:07 ` [PATCH v9 5/6] cpufreq: exynos: remove exynos4210/5250 specific cpufreq driver support Thomas Abraham 2014-07-30 8:07 ` Thomas Abraham 2014-07-30 8:07 ` [PATCH v9 6/6] clk: samsung: remove unused clock aliases and update clock flags Thomas Abraham 2014-07-30 8:07 ` Thomas Abraham 2014-07-31 14:13 ` Tomasz Figa 2014-07-31 14:13 ` Tomasz Figa 2014-07-31 18:24 ` Thomas Abraham 2014-07-31 18:24 ` Thomas Abraham 2014-07-31 18:35 ` Tomasz Figa 2014-07-31 18:35 ` Tomasz Figa 2014-07-31 18:41 ` Thomas Abraham 2014-07-31 18:41 ` Thomas Abraham 2014-07-31 18:46 ` Tomasz Figa 2014-07-31 18:46 ` Tomasz Figa 2014-07-31 18:49 ` Thomas Abraham 2014-07-31 18:49 ` Thomas Abraham 2014-09-01 22:31 ` Mike Turquette 2014-09-01 22:31 ` Mike Turquette 2014-07-31 6:20 ` [PATCH v9 0/6] cpufreq: use generic cpufreq drivers for exynos platforms Chander M. Kashyap 2014-07-31 6:20 ` Chander M. Kashyap 2014-07-31 10:59 ` Thomas Abraham 2014-07-31 10:59 ` Thomas Abraham 2014-07-31 12:24 ` Chander M. Kashyap 2014-07-31 12:24 ` Chander M. Kashyap 2014-07-31 14:15 ` Tomasz Figa 2014-07-31 14:15 ` Tomasz Figa 2014-07-31 18:25 ` Thomas Abraham 2014-07-31 18:25 ` Thomas Abraham 2014-07-31 18:34 ` Thomas Abraham 2014-07-31 18:34 ` Thomas Abraham 2014-08-01 9:42 ` Viresh Kumar 2014-08-01 9:42 ` Viresh Kumar
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=20140825085352.14290508@amdc2363 \ --to=l.majewski@samsung.com \ --cc=amit.kucheria@linaro.org \ --cc=b.zolnierkie@samsung.com \ --cc=cw00.choi@samsung.com \ --cc=heiko@sntech.de \ --cc=kgene.kim@samsung.com \ --cc=khilman@linaro.org \ --cc=l.majewski@majess.pl \ --cc=linaro-kernel@lists.linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-pm@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=m.szyprowski@samsung.com \ --cc=mturquette@linaro.org \ --cc=thomas.ab@samsung.com \ --cc=tomasz.figa@gmail.com \ --cc=viresh.kumar@linaro.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.