[PATCH 1/5] ARM: bcm4760: Add platform infrastructure
Domenico Andreoli
cavokz at gmail.com
Sun Jul 21 06:29:25 EDT 2013
Arnd Bergmann <arnd at arndb.de> wrote:
>On Sunday 21 July 2013, Domenico Andreoli wrote:
>> From: Domenico Andreoli <domenico.andreoli at linux.com>
>>
>> Platform infrastructure for the Broadcom BCM4760 based ARM11 SoCs.
>>
>> Cc: linux-arm-kernel at lists.infradead.org
>> Signed-off-by: Domenico Andreoli <domenico.andreoli at linux.com>
>
>Looks very nice overall, thanks for following up on this!
Thank you for reviewing again.
>
>> +#define BCM4760_PERIPH_PHYS 0x00080000
>> +#define BCM4760_PERIPH_VIRT IOMEM(0xd0080000)
>> +#define BCM4760_PERIPH_SIZE SZ_512K
>> +
>> +static struct map_desc io_map __initdata = {
>> + .virtual = (unsigned long) BCM4760_PERIPH_VIRT,
>> + .pfn = __phys_to_pfn(BCM4760_PERIPH_PHYS),
>> + .length = BCM4760_PERIPH_SIZE,
>> + .type = MT_DEVICE,
>> +};
>> +
>> +static void __init bcm4760_map_io(void)
>> +{
>> + iotable_init(&io_map, 1);
>> +}
>
>I would hope expect a comment here explaining what those registers are
>and why
>they are mapped early.
Without these the board doesn't boot so I must be doing something
wrong somewhere else. I'll investigate.
>
>> +
>> +#define BCM4760_CPUID0 IOMEM(0xd00b0ff0)
>> +#define BCM4760_CPUID1 IOMEM(0xd00b0ff4)
>
>Better make these
>
>#define BCM4760_CPUID0 (BCM4760_PERIPH_VIRT + 0x30ff0)
>#define BCM4760_CPUID1 (BCM4760_PERIPH_VIRT + 0x30ff4)
>
>for clarity.
>
>> +static void __init bcm4760_system_rev(void)
>> +{
>> + u32 id0, id1;
>> +
>> + id0 = readl_relaxed(BCM4760_CPUID0);
>> + id1 = readl_relaxed(BCM4760_CPUID1);
>> +
>> + if (id0 >> 16 != 0xbcbc)
>> + system_rev = 0xbc4760a0;
>> + else
>> + system_rev = id0 << 8 | (id1 & 0xff);
>> +}
>
>Or even better, change this function to do:
>
> struct device_node *node = of_find_compatible_node(NULL, NULL,
>"brcm,whatever");
> void __iomem *regs = of_iomap(node, 0);
> u32 id0, id1;
>
> id0 = readl_relaxed(regs + BCM4760_CPUID0);
> id1 = readl_relaxed(regs + BCM4760_CPUID1);
>
> ...
>
> iounmap(regs);
> of_node_put(node);
>
>
>bonus points if you use soc_device_register();
>
>What is the system_rev variable actually used for?
I use it to show something sensible in /proc/cpuinfo, to report
whether the soc is a 4760 or 4761 and the silicon revision.
If the proper way to deal with this has so much boilerplate as
you say, I think I'll drop it altogether. I'd like to print the info
somewhere in the bootlog anyway.
btw this could well be one of the accesses requiring the io
mapping above.
>> + uart0 at c0000 {
>> + compatible = "brcm,bcm4760-pl011", "arm,pl011", "arm,primecell";
>> + reg = <0xc0000 0x1000>;
>> + interrupt-parent = <&vic0>;
>> + interrupts = <14>;
>> + };
>> +
>> + uart1 at c1000 {
>> + compatible = "brcm,bcm4760-pl011", "arm,pl011", "arm,primecell";
>> + reg = <0xc1000 0x1000>;
>> + interrupt-parent = <&vic0>;
>> + interrupts = <15>;
>> + };
>> +
>> + uart2 at b2000 {
>> + compatible = "brcm,bcm4760-pl011", "arm,pl011", "arm,primecell";
>> + reg = <0xb2000 0x1000>;
>> + interrupt-parent = <&vic0>;
>> + interrupts = <16>;
>> + };
>> + };
>
>Please change the names here to say "serial" rather than "uartX". The
>name should not
>have an index in it (that's what the @address part is for) and there
>are conventions
>for common devices.
ok, will fix
>If some of the serial ports are not connected on all boars, best mark
>them as
>status="disabled"; here and only enable them in the board specific
>file.
uhm.. interesting
>> +config ARCH_BCM4760
>> + bool "Broadcom BCM4760 based SoCs (ARM11)" if ARCH_MULTI_V6
>> + select ARCH_WANT_OPTIONAL_GPIOLIB
>> + select ARM_AMBA
>> + select ARM_VIC
>> + select CLKDEV_LOOKUP
>> + select CLKSRC_OF
>> + select COMMON_CLK
>> + select CPU_V6
>> + select GENERIC_CLOCKEVENTS
>> + select GENERIC_IRQ_CHIP
>> + select MULTI_IRQ_HANDLER
>> + select NO_IOPORT
>> + select PINCTRL
>> + select PINMUX
>> + select SPARSE_IRQ
>> + select USE_OF
>
>A lot of these are implied by ARCH_MULTIPLATFORM or ARCH_MULTI_V6 and
>can be removed
>here. I don't think you should select 'PINCTRL and PINMUX' here, as
>long as the code
>builds without them.
>
> Arnd
>
>_______________________________________________
>linux-arm-kernel mailing list
>linux-arm-kernel at lists.infradead.org
>http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
More information about the linux-arm-kernel
mailing list