On 10/09/13 20:24, Joel Fernandes wrote: > Here are last few patches required to add EDMA and MMC/SPI support for AM33xx. > > Now that all dependent DMA patches and fixes are in linux next or mainline, except > for [1] which should go in for 3.12 -rc cycle, it is safe to enable MMC and SPI support > and this patch series enables it. These are originally Matt Porter's patches with > changes to make it work with recent kernels, addition of irq, memory resources and > enable other extra properties. > > These patches should cleanly apply on master branch after Koen's patch [2] for basic > BBB DT support is applied. > > MMC support is enabled for: Beaglebone, AM335x EVM and EVM-SK boards. MMC support > for BBB is intentionally not added due to custom fixes and other patches that are > in Koen's tree and which will be separately submitted by him. > > [1] http://marc.info/?l=linux-omap&m=137883926226451&w=2 > [2] http://comments.gmane.org/gmane.linux.kernel.stable/63648 > > Matt Porter (3): > ARM: dts: add AM33XX EDMA support > ARM: dts: add AM33XX SPI DMA support > ARM: dts: add AM33XX MMC support and documentation > > .../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 26 +++++++++- > arch/arm/boot/dts/am335x-bone.dts | 11 ++++ > arch/arm/boot/dts/am335x-evm.dts | 7 +++ > arch/arm/boot/dts/am335x-evmsk.dts | 7 +++ > arch/arm/boot/dts/am33xx.dtsi | 60 ++++++++++++++++++++++ > 5 files changed, 110 insertions(+), 1 deletion(-) This is not (quite) working for me on our custom AM335x board. Everything compiles fine, but I get the following in the boot log:- [ 1.339805] omap_hsmmc 48060000.mmc: vmmc regulator missing I can see that the regulator *does* get enabled, but later on in the boot process !! [ 1.568731] DCDC1: at 1500 mV [ 1.574454] vdd_mpu: 925 <--> 1325 mV at 1100 mV [ 1.581754] vdd_core: 925 <--> 1150 mV at 1100 mV [ 1.589093] LDO1: at 1800 mV [ 1.594515] LDO2: at 3300 mV [ 1.599820] LDO3: 1800 <--> 3300 mV at 1800 mV [ 1.606872] LDO4: at 3300 mV [ 1.611901] tps65217 0-0024: TPS65217 ID 0xe version 1.2 I can only think this is the cause of the issue. However ... cards plugged into the sd card slot are seen and are mount-able. I've attached my board dts and .config if that helps. Any clues ? Cheers Mark J.