On Saturday 14 March 2009, Steve Sakoman wrote: > On Sat, Mar 14, 2009 at 12:08 PM, David Brownell <david-b@xxxxxxxxxxx> wrote: > > On Saturday 14 March 2009, Tony Lindgren wrote: > >> > >> > I've collected Dave's recent recent regulator patches and will try > >> > again with those applied. > >> > >> Thanks, let me know what we're missing in l-o tree.. I probably > >> won't have a chance to look at it until Monday. > > > > I suggest this as the current solution ... though the "right" > > long term fix is still an open question. > > > > The basic problem is that still-unfixed goofage in the regulator > > framework: it seriously mis-handles regulators that bootloaders > > leave enabled. This can be teased apart into at least two bugs, > > possibly as many as four. The fix for one of them is queued in > > the regulator-next tree. > > > > One workable solution is to use the twl4030-power driver to > > initialize power resources including VMMC1 (I'll send a sample > > patch) but that requires lots of per-board updates. That will > > remove the need for regulator-core fixes. > > Dave, > > I tried another build with three of your patches that didn't seem to > applied yet: > > 1. This patch hooks up the twl4030 MMC1 regulator on Overo . . . Right. > 2. Make the regulator setup code simpler and more consistent . . . Which I sent on this thread. > 3. Fix some refcounting issues in the regulator framework . . . Not sure which one that is. Sounds like one that I sent against regulator-next, which wouldn't be needed given #2 above (regulator-next has two refcount fix patches). > My build also includes a patch for DSS2, but I don't believe that to > be an issue. Right. > I don't get the warning now, but mmc0 is still broken (boot log below) Works for me, and I think you've got all the patches that should matter. This is against today's GIT, yes? Does taking #3 away help? > Steve > > Linux version 2.6.29-rc8-omap1 (sakoman@tera) (gcc version 4.3.1 (GCC) > ) #1 Sat Mar 14 11:23:06 PDT 2009 > CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=10c5387f > CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache > Machine: Gumstix Overo > omapfb_early_vram, 12582912, 0x0 > Memory policy: ECC disabled, Data cache writeback > OMAP3430 ES2.1 I hear ES3.1 will have better-working EHCI. ;) > SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000 > Reserving 12582912 bytes SDRAM for VRAM > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 > Kernel command line: console=ttyS2,115200n8 vram=12M > omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y omapdss.def_disp=dvi > root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait > Clocking rate (Crystal/DPLL/ARM core): 26.0/331/500 MHz > GPMC revision 5.0 > IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts > Total of 96 interrupts on 1 active controller > OMAP34xx GPIO hardware version 2.5 > PID hash table entries: 512 (order: 9, 2048 bytes) > OMAP clockevent source: GPTIMER1 at 32768 Hz > Console: colour dummy device 80x30 > Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) > Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) > Memory: 128MB = 128MB total > Memory: 111516KB available (4468K code, 531K data, 936K init) > Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696) > Mount-cache hash table entries: 512 > CPU: Testing write buffer coherency: ok > net_namespace: 764 bytes > regulator: core version 0.5 > NET: Registered protocol family 16 > Found NAND on CS0 > Registering NAND on CS0 > OMAP DMA hardware revision 4.0 > bio: create slab <bio-0> at 0 > OMAP DSS rev 2.0 > OMAP DISPC rev 3.0 > OMAP VENC rev 2 > i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz > twl4030: PIH (irq 7) chaining IRQs 368..375 > twl4030: power (irq 373) chaining IRQs 376..383 > twl4030: gpio (irq 368) chaining IRQs 384..401 > set_machine_constraints: disable 'VMMC1' --> 0 So the initial state is as expected, good ... > regulator: VMMC1: 1850 <--> 3150 mV normal standby > set_machine_constraints: disable 'VUSB1V5' --> 0 > regulator: VUSB1V5: 1500 <--> 0 mV normal standby > set_machine_constraints: disable 'VUSB1V8' --> 0 > regulator: VUSB1V8: 1800 <--> 0 mV normal standby > set_machine_constraints: disable 'VUSB3V1' --> 0 > regulator: VUSB3V1: 3100 <--> 0 mV normal standby > i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz > SCSI subsystem initialized > twl4030_usb twl4030_usb: Initialized TWL4030 USB module > usbcore: registered new interface driver usbfs > usbcore: registered new interface driver hub > usbcore: registered new device driver usb > Bluetooth: Core ver 2.14 > NET: Registered protocol family 31 > Bluetooth: HCI device and connection manager initialized > Bluetooth: HCI socket layer initialized > cfg80211: Using static regulatory domain info > cfg80211: Regulatory domain: US > (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) > (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm) > (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm) > cfg80211: Calling CRDA for country: US > musb_hdrc: version 6.0, musb-dma, host, debug=0 > musb_hdrc: USB Host mode controller at d80ab000 using DMA, IRQ 92 > musb_hdrc musb_hdrc: MUSB HDRC host driver > musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1 > usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 > usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 > usb usb1: Product: MUSB HDRC host driver > usb usb1: Manufacturer: Linux 2.6.29-rc8-omap1 musb-hcd > usb usb1: SerialNumber: musb_hdrc > usb usb1: configuration #1 chosen from 1 choice > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 1 port detected > NET: Registered protocol family 2 > IP route cache hash table entries: 1024 (order: 0, 4096 bytes) > TCP established hash table entries: 4096 (order: 3, 32768 bytes) > TCP bind hash table entries: 4096 (order: 2, 16384 bytes) > TCP: Hash tables configured (established 4096 bind 4096) > TCP reno registered > NET: Registered protocol family 1 > VFS: Disk quotas dquot_6.5.2 > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. > msgmni has been set to 218 > alg: No test for stdrng (krng) > io scheduler noop registered > io scheduler anticipatory registered (default) > io scheduler deadline registered > io scheduler cfq registered > Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled > serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 > serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 > serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654 > console [ttyS2] enabled > brd: module loaded > loop: module loaded > usbcore: registered new interface driver asix > usbcore: registered new interface driver cdc_ether > i2c /dev entries driver > Driver 'sd' needs updating - please use bus_type methods > omap2-nand driver initializing > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB > 1,8V 16-bit) > cmdlinepart partition parsing not available > Creating 5 MTD partitions on "omap2-nand": > 0x000000000000-0x000000080000 : "xloader" > 0x000000080000-0x000000240000 : "uboot" > 0x000000240000-0x000000280000 : "uboot environment" > 0x000000280000-0x000000680000 : "linux" > 0x000000680000-0x000010000000 : "rootfs" > ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > ehci-omap ehci-omap.0: OMAP-EHCI Host Controller > ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2 > ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 > ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00 > usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 > usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 > usb usb2: Product: OMAP-EHCI Host Controller > usb usb2: Manufacturer: Linux 2.6.29-rc8-omap1 ehci_hcd > usb usb2: SerialNumber: ehci-omap.0 > usb usb2: configuration #1 chosen from 1 choice > hub 2-0:1.0: USB hub found > hub 2-0:1.0: 3 ports detected > Initializing USB Mass Storage driver... > usbcore: registered new interface driver usb-storage > USB Mass Storage support registered. > udc: OMAP UDC driver, version: 4 October 2004 (iso) (dma) > mice: PS/2 mouse device common for all mice > twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0 > twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC. > OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec > Bluetooth: HCI UART driver ver 2.2 > Bluetooth: HCI H4 protocol initialized > Bluetooth: HCI BCSP protocol initialized > Bluetooth: Broadcom Blutonium firmware driver ver 1.2 > usbcore: registered new interface driver bcm203x > Bluetooth: Digianswer Bluetooth USB driver ver 0.10 > usbcore: registered new interface driver bpa10x > sdhci: Secure Digital Host Controller Interface driver > sdhci: Copyright(c) Pierre Ossman Why do you have SDHCI configured?? > mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock > regulator: Unable to get requested regulator: vmmc_aux Right -- mmci-omap-hs.0 only has vmmc (twl4030 VMMC1). > mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock > regulator: Unable to get requested regulator: vmmc And mmci-omap-hs.1 doesn't have any regulators at all; a "fixed.c" regulator would make sense, but it's not going to be usable till 2.6.30. > mmc_rescan: card ocr from io_op=0x90ff8000, err = 0 Nothing looking odd there, although ISTR complaints about the debounce clock are recent additions. Which slot reports that mmc_rescan() thing though? I take it that's your diagnostic. More important ... why are you only getting one such message? I hope you really *do* have an uSD card in that slot. ;) Try sticking diagnostics where it's checking whether there is a card in the slot. And then where it turns on the regulator for mmc0 ... I'm thinking the latter doesn't seem to be happening, > usbcore: registered new interface driver usbhid > usbhid: v2.6:USB HID core driver > Advanced Linux Sound Architecture Driver Version 1.0.18a. > usbcore: registered new interface driver snd-usb-audio > No device for DAI twl4030 > No device for DAI omap-mcbsp-dai-0 > No device for DAI omap-mcbsp-dai-1 > No device for DAI omap-mcbsp-dai-2 > No device for DAI omap-mcbsp-dai-3 > No device for DAI omap-mcbsp-dai-4 > overo SoC init > TWL4030 Audio Codec init > asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok > ALSA device list: > #0: overo (twl4030) > oprofile: using arm/armv7 > TCP cubic registered > NET: Registered protocol family 17 > NET: Registered protocol family 15 > Bluetooth: L2CAP ver 2.11 > Bluetooth: L2CAP socket layer initialized > Bluetooth: SCO (Voice Link) ver 0.6 > Bluetooth: SCO socket layer initialized > Bluetooth: RFCOMM socket layer initialized > Bluetooth: RFCOMM TTY layer initialized > Bluetooth: RFCOMM ver 1.10 > Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > Bluetooth: BNEP filters: protocol multicast > Bluetooth: HIDP (Human Interface Emulation) ver 1.2 > RPC: Registered udp transport module. > RPC: Registered tcp transport module. > ThumbEE CPU extension supported. > Power Management for TI OMAP3. > SmartReflex driver initialized > VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 > fbcvt: 1024x768@60: CVT Name - .786M3-R > Console: switching to colour frame buffer device 128x48 > clock: clksel_round_rate_div: dpll4_m4_ck target_rate 86400000 > clock: new_div = 5, new_rate = 86400000 I don't hook up the framebuffer, but here I get an MMC diagnostic I've added: mmc0: voltage mask 0f0000 (orig ff8000, use 010000) > twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:00:00 > UTC (946684800) > Waiting for root device /dev/mmcblk0p2... > mmc1: new SDIO card at address 0001 > > At that point I get: Waiting for root device /dev/mmcblk0p2... mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SD card at address 3395 mmcblk0: mmc0:3395 SD02G 1.83 GiB mmcblk0: p1 p2 mmc1: voltage mask 100000 (orig ff8000, use 100000) usb 2-1: new high speed USB device using musb_hdrc and address 2 mmc1: new SDIO card at address 0001 libertas_sdio mmc1:0001:1: firmware: using built-in firmware sd8686_helper.bin libertas_sdio mmc1:0001:1: firmware: using built-in firmware sd8686.bin -- 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
