On 2014-12-03 11:56, Arnd Bergmann wrote:
> On Wednesday 03 December 2014 01:12:09 Stefan Agner wrote:
>> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
>> index 89c4b5c..fdebe18 100644
>> --- a/arch/arm/Kconfig
>> +++ b/arch/arm/Kconfig
>> @@ -459,6 +459,18 @@ config ARCH_FOOTBRIDGE
>> Support for systems based on the DC21285 companion chip
>> ("FootBridge"), such as the Simtec CATS and the Rebel NetWinder.
>>
>> +menuconfig ARCH_MXCM4
>> + bool "Freescale Vybrid/i.MX family on Cortex-M4" if !MMU
>> + select ARCH_REQUIRE_GPIOLIB
>> + select ARM_CPU_SUSPEND if PM
>> + select CLKSRC_MMIO
>> + select GENERIC_IRQ_CHIP
>> + select PINCTRL
>> + select PM_OPP if PM
>> + select SOC_BUS
>> + help
>> + Support for Freescale Vybrid/iMX-based family of processors on
>> Cortex-M4
>> +
>> config ARCH_NETX
>> bool "Hilscher NetX based"
>> select ARM_VIC
>
> I would really prefer not to see any more standalone machine types,
> but rather have ARMv7-M as one of the options for the
> multiplatform configuration. In particular, that would let us
> do *build* testing on a combined mxcm4/efm32/vexpress kernel,
> although that kernel would clearly not be usable anywhere
> because of the restrictions of nommu machines.
Yes me too, but as I pointed out in the cover letter, I'm not sure I'm
up to that task.... I'm not at all in a hurry with the Vybrid M4 Linux
stuff, so I can wait until that is resolved or maybe try to resolve that
myself (again)...
Beside that the multi-platform would help do build tests, Vybrid is also
a nice platform to do smoke tests on a !MMU platform. Uwe would be happy
about that, as he discovered that !MMU was broken for several releases
lately :-)
>
>> +static void __init vf610m4_init_irq(void)
>> +{
>> + vf610_mscm_init();
>> + irqchip_init();
>> +}
>
> Can you make vf610_mscm_init get called from irqchip and remove this
> function?
>
I guess you mean by IRQCHIP_DECLARE? I hesitated to do this since I only
found drivers in drivers/irqchip using that. However, MSCM is currently
part of mach-imx. First I used arch_extn to implement the functionality,
so I thought it really fits more into arch. But I guess when it is a
normal irqchip driver, I will have to move it anyway, despite the fact
that it is only available on Vybrid....?
--
Stefan
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
