From: Tushar Behera <tushar.behera@linaro.org>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
mturquette@linaro.org, kgene.kim@samsung.com, patches@linaro.org,
swarren@wwwdotorg.org, grant.likely@linaro.org,
rob.herring@calxeda.com, devicetree-discuss@lists.ozlabs.org,
broonie@kernel.org, l.majewski@samsung.com,
s.nawrocki@samsung.com
Subject: Re: [PATCH 2/2] clk: exynos4: Add alias for cpufreq related clocks
Date: Mon, 17 Jun 2013 10:20:45 +0530 [thread overview]
Message-ID: <51BE95A5.5090509@linaro.org> (raw)
In-Reply-To: <3226068.I7g6oVyl1p@flatron>
On 06/11/2013 12:23 AM, Tomasz Figa wrote:
> On Monday 10 of June 2013 09:13:11 Tushar Behera wrote:
>> On 06/08/2013 05:20 PM, Tomasz Figa wrote:
>>> On Thursday 06 of June 2013 16:52:28 Tushar Behera wrote:
[ ... ]
>>>> MUX_A(mout_core, "mout_core", mout_core_p4210,
>>>>
>>>> - SRC_CPU, 16, 1, "mout_core"),
>>>> + SRC_CPU, 16, 1, "moutcore"),
>>>
>>> IMHO those typo corrections are not part of this patch.
>>
>> But the older drivers (before migration to CCF) were using the clock
>> "moutcore" (not "mout_core").
>
> I mean, this should be placed in a separate patch, as this change is not
> "adding alias for cpufreq related clocks", but rather fixing a typo.
>
Is it ok if I split this patch into 2, one adding clock alias
'mout_apll' and another one fixing the alias names 'mout_mpll',
'moutcore' and 'armclk'?
[ ... ]
>>> Basically I don't like the idea of those global aliases, which IMHO
>>> should be completely dropped. Someone might not like it, but I'd go
>>> with the conversion of our cpufreq drivers to platform drivers
>>> instead, which could receive things like clocks and regulators using
>>> DT-based lookups.
>> I agree. Migration of exynos-cpufreq driver as a platform driver is the
>> best solution. But unless someone picks up that work, cpufreq support
>> for EXYNOS4 based systems is broken because of the incorrect clock
>> aliases.
>
> We have patches for this in our internal tree. I will clean them up a bit
> and submit soon.
>
If you are going to submit the cpufreq driver patches for v3.11, then we
can ignore this patchset. Otherwise, I would prefer to get these patches
merged for v3.11 to get cpufreq working. Once the driver changes are
incorporated, we can very well modify these later.
Thanks.
--
Tushar Behera
next prev parent reply other threads:[~2013-06-17 4:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 11:22 [PATCH 0/2] Clock update for EXYNOS4210-CPUFREQ driver Tushar Behera
2013-06-06 11:22 ` [PATCH 1/2] clk: samsung: Add MUX_FA macro to pass flag and alias Tushar Behera
2013-06-06 11:22 ` [PATCH 2/2] clk: exynos4: Add alias for cpufreq related clocks Tushar Behera
2013-06-08 11:50 ` Tomasz Figa
2013-06-10 3:43 ` Tushar Behera
2013-06-10 18:53 ` Tomasz Figa
2013-06-17 4:50 ` Tushar Behera [this message]
2013-06-19 4:50 ` Tushar Behera
2013-06-19 7:43 ` Tomasz Figa
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=51BE95A5.5090509@linaro.org \
--to=tushar.behera@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=l.majewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=patches@linaro.org \
--cc=rob.herring@calxeda.com \
--cc=s.nawrocki@samsung.com \
--cc=swarren@wwwdotorg.org \
--cc=tomasz.figa@gmail.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).