* Scott Ellis <sc...@jumpnowtek.com> [100314 10:22]:
> The McSPI_CHxCONF.CLKD register field has different limits for
> the OMAP3 then the OMAP24xx. New max_clk_div field added to
> mcspi platform config structure to keep track of this.
>
> Revised patch to not break multi-omap booting.
>
> Signed-off-by: Scott Ellis <sc...@jumpnowtek.com>
>
> arch/arm/mach-omap2/devices.c | 14 ++++++++++++++
> arch/arm/plat-omap/include/plat/mcspi.h | 1 +
> 2 files changed, 15 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
> index 23e4d77..200f382 100644
> --- a/arch/arm/mach-omap2/devices.c
> +++ b/arch/arm/mach-omap2/devices.c
> @@ -415,6 +415,11 @@ static inline void omap4_mcspi_fixup(void)
> defined(CONFIG_ARCH_OMAP4)
> static inline void omap2_mcspi3_init(void)
> {
> + if (cpu_is_omap343x() || cpu_is_omap44xx())
> + omap2_mcspi3_config.max_clk_div = 0x0c;
> + else
> + omap2_mcspi3_config.max_clk_div = 0x0f;
> +
> platform_device_register(&omap2_mcspi3);
> }
> #else
Hmm now it looks like you're missing 3630 handling?
If the max_clk_div is 0x0f for 2420 and 2430, then you
can just check for cpu_is_omap24xx(). If it's only
different for 2420, then you can check for cpu_is_omap2420().
That way it should be more future proof, and you don't
need to change it for new processors.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
