[RFC V1 0/8] CPUFreq: create platform-dev for DT based cpufreq drivers

Viresh Kumar viresh.kumar at linaro.org
Mon Dec 1 06:48:10 PST 2014


On 1 December 2014 at 19:35, Arnd Bergmann <arnd at arndb.de> wrote:
> I guess a string would be better here, the idea here was to
> have a different bool property per driver, which would also
> work.

Hmm, I will prefer string as we don't need to define any more bindings then
for new drivers.

>> > @@ -367,29 +404,19 @@ static int dt_cpufreq_probe(struct platform_device *pdev)
>> >         if (!IS_ERR(cpu_reg))
>> >                 regulator_put(cpu_reg);
>> >
>> > -       dt_cpufreq_driver.driver_data = dev_get_platdata(&pdev->dev);
>> > -
>>
>> We still need this, and its about how clocks are shared between CPUs.
>
> I didn't see where this comes from. Who is setting up this platform
> data?

Mvebu is using it to communicate that all CPUs have separate
clock lines.

--
viresh



More information about the linux-arm-kernel mailing list