musb module names in 4.4.0-rc7
Hi Felipe, Using the openSUSE kernel config [1] I've noticed the following modules get built for recent RCs: /lib/modules/4.4.0-rc7-1.g276c9f4-lpae/kernel/drivers/usb/musb> ls am35x.ko musb_am335x.ko musb_dsps.ko musb_hdrc.ko omap2430.ko sunxi.ko In my case I was testing on a sun9i based Optimus Board and needed to specify "sunxi" as driver for dracut to add to my initrd for USB root. Shouldn't that rather be "musb_sunxi" for module name uniqueness? Same issue with am35x and omap2430 above, I guess. Cheers and Happy New Year, Andreas [1] http://kernel.opensuse.org/cgit/kernel-source/tree/config/armv7hl -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- 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
Re: [RFC] adp1653: Add device tree bindings for LED controller
Hi Pavel, Am 16.11.2014 um 08:59 schrieb Pavel Machek: > For device tree people: Yes, I know I'll have to create file in > documentation, but does the binding below look acceptable? [...] > diff --git a/arch/arm/boot/dts/omap3-n900.dts > b/arch/arm/boot/dts/omap3-n900.dts > index 739fcf2..ed0bfc1 100644 > --- a/arch/arm/boot/dts/omap3-n900.dts > +++ b/arch/arm/boot/dts/omap3-n900.dts > @@ -553,6 +561,18 @@ > > ti,usb-charger-detection = <&isp1704>; > }; > + > + adp1653: adp1653@30 { This should probably be led-controller@30 (a generic description not specific to the model). The label name is fine. > + compatible = "ad,adp1653"; > + reg = <0x30>; > + > + max-flash-timeout-usec = <50>; > + max-flash-intensity-uA= <32>; > + max-torch-intensity-uA = <5>; > + max-indicator-intensity-uA = <17500>; > + > + gpios = <&gpio3 24 GPIO_ACTIVE_HIGH>; /* Want 88 */ At least to me, the meaning of "Want 88" is not clear - drop or clarify? > + }; > }; > > &i2c3 { [snip] Regards, Andreas -- SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg -- 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
Re: dtb size limit? was Re: Tiny dts change breaks boot on n900
Am 10.11.2014 um 12:58 schrieb Pavel Machek: > If I replace the blo[ck] below with > > a = <1>; > b = <2>; > c = <3>; > d = <4>; > > Resulting kernel boots. Replacing it with > > a-really-long-attribute-name-hopefully-this-breaks-stuff = <1>; > b = <2>; > c = <3>; > d = <4>; > > Breaks the boot. I'm using dtb append option. Any ideas? Nonbooting > dtb is 68910 bytes. Did you verify that your initrd, if any, does not overlap the end of the kernel when loading it from the bootloader? Andreas -- SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg -- 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
Re: [PATCH POST V2] ARM: dts: Add am57xx-beagle-x15
Hi, Am 07.11.2014 um 18:47 schrieb Nishanth Menon: > BeagleBoard-X15 is the next generation Open Source Hardware > BeagleBoard based on TI's AM5728 SoC featuring dual core 1.5GHz A15 > processor. The platform features 2GB DDR3L (w/dual 32bit busses), > eSATA, 3 USB3.0 ports, integrated HDMI (1920x1080@60), separate LCD > port, video In port, 4GB eMMC, uSD, Analog audio in/out, dual 1G > Ethernet. > > For more information, refer to: > BeagleBoard-X15 Wiki: > http://www.elinux.org/Beagleboard:BeagleBoard-X15 That page is very empty... is it the correct URL? Regards, Andreas -- SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg -- 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