* Arnaud Patard <arnaud.patard@xxxxxxxxxxx> [130619 02:52]: > Tony Lindgren <tony@xxxxxxxxxxx> writes: > > Hi, > > > * Tony Lindgren <tony@xxxxxxxxxxx> [130617 03:32]: > >> * Arnaud Patard <arnaud.patard@xxxxxxxxxxx> [130617 02:52]: > >> > Tony Lindgren <tony@xxxxxxxxxxx> writes: > >> > > >> > I understand your concerns but, please, cope with reality: the clock > >> > work is not in -next so this tends to make me think it won't reach > >> > 3.11. We're at -rc6 after all. Telling users that their system doesn't > >> > have any network because it was easier to maintain, is not something > >> > they will understand imho. > >> > >> Right, like I said: the idea is to have it usable with DT. And USB and > >> Ethernet certainly are part of what I call usable. So is MMC, WLAN and > >> DSS. I've certainly spent quite a bit of time on making sure panda works > >> with DT, and I can assure you that fixing the USB extclock is easier than > >> supporting the legacy boot with DT :) > >> > >> This issue can also be fixed with a clock alias if we don't have DT > >> defined clocks ready for v3.11. It may take a few days for us to have > >> the solution. But get getting a clock to a driver certainly is not a > >> showstopper here. After all, that's what all drivers already do. > > > > Care to test the last patch just posted by Roger in thread > > " [PATCH 0/4] ARM: OMAP4: Panda USB Host support and DVI EDID fix"? > > I tried to test them but they don't apply on linux-next due to some > pinctrl changes probably missing: > Error: arch/arm/boot/dts/omap4-panda-common.dtsi:177.14-15 syntax error > > which corresponds to : > 0x82 (PIN_INPUT_PULLDOWN | MUX_MODE4) Oops, right, that's in Benoit's branch too for the .dts preprocessing. Until it is merged, maybe try with Roger's earlier version of that patch that did not yet use the macros? > Also, the patch 3 (ARM: dts: omap5-uevm: Provide USB Host PHY clock) > doesn't apply as the omap5-uevm.dts doesn't exist. OK that's in Benoit's branch. But you won't need that one. > Which tree should I use to test the patches if it's not linux-next ? > > Also, you might want to know that drivers/usb/musb/omap2430.c doesn't > build due to some typos (musb_resources vs musb_resouces). Thanks, I think Felipe is already aware of that. 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
