* Pavel Machek <pavel@xxxxxx> [141029 01:48]: > > Speaking of testing: > > I'm not sure what is omap_l3_smx neccessary for, but it does not work. > > [ 0.223297] omap_l3_smx omap_l3_smx.0: couldn't request debug irq > [ 0.223419] omap_l3_smx: probe of omap_l3_smx.0 failed with error > -22 Hmm this should be fixed to get interrupts about invalid bus access. > There is some fun in pinmuxing: > > [ 0.247131] irq: no irq domain found for /ocp/pinmux@48002030 ! > [ 0.248291] irq: no irq domain found for /ocp/pinmux@48002030 ! > ... > [ 0.384826] omap_i2c 48070000.i2c: could not find pctldev for node > /ocp/pinmux@48002030/pinmux_i\ > 2c1_pins, deferring probe > [ 0.384918] platform 48070000.i2c: Driver omap_i2c requests probe > deferral > [ 0.385070] omap_i2c 48072000.i2c: could not find pctldev for node > /ocp/pinmux@48002030/pinmux_i\ > 2c2_pins, deferring probe > [ 0.385162] platform 48072000.i2c: Driver omap_i2c requests probe > deferral > [ 0.385284] omap_i2c 48060000.i2c: could not find pctldev for node > /ocp/pinmux@48002030/pinmux_i\ > 2c3_pins, deferring probe > [ 0.385375] platform 48060000.i2c: Driver omap_i2c requests probe > deferral These are related to deferred probe and should go away when we make drivers/i2c/busses/i2c-omap.c to use regular module_init and stop using subsys_initcall. But I think legacy booting still needs it early, could be omap1 only nowadays though. > And serial has some problems: > > [ 0.482208] of_get_named_gpiod_flags: can't parse 'rts-gpio' > property of node '/ocp/serial@4806c\ > 000[0]' > [ 0.482513] omap_uart 4806c000.serial: ttyO1 at MMIO 0x4806c000 > (irq = 223, base_baud = 3000000)\ > is a OMAP UART1 > [ 0.484588] of_get_named_gpiod_flags: can't parse 'rts-gpio' > property of node '/ocp/serial@49020\ > 000[0]' > [ 0.484771] omap_uart 49020000.serial: ttyO2 at MMIO 0x49020000 > (irq = 224, base_baud = 3000000)\ > is a OMAP UART2 I these come from the GPIO framework when booting with debug enabled. > There's a lot of noise from probe defferal :-(. And it looks like mmc > properties have some problems: > > [ 0.739349] of_get_named_gpiod_flags: can't parse 'wp-gpios' > property of node '/ocp/mmc@4809c000\ > [0]' > [ 0.740142] omap_hsmmc 4809c000.mmc: unable to get vmmc regulator > -517 > [ 0.740386] platform 4809c000.mmc: Driver omap_hsmmc requests probe > deferral > [ 0.740661] of_get_named_gpiod_flags: can't parse 'cd-gpios' > property of node '/ocp/mmc@480b4000\ > [0]' > [ 0.740692] of_get_named_gpiod_flags: can't parse 'wp-gpios' > property of node '/ocp/mmc@480b4000\ > [0]' These too. But yeah, I agree, let's try to patch away some of the deferred probe noise. > omapfb reports problems, but seems to work ok: > > [ 0.990386] omapfb omapfb: cannot parse default modes > [ 1.004791] Console: switching to colour frame buffer device 100x30 > [ 1.073150] omapfb omapfb: using display 'lcd' mode 800x480 Tomi, is the default mode warning correct here? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
