like to use the driver for those boards
which are not yet converted to DT. In that situation, we have a kernel
dedicate to kirkwood and the cpuidle driver is always relevant.
Thus i need to code something like:
(of_machine_is_compatible(marvell, kirkwood) ||
!machine_is_dt())
However
On Mon, Jan 7, 2013 at 3:59 PM, Rob Herring robherri...@gmail.com wrote:
You could make the platform code create the platform device in the DT
case as well. Not all platform devices have to come from a DT node and
putting virtual devices in DT is wrong.
For the ux500 cpufreq we do exactly
On Sun, Jan 06, 2013 at 02:18:05PM +0100, Andrew Lunn wrote:
Hi Folks
I'm moving the cpuidle code for Kirkwood into drivers/cpuidle. I'm
following the way cpuidle-calxeda.c instantiates the driver, it uses
module_init(calxeda_cpuidle_init) and calxeda_cpuidle_init() uses
.
Thus i need to code something like:
(of_machine_is_compatible(marvell, kirkwood) ||
!machine_is_dt())
However, there is no macro machine_is_dt().
Is there a way to tell if a machine has been booted using a machine
number as opposed to DT?
Thanks
Andrew
dedicate to kirkwood and the cpuidle driver is always relevant.
Thus i need to code something like:
(of_machine_is_compatible(marvell, kirkwood) ||
!machine_is_dt())
However, there is no macro machine_is_dt().
Is there a way to tell if a machine has been booted using a machine
number
boards
which are not yet converted to DT. In that situation, we have a kernel
dedicate to kirkwood and the cpuidle driver is always relevant.
Thus i need to code something like:
(of_machine_is_compatible(marvell, kirkwood) ||
!machine_is_dt())
However, there is no macro
