From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 3/3] ARM: shmobile: sh73a0: add CPUFreq support
Date: Fri, 05 Apr 2013 18:16:34 +0000 [thread overview]
Message-ID: <515F1502.3080301@cogentembedded.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1304051959500.997@axis700.grange>
On 04/05/2013 10:04 PM, Guennadi Liakhovetski wrote:
>>> This patch enables the use of the generic cpufreq-cpu0 driver on sh73a0.
>>> Providing a regulator, a list of OPPs in DT, combined with a virtual
>>> cpufreq-cpu0 platform device and a clock, attached to it is everything,
>>> the cpufreq-cpu0 driver needs. The first sh73a0 platform, implementing
>>> such CPUFreq support is kzm9g-reference.
>>> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
>>> ---
>>> v5: remove sh73a0-kzm9g-reference.dts hunk, it's now merged into patch 2/3
>>> arch/arm/mach-shmobile/Kconfig | 2 ++
>>> arch/arm/mach-shmobile/setup-sh73a0.c | 5 +++++
>>> 2 files changed, 7 insertions(+), 0 deletions(-)
>>> diff --git a/arch/arm/mach-shmobile/Kconfig b/arch/arm/mach-shmobile/Kconfig
>>> index 1a517e2..4ac5bf9 100644
>>> --- a/arch/arm/mach-shmobile/Kconfig
>>> +++ b/arch/arm/mach-shmobile/Kconfig
>> [...]
>>> diff --git a/arch/arm/mach-shmobile/setup-sh73a0.c
>>> b/arch/arm/mach-shmobile/setup-sh73a0.c
>>> index d10ded0..9a522f9 100644
>>> --- a/arch/arm/mach-shmobile/setup-sh73a0.c
>>> +++ b/arch/arm/mach-shmobile/setup-sh73a0.c
>>> @@ -1003,6 +1003,8 @@ static const struct of_dev_auxdata
>>> sh73a0_auxdata_lookup[] __initconst = {
>>>
>>> void __init sh73a0_add_standard_devices_dt(void)
>>> {
>>> + struct platform_device_info devinfo = { .name = "cpufreq-cpu0", .id >>> -1, };
>> With NULL .parent? Shouldn't it be 'platform_bus'?
> Look at platform_device_add():
>
> if (!pdev->dev.parent)
> pdev->dev.parent = &platform_bus;
Ah, thanks for pointing that out -- I didn't follow the call chain.
I could have passed NULL to platform_device_register_resndata()
too then... Well, now it's too late, and it doesn't matter much anyway.
WBR, Sergei
next prev parent reply other threads:[~2013-04-05 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 10:00 [PATCH v5 0/3] CPUFreq for sh73a0 / kzm9g, using cpufreq-cpu0 Guennadi Liakhovetski
2013-04-05 10:00 ` [PATCH v5 1/3] ARM: shmobile: sh73a0: add support for adjusting CPU frequency Guennadi Liakhovetski
2013-04-18 13:52 ` Simon Horman
2013-04-05 10:00 ` [PATCH v5 2/3] ARM: shmobile: kzm9g-reference: add AS3711 and CPUFreq DT bindings Guennadi Liakhovetski
2013-04-18 13:51 ` Simon Horman
2013-04-05 10:00 ` [PATCH v5 3/3] ARM: shmobile: sh73a0: add CPUFreq support Guennadi Liakhovetski
2013-04-05 16:07 ` Sergei Shtylyov
2013-04-05 18:04 ` Guennadi Liakhovetski
2013-04-05 18:16 ` Sergei Shtylyov [this message]
2013-04-18 13:52 ` Simon Horman
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=515F1502.3080301@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-arm-kernel@lists.infradead.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: 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).