* [PATCH] Disable the non working eMMC on Zoom2/3 @ 2010-04-01 0:25 Madhusudhan Chikkature 2010-04-01 4:03 ` Ghorai, Sukumar 0 siblings, 1 reply; 21+ messages in thread From: Madhusudhan Chikkature @ 2010-04-01 0:25 UTC (permalink / raw) To: tony; +Cc: linux-omap, linux-mmc From: Madhusudhan Chikkature <madhu.cr@ti.com> Date: Wed, 31 Mar 2010 12:29:19 -0400 Subject: [PATCH] Zoom2/3: Disable MMC2 The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the writes to fail since the card size is not detected correctly by the MMC core. Disable the MMC2 support for Zoom2/3. Signed-off-by: Madhusudhan Chikkature <madhu.cr@ti.com> --- arch/arm/mach-omap2/board-zoom-peripherals.c | 30 -------------------------- 1 files changed, 0 insertions(+), 30 deletions(-) diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c b/arch/arm/mach-omap2/board-zoom-peripherals.c index 6b39849..ac791d2 100644 --- a/arch/arm/mach-omap2/board-zoom-peripherals.c +++ b/arch/arm/mach-omap2/board-zoom-peripherals.c @@ -102,10 +102,6 @@ static struct regulator_consumer_supply zoom_vsim_supply = { .supply = "vmmc_aux", }; -static struct regulator_consumer_supply zoom_vmmc2_supply = { - .supply = "vmmc", -}; - /* VMMC1 for OMAP VDD_MMC1 (i/o) and MMC1 card */ static struct regulator_init_data zoom_vmmc1 = { .constraints = { @@ -121,21 +117,6 @@ static struct regulator_init_data zoom_vmmc1 = { .consumer_supplies = &zoom_vmmc1_supply, }; -/* VMMC2 for MMC2 card */ -static struct regulator_init_data zoom_vmmc2 = { - .constraints = { - .min_uV = 1850000, - .max_uV = 1850000, - .apply_uV = true, - .valid_modes_mask = REGULATOR_MODE_NORMAL - | REGULATOR_MODE_STANDBY, - .valid_ops_mask = REGULATOR_CHANGE_MODE - | REGULATOR_CHANGE_STATUS, - }, - .num_consumer_supplies = 1, - .consumer_supplies = &zoom_vmmc2_supply, -}; - /* VSIM for OMAP VDD_MMC1A (i/o for DAT4..DAT7) */ static struct regulator_init_data zoom_vsim = { .constraints = { @@ -159,15 +140,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = { .gpio_wp = -EINVAL, .power_saving = true, }, - { - .name = "internal", - .mmc = 2, - .wires = 8, - .gpio_cd = -EINVAL, - .gpio_wp = -EINVAL, - .nonremovable = true, - .power_saving = true, - }, {} /* Terminator */ }; @@ -183,7 +155,6 @@ static int zoom_twl_gpio_setup(struct device *dev, */ zoom_vmmc1_supply.dev = mmc[0].dev; zoom_vsim_supply.dev = mmc[0].dev; - zoom_vmmc2_supply.dev = mmc[1].dev; return 0; } @@ -241,7 +212,6 @@ static struct twl4030_platform_data zoom_twldata = { .keypad = &zoom_kp_twl4030_data, .codec = &zoom_codec_data, .vmmc1 = &zoom_vmmc1, - .vmmc2 = &zoom_vmmc2, .vsim = &zoom_vsim, }; -- 1.6.3.3 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* RE: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-01 0:25 [PATCH] Disable the non working eMMC on Zoom2/3 Madhusudhan Chikkature @ 2010-04-01 4:03 ` Ghorai, Sukumar 2010-04-01 17:04 ` Madhusudhan 0 siblings, 1 reply; 21+ messages in thread From: Ghorai, Sukumar @ 2010-04-01 4:03 UTC (permalink / raw) To: Chikkature Rajashekar, Madhusudhan, tony@atomide.com Cc: linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org Madhu, > -----Original Message----- > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap- > owner@vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan > Sent: 2010-04-01 05:56 > To: tony@atomide.com > Cc: linux-omap@vger.kernel.org; linux-mmc@vger.kernel.org > Subject: [PATCH] Disable the non working eMMC on Zoom2/3 > > From: Madhusudhan Chikkature <madhu.cr@ti.com> > Date: Wed, 31 Mar 2010 12:29:19 -0400 > Subject: [PATCH] Zoom2/3: Disable MMC > > The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the > writes to fail since the card size is not detected correctly by the MMC > core. Disable the MMC2 support for Zoom2/3. [Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the exact problem. Because we never face any issue for eMMC in ZOOM3. Because we have the same eMMC device in 3630-SDP and could have the same problem. > > Signed-off-by: Madhusudhan Chikkature <madhu.cr@ti.com> > --- > arch/arm/mach-omap2/board-zoom-peripherals.c | 30 --------------------- > ----- > 1 files changed, 0 insertions(+), 30 deletions(-) > > diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c > b/arch/arm/mach-omap2/board-zoom-peripherals.c > index 6b39849..ac791d2 100644 > --- a/arch/arm/mach-omap2/board-zoom-peripherals.c > +++ b/arch/arm/mach-omap2/board-zoom-peripherals.c > @@ -102,10 +102,6 @@ static struct regulator_consumer_supply > zoom_vsim_supply = { > .supply = "vmmc_aux", > }; > > -static struct regulator_consumer_supply zoom_vmmc2_supply = { > - .supply = "vmmc", > -}; > - > /* VMMC1 for OMAP VDD_MMC1 (i/o) and MMC1 card */ > static struct regulator_init_data zoom_vmmc1 = { > .constraints = { > @@ -121,21 +117,6 @@ static struct regulator_init_data zoom_vmmc1 = { > .consumer_supplies = &zoom_vmmc1_supply, > }; > > -/* VMMC2 for MMC2 card */ > -static struct regulator_init_data zoom_vmmc2 = { > - .constraints = { > - .min_uV = 1850000, > - .max_uV = 1850000, > - .apply_uV = true, > - .valid_modes_mask = REGULATOR_MODE_NORMAL > - | REGULATOR_MODE_STANDBY, > - .valid_ops_mask = REGULATOR_CHANGE_MODE > - | REGULATOR_CHANGE_STATUS, > - }, > - .num_consumer_supplies = 1, > - .consumer_supplies = &zoom_vmmc2_supply, > -}; > - > /* VSIM for OMAP VDD_MMC1A (i/o for DAT4..DAT7) */ > static struct regulator_init_data zoom_vsim = { > .constraints = { > @@ -159,15 +140,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = { > .gpio_wp = -EINVAL, > .power_saving = true, > }, > - { > - .name = "internal", > - .mmc = 2, > - .wires = 8, > - .gpio_cd = -EINVAL, > - .gpio_wp = -EINVAL, > - .nonremovable = true, > - .power_saving = true, > - }, > {} /* Terminator */ > }; > > @@ -183,7 +155,6 @@ static int zoom_twl_gpio_setup(struct device *dev, > */ > zoom_vmmc1_supply.dev = mmc[0].dev; > zoom_vsim_supply.dev = mmc[0].dev; > - zoom_vmmc2_supply.dev = mmc[1].dev; > > return 0; > } > @@ -241,7 +212,6 @@ static struct twl4030_platform_data zoom_twldata = { > .keypad = &zoom_kp_twl4030_data, > .codec = &zoom_codec_data, > .vmmc1 = &zoom_vmmc1, > - .vmmc2 = &zoom_vmmc2, > .vsim = &zoom_vsim, > > }; > -- > 1.6.3.3 > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-01 4:03 ` Ghorai, Sukumar @ 2010-04-01 17:04 ` Madhusudhan 2010-04-01 18:34 ` Ghorai, Sukumar 0 siblings, 1 reply; 21+ messages in thread From: Madhusudhan @ 2010-04-01 17:04 UTC (permalink / raw) To: 'Ghorai, Sukumar', tony; +Cc: linux-omap, linux-mmc [-- Attachment #1: Type: text/plain, Size: 4266 bytes --] > -----Original Message----- > From: Ghorai, Sukumar [mailto:s-ghorai@ti.com] > Sent: Wednesday, March 31, 2010 11:03 PM > To: Chikkature Rajashekar, Madhusudhan; tony@atomide.com > Cc: linux-omap@vger.kernel.org; linux-mmc@vger.kernel.org > Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3 > > Madhu, > > > -----Original Message----- > > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap- > > owner@vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan > > Sent: 2010-04-01 05:56 > > To: tony@atomide.com > > Cc: linux-omap@vger.kernel.org; linux-mmc@vger.kernel.org > > Subject: [PATCH] Disable the non working eMMC on Zoom2/3 > > > > From: Madhusudhan Chikkature <madhu.cr@ti.com> > > Date: Wed, 31 Mar 2010 12:29:19 -0400 > > Subject: [PATCH] Zoom2/3: Disable MMC > > > > The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the > > writes to fail since the card size is not detected correctly by the MMC > > core. Disable the MMC2 support for Zoom2/3. > > > [Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the exact > problem. Because we never face any issue for eMMC in ZOOM3. Because we > have the same eMMC device in 3630-SDP and could have the same problem. > On Zoom3 the EXT_CSD Rev reported by eMMC is zero. See the log attached. Hence the failures which are reported by people on the list. I had already bought this problem up on the list previously and was discussed, right? >From the log you can also see that a 16GB device is detected as a 1GB. Regards, Madhu > > > > Signed-off-by: Madhusudhan Chikkature <madhu.cr@ti.com> > > --- > > arch/arm/mach-omap2/board-zoom-peripherals.c | 30 ------------------- > -- > > ----- > > 1 files changed, 0 insertions(+), 30 deletions(-) > > > > diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c > > b/arch/arm/mach-omap2/board-zoom-peripherals.c > > index 6b39849..ac791d2 100644 > > --- a/arch/arm/mach-omap2/board-zoom-peripherals.c > > +++ b/arch/arm/mach-omap2/board-zoom-peripherals.c > > @@ -102,10 +102,6 @@ static struct regulator_consumer_supply > > zoom_vsim_supply = { > > .supply = "vmmc_aux", > > }; > > > > -static struct regulator_consumer_supply zoom_vmmc2_supply = { > > - .supply = "vmmc", > > -}; > > - > > /* VMMC1 for OMAP VDD_MMC1 (i/o) and MMC1 card */ > > static struct regulator_init_data zoom_vmmc1 = { > > .constraints = { > > @@ -121,21 +117,6 @@ static struct regulator_init_data zoom_vmmc1 = { > > .consumer_supplies = &zoom_vmmc1_supply, > > }; > > > > -/* VMMC2 for MMC2 card */ > > -static struct regulator_init_data zoom_vmmc2 = { > > - .constraints = { > > - .min_uV = 1850000, > > - .max_uV = 1850000, > > - .apply_uV = true, > > - .valid_modes_mask = REGULATOR_MODE_NORMAL > > - | REGULATOR_MODE_STANDBY, > > - .valid_ops_mask = REGULATOR_CHANGE_MODE > > - | REGULATOR_CHANGE_STATUS, > > - }, > > - .num_consumer_supplies = 1, > > - .consumer_supplies = &zoom_vmmc2_supply, > > -}; > > - > > /* VSIM for OMAP VDD_MMC1A (i/o for DAT4..DAT7) */ > > static struct regulator_init_data zoom_vsim = { > > .constraints = { > > @@ -159,15 +140,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = { > > .gpio_wp = -EINVAL, > > .power_saving = true, > > }, > > - { > > - .name = "internal", > > - .mmc = 2, > > - .wires = 8, > > - .gpio_cd = -EINVAL, > > - .gpio_wp = -EINVAL, > > - .nonremovable = true, > > - .power_saving = true, > > - }, > > {} /* Terminator */ > > }; > > > > @@ -183,7 +155,6 @@ static int zoom_twl_gpio_setup(struct device *dev, > > */ > > zoom_vmmc1_supply.dev = mmc[0].dev; > > zoom_vsim_supply.dev = mmc[0].dev; > > - zoom_vmmc2_supply.dev = mmc[1].dev; > > > > return 0; > > } > > @@ -241,7 +212,6 @@ static struct twl4030_platform_data zoom_twldata = { > > .keypad = &zoom_kp_twl4030_data, > > .codec = &zoom_codec_data, > > .vmmc1 = &zoom_vmmc1, > > - .vmmc2 = &zoom_vmmc2, > > .vsim = &zoom_vsim, > > > > }; > > -- > > 1.6.3.3 > > > > > > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html [-- Attachment #2: EXT_CSD_REV_ZOOM3.TXT --] [-- Type: text/plain, Size: 10835 bytes --] dhcp 0x80000000 madhu/uImagelo LAN9x18 (0x92210000) detected. Read mac address: 00:08:EE:03:2A:5B start Auto negotiation... (take ~2sec) Auto negotiation complete, 100BaseTX, full duplex BOOTP broadcast 1 *** Unhandled DHCP Option in OFFER/ACK: 43 *** Unhandled DHCP Option in OFFER/ACK: 44 *** Unhandled DHCP Option in OFFER/ACK: 46 *** Unhandled DHCP Option in OFFER/ACK: 43 *** Unhandled DHCP Option in OFFER/ACK: 44 *** Unhandled DHCP Option in OFFER/ACK: 46 DHCP client bound to address 128.247.79.222 TFTP from server 128.247.75.101; our IP address is 128.247.79.222; sending through gateway 128.247.78.2 Filename 'madhu/uImagelo'. Load address: 0x80000000 Loading: *\b################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ############################################################ done Bytes transferred = 1968152 (1e0818 hex) OMAP36XX ZOOM3 # bootm ## Booting image at 80000000 ... Image Name: Linux-2.6.34-rc3-07875-geba0147- Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1968088 Bytes = 1.9 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Linux version 2.6.34-rc3-07875-geba0147-dirty (madhu@praneeth) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #7 Thu Apr 1 12:17:57 EDT 2010 CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: OMAP Zoom3 board Memory policy: ECC disabled, Data cache writeback OMAP3630 ES1.0 (l2cache iva sgx neon isp 192mhz_clk ) SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: console=ttyS0,115200n8 noinitrd root=/dev/nfs rw nfsroot=128.247.75.252:/filesystems/madhu/target,nolock,tcp,tcp,wsize=1024,rsize=1024 ip=dhcp devfs=mount PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 256MB 256MB = 512MB total Memory: 515812k/515812k available, 8476k reserved, 0K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xffc00000 - 0xffe00000 ( 2 MB) vmalloc : 0xe0800000 - 0xf8000000 ( 376 MB) lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) modules : 0xbf000000 - 0xc0000000 ( 16 MB) .init : 0xc0008000 - 0xc002c000 ( 144 kB) .text : 0xc002c000 - 0xc0378000 (3376 kB) .data : 0xc0396000 - 0xc03cab80 ( 211 kB) Hierarchical RCU implementation. NR_IRQS:402 Clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz (null): Could not get uart4_ick (null): Could not get uart4_fck Reprogramming SDRC clock to 400000000 Hz GPMC revision 5.0 IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts Total of 96 interrupts on 1 active controller OMAP GPIO hardware version 2.5 OMAP clockevent source: GPTIMER1 at 32768 Hz Console: colour dummy device 80x30 Calibrating delay loop... 597.64 BogoMIPS (lpj=2334720) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok regulator: core version 0.5 NET: Registered protocol family 16 mux: Unknown ball offset 0x5e mux: Unknown ball offset 0x60 mux: Unknown ball offset 0x62 mux: Unknown ball offset 0x64 mux: Unknown ball offset 0x66 mux: Unknown ball offset 0x68 mux: Unknown ball offset 0x6a mux: Unknown ball offset 0x6c mux: Unknown ball offset 0x90 mux: Unknown ball offset 0x7e mux: Unknown ball offset 0x92 mux: Unknown ball offset 0x94 mux: Unknown ball offset 0x9c mux: Unknown ball offset 0x18a mux: Unknown ball offset 0x18c mux: Unknown ball offset 0xa1e mux: Unknown ball offset 0x9ee mux: Unknown ball offset 0x9f2 mux: Unknown ball offset 0xa20 mux: Unknown ball offset 0x9f0 mux: Unknown ball offset 0x574 mux: Unknown ball offset 0x576 mux: Unknown ball offset 0x588 mux: Unknown ball offset 0x58a mux: Unknown ball offset 0x58c mux: Unknown ball offset 0x58e mux: Unknown ball offset 0x590 mux: Unknown ball offset 0x578 mux: Unknown ball offset 0x57a mux: Unknown ball offset 0x57c mux: Unknown ball offset 0x57e mux: Unknown ball offset 0x580 mux: Unknown ball offset 0x582 mux: Unknown ball offset 0x584 mux: Unknown ball offset 0x586 mux: Unknown ball offset 0x570 mux: Unknown ball offset 0x572 mux: Unknown ball offset 0x40 mux: Unknown ball offset 0x0 mux: Unknown ball offset 0x2 mux: Unknown ball offset 0x14 mux: Unknown ball offset 0x16 mux: Unknown ball offset 0x18 mux: Unknown ball offset 0x1a mux: Unknown ball offset 0x1c mux: Unknown ball offset 0x1e mux: Unknown ball offset 0x20 mux: Unknown ball offset 0x22 mux: Unknown ball offset 0x24 mux: Unknown ball offset 0x26 mux: Unknown ball offset 0x4 mux: Unknown ball offset 0x28 mux: Unknown ball offset 0x2a mux: Unknown ball offset 0x2c mux: Unknown ball offset 0x2e mux: Unknown ball offset 0x30 mux: Unknown ball offset 0x32 mux: Unknown ball offset 0x34 mux: Unknown ball offset 0x36 mux: Unknown ball offset 0x38 mux: Unknown ball offset 0x3a mux: Unknown ball offset 0x6 mux: Unknown ball offset 0x3c mux: Unknown ball offset 0x3e mux: Unknown ball offset 0x8 mux: Unknown ball offset 0xa mux: Unknown ball offset 0xc mux: Unknown ball offset 0xe mux: Unknown ball offset 0x10 mux: Unknown ball offset 0x12 mux: Unknown ball offset 0x59e mux: Unknown ball offset 0x5a0 mux: Unknown ball offset 0x5a2 mux: Unknown ball offset 0x5a4 mux: Unknown ball offset 0x42 mux: Unknown ball offset 0x44 mux: Unknown ball offset 0x46 mux: Unknown ball offset 0x48 mux: Unknown ball offset 0x59a mux: Unknown ball offset 0x596 mux: Unknown ball offset 0x592 mux: Unknown ball offset 0x594 mux: Unknown ball offset 0x598 mux: Unknown ball offset 0x59c mux: Unknown ball offset 0x9d4 OMAP DMA hardware revision 5.0 bio: create slab <bio-0> at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb i2c_omap i2c_omap.1: bus 1 rev4.0 at 2400 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 regulator: VUSB1V5: 1500 mV normal standby regulator: VUSB1V8: 1800 mV normal standby regulator: VUSB3V1: 3100 mV normal standby twl4030_usb twl4030_usb: Initialized TWL4030 USB module regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby regulator: VMMC2: 1850 mV normal standby regulator: VSIM: 1800 <--> 3000 mV at 1800 mV normal standby i2c_omap i2c_omap.2: bus 2 rev4.0 at 400 kHz i2c_omap i2c_omap.3: bus 3 rev4.0 at 400 kHz Advanced Linux Sound Architecture Driver Version 1.0.22.1. Switching to clocksource 32k_counter musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0 musb_hdrc musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92 NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. NetWinder Floating Point Emulator V0.97 (double precision) VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) msgmni has been set to 1007 alg: No test for stdrng (krng) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled serial8250.0: ttyS0 at MMIO 0x10000000 (irq = 262) is a ST16654 console [ttyS0] enabled brd: module loaded loop: module loaded smsc911x: Driver version 2008-10-21. smsc911x-mdio: probed eth0: attached PHY driver [SMSC LAN8700] (mii_bus:phy_addr=ffffffff:01, irq=-1) net eth0: MAC Address: 00:08:ee:03:2a:5b Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. input: TWL4030 Keypad as /class/input/input0 twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 i2c /dev entries driver Driver for 1-wire Dallas network protocol. usbcore: registered new interface driver usbhid usbhid: USB HID core driver ALSA device list: No soundcards found. TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 17 NET: Registered protocol family 15 Power Management for TI OMAP3. VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 twl_rtc twl_rtc: setting system clock to 2000-01-07 17:10:01 UTC (947265001) ............ EXT CSD REV 0 mmc1: new high speed MMC card at address 0001 mmcblk0: mmc1:0001 STM16G 1.00 GiB mmcblk0: p1 p2 mmcblk0: p2 size 4294817100 exceeds device capacity, limited to end of disk net eth0: SMSC911x/921x identified at 0xe080c000, IRQ: 318 Sending DHCP requests .., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 128.247.79.222 IP-Config: Complete: device=eth0, addr=128.247.79.222, mask=255.255.254.0, gw=128.247.78.2, host=128.247.79.222, domain=am.dhcp.ti.com, nis-domain=(none), bootserver=0.0.0.0, rootserver=128.247.75.252, rootpath= Looking up port of RPC 100003/2 on 128.247.75.252 Looking up port of RPC 100005/1 on 128.247.75.252 VFS: Mounted root (nfs filesystem) on device 0:11. Freeing init memory: 144K ****************************************** Starting System Init for 12.0.1 Release: 12.0.1 ****************************************** Saving kernel ring buffer : OK Mounting devpts : OK Setting up networking Configuring lo : OK Configuring eth0 : OK - 128.247.79.222 Starting telnetd : OK Starting syslogd : OK Starting klogd : OK Mounting filesystems : mount: Mounting none on /dev/gadget failed: No such file or directory Please press Enter to activate this console. BusyBox v1.2.1 (2007.08.06-21:03+0000) Built-in shell (ash) Enter 'help' for a list of built-in commands. # ^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-01 17:04 ` Madhusudhan @ 2010-04-01 18:34 ` Ghorai, Sukumar 2010-04-01 21:59 ` Nishanth Menon 0 siblings, 1 reply; 21+ messages in thread From: Ghorai, Sukumar @ 2010-04-01 18:34 UTC (permalink / raw) To: Chikkature Rajashekar, Madhusudhan, tony@atomide.com Cc: linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org Madhusudhan, > -----Original Message----- > From: Chikkature Rajashekar, Madhusudhan > Sent: 2010-04-01 22:35 > To: Ghorai, Sukumar; tony@atomide.com > Cc: linux-omap@vger.kernel.org; linux-mmc@vger.kernel.org > Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3 > > > > > -----Original Message----- > > From: Ghorai, Sukumar [mailto:s-ghorai@ti.com] > > Sent: Wednesday, March 31, 2010 11:03 PM > > To: Chikkature Rajashekar, Madhusudhan; tony@atomide.com > > Cc: linux-omap@vger.kernel.org; linux-mmc@vger.kernel.org > > Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3 > > > > Madhu, > > > > > -----Original Message----- > > > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap- > > > owner@vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan > > > Sent: 2010-04-01 05:56 > > > To: tony@atomide.com > > > Cc: linux-omap@vger.kernel.org; linux-mmc@vger.kernel.org > > > Subject: [PATCH] Disable the non working eMMC on Zoom2/3 > > > > > > From: Madhusudhan Chikkature <madhu.cr@ti.com> > > > Date: Wed, 31 Mar 2010 12:29:19 -0400 > > > Subject: [PATCH] Zoom2/3: Disable MMC > > > > > > The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the > > > writes to fail since the card size is not detected correctly by the > MMC > > > core. Disable the MMC2 support for Zoom2/3. > > > > > > [Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the > exact > > problem. Because we never face any issue for eMMC in ZOOM3. Because we > > have the same eMMC device in 3630-SDP and could have the same problem. > > > > On Zoom3 the EXT_CSD Rev reported by eMMC is zero. See the log attached. > > Hence the failures which are reported by people on the list. I had already > bought this problem up on the list previously and was discussed, right? > From the log you can also see that a 16GB device is detected as a 1GB. [Ghorai] I feel it's an issue with eMMC in pilot-board. And production-board is working fine. And I feel outside TI people having production board only. And 16GB eMMC device is a very good size to work with different things. Otherwise we are talking about MMC#2 boot, eMMC boot, 16GB eMMC device in zoom,.. all these information in different page/ link looks very misleading information, if really having such problem. I the mean time I will check this in Pilot board too and think you checked in pilot board only. > > Regards, > Madhu > > > > > > > Signed-off-by: Madhusudhan Chikkature <madhu.cr@ti.com> > > > --- > > > arch/arm/mach-omap2/board-zoom-peripherals.c | 30 ----------------- > -- > > -- > > > ----- > > > 1 files changed, 0 insertions(+), 30 deletions(-) > > > > > > diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c > > > b/arch/arm/mach-omap2/board-zoom-peripherals.c > > > index 6b39849..ac791d2 100644 > > > --- a/arch/arm/mach-omap2/board-zoom-peripherals.c > > > +++ b/arch/arm/mach-omap2/board-zoom-peripherals.c > > > @@ -102,10 +102,6 @@ static struct regulator_consumer_supply > > > zoom_vsim_supply = { > > > .supply = "vmmc_aux", > > > }; > > > > > > -static struct regulator_consumer_supply zoom_vmmc2_supply = { > > > - .supply = "vmmc", > > > -}; > > > - > > > /* VMMC1 for OMAP VDD_MMC1 (i/o) and MMC1 card */ > > > static struct regulator_init_data zoom_vmmc1 = { > > > .constraints = { > > > @@ -121,21 +117,6 @@ static struct regulator_init_data zoom_vmmc1 = { > > > .consumer_supplies = &zoom_vmmc1_supply, > > > }; > > > > > > -/* VMMC2 for MMC2 card */ > > > -static struct regulator_init_data zoom_vmmc2 = { > > > - .constraints = { > > > - .min_uV = 1850000, > > > - .max_uV = 1850000, > > > - .apply_uV = true, > > > - .valid_modes_mask = REGULATOR_MODE_NORMAL > > > - | REGULATOR_MODE_STANDBY, > > > - .valid_ops_mask = REGULATOR_CHANGE_MODE > > > - | REGULATOR_CHANGE_STATUS, > > > - }, > > > - .num_consumer_supplies = 1, > > > - .consumer_supplies = &zoom_vmmc2_supply, > > > -}; > > > - > > > /* VSIM for OMAP VDD_MMC1A (i/o for DAT4..DAT7) */ > > > static struct regulator_init_data zoom_vsim = { > > > .constraints = { > > > @@ -159,15 +140,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = > { > > > .gpio_wp = -EINVAL, > > > .power_saving = true, > > > }, > > > - { > > > - .name = "internal", > > > - .mmc = 2, > > > - .wires = 8, > > > - .gpio_cd = -EINVAL, > > > - .gpio_wp = -EINVAL, > > > - .nonremovable = true, > > > - .power_saving = true, > > > - }, > > > {} /* Terminator */ > > > }; > > > > > > @@ -183,7 +155,6 @@ static int zoom_twl_gpio_setup(struct device *dev, > > > */ > > > zoom_vmmc1_supply.dev = mmc[0].dev; > > > zoom_vsim_supply.dev = mmc[0].dev; > > > - zoom_vmmc2_supply.dev = mmc[1].dev; > > > > > > return 0; > > > } > > > @@ -241,7 +212,6 @@ static struct twl4030_platform_data zoom_twldata = > { > > > .keypad = &zoom_kp_twl4030_data, > > > .codec = &zoom_codec_data, > > > .vmmc1 = &zoom_vmmc1, > > > - .vmmc2 = &zoom_vmmc2, > > > .vsim = &zoom_vsim, > > > > > > }; > > > -- > > > 1.6.3.3 > > > > > > > > > > > > -- > > > To unsubscribe from this list: send the line "unsubscribe linux-omap" > in > > > the body of a message to majordomo@vger.kernel.org > > > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-01 18:34 ` Ghorai, Sukumar @ 2010-04-01 21:59 ` Nishanth Menon 2010-04-01 22:58 ` Madhusudhan 0 siblings, 1 reply; 21+ messages in thread From: Nishanth Menon @ 2010-04-01 21:59 UTC (permalink / raw) To: Ghorai, Sukumar Cc: Chikkature Rajashekar, Madhusudhan, tony@atomide.com, linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org Ghorai, Sukumar had written, on 04/01/2010 01:34 PM, the following: >>>> -----Original Message----- >>>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap- >>>> owner@vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan >>>> Sent: 2010-04-01 05:56 >>>> To: tony@atomide.com >>>> Cc: linux-omap@vger.kernel.org; linux-mmc@vger.kernel.org >>>> Subject: [PATCH] Disable the non working eMMC on Zoom2/3 >>>> >>>> From: Madhusudhan Chikkature <madhu.cr@ti.com> >>>> Date: Wed, 31 Mar 2010 12:29:19 -0400 >>>> Subject: [PATCH] Zoom2/3: Disable MMC >>>> >>>> The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the >>>> writes to fail since the card size is not detected correctly by the >> MMC >>>> core. Disable the MMC2 support for Zoom2/3. >>> >>> [Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the >> exact >>> problem. Because we never face any issue for eMMC in ZOOM3. Because we >>> have the same eMMC device in 3630-SDP and could have the same problem. >>> >> On Zoom3 the EXT_CSD Rev reported by eMMC is zero. See the log attached. >> >> Hence the failures which are reported by people on the list. I had already >> bought this problem up on the list previously and was discussed, right? >> From the log you can also see that a 16GB device is detected as a 1GB. > > [Ghorai] I feel it's an issue with eMMC in pilot-board. And production-board is working fine. And I feel outside TI people having production board only. And 16GB eMMC device is a very good size to work with different things. Otherwise we are talking about MMC#2 boot, eMMC boot, 16GB eMMC device in zoom,.. all these information in different page/ link looks very misleading information, if really having such problem. > I the mean time I will check this in Pilot board too and think you checked in pilot board only. > Ref [1] I believe tony has the brand new zoom board - I think your assumption here might be flawed.. -- Regards, Nishanth Menon Ref: [1] http://marc.info/?l=linux-omap&m=126938456103707&w=2 ^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-01 21:59 ` Nishanth Menon @ 2010-04-01 22:58 ` Madhusudhan 2010-04-07 11:49 ` Tony Lindgren 0 siblings, 1 reply; 21+ messages in thread From: Madhusudhan @ 2010-04-01 22:58 UTC (permalink / raw) To: 'Nishanth Menon', 'Ghorai, Sukumar' Cc: tony, linux-omap, linux-mmc > -----Original Message----- > From: Nishanth Menon [mailto:nm@ti.com] > Sent: Thursday, April 01, 2010 4:59 PM > To: Ghorai, Sukumar > Cc: Chikkature Rajashekar, Madhusudhan; tony@atomide.com; linux- > omap@vger.kernel.org; linux-mmc@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > Ghorai, Sukumar had written, on 04/01/2010 01:34 PM, the following: > > >>>> -----Original Message----- > >>>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap- > >>>> owner@vger.kernel.org] On Behalf Of Chikkature Rajashekar, > Madhusudhan > >>>> Sent: 2010-04-01 05:56 > >>>> To: tony@atomide.com > >>>> Cc: linux-omap@vger.kernel.org; linux-mmc@vger.kernel.org > >>>> Subject: [PATCH] Disable the non working eMMC on Zoom2/3 > >>>> > >>>> From: Madhusudhan Chikkature <madhu.cr@ti.com> > >>>> Date: Wed, 31 Mar 2010 12:29:19 -0400 > >>>> Subject: [PATCH] Zoom2/3: Disable MMC > >>>> > >>>> The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the > >>>> writes to fail since the card size is not detected correctly by the > >> MMC > >>>> core. Disable the MMC2 support for Zoom2/3. > >>> > >>> [Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the > >> exact > >>> problem. Because we never face any issue for eMMC in ZOOM3. Because we > >>> have the same eMMC device in 3630-SDP and could have the same problem. > >>> > >> On Zoom3 the EXT_CSD Rev reported by eMMC is zero. See the log > attached. > >> > >> Hence the failures which are reported by people on the list. I had > already > >> bought this problem up on the list previously and was discussed, right? > >> From the log you can also see that a 16GB device is detected as a 1GB. > > > > [Ghorai] I feel it's an issue with eMMC in pilot-board. And production- > board is working fine. And I feel outside TI people having production > board only. And 16GB eMMC device is a very good size to work with > different things. Otherwise we are talking about MMC#2 boot, eMMC boot, > 16GB eMMC device in zoom,.. all these information in different page/ link > looks very misleading information, if really having such problem. > > I the mean time I will check this in Pilot board too and think you > checked in pilot board only. > > > Ref [1] I believe tony has the brand new zoom board - I think your > assumption here might be flawed.. > Wait, I just looked up the serial number on the board. The one I was using is a pilot version where this problem exists. I happen to get an other board which is production unit with ser # 1013089 Rev B. The eMMC on this board has no issue. It reports the EXT_CSD Rev 2 which is correct and works fine. http://omappedia.org/wiki/Zoom_Resources There is a table here which could help. Tony, do you care to just look up the serial number of your board? But again there are several boards out there which could have this non-working eMMC. So what do we do?? It does not make sense to keep something enabled which does not work. Regards, Madhu > -- > Regards, > Nishanth Menon > Ref: > [1] http://marc.info/?l=linux-omap&m=126938456103707&w=2 ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-01 22:58 ` Madhusudhan @ 2010-04-07 11:49 ` Tony Lindgren 2010-04-08 17:11 ` Madhusudhan 0 siblings, 1 reply; 21+ messages in thread From: Tony Lindgren @ 2010-04-07 11:49 UTC (permalink / raw) To: Madhusudhan Cc: 'Nishanth Menon', 'Ghorai, Sukumar', linux-omap, linux-mmc * Madhusudhan <madhu.cr@ti.com> [100401 15:54]: <snip> > > Ref [1] I believe tony has the brand new zoom board - I think your > > assumption here might be flawed.. > > > > Wait, I just looked up the serial number on the board. The one I was using > is a pilot version where this problem exists. > > I happen to get an other board which is production unit with ser # 1013089 > Rev B. The eMMC on this board has no issue. It reports the EXT_CSD Rev 2 > which is correct and works fine. > > http://omappedia.org/wiki/Zoom_Resources > > There is a table here which could help. > > Tony, do you care to just look up the serial number of your board? Sorry for the delay in replying, I've been travelling for a few weeks and been in meetings quite a bit. Anyways, it's a 1013037 REV A board, which seems to be production in the table above. > But again there are several boards out there which could have this > non-working eMMC. So what do we do?? It does not make sense to keep > something enabled which does not work. There's arm kernel parameter for ATAG_REVISION that can be passed from bootloader and then the board-*.c code can initialize things accordingly based on the board revision. Regards, Tony > > [1] http://marc.info/?l=linux-omap&m=126938456103707&w=2 > ^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-07 11:49 ` Tony Lindgren @ 2010-04-08 17:11 ` Madhusudhan 2010-04-27 18:21 ` Tony Lindgren 0 siblings, 1 reply; 21+ messages in thread From: Madhusudhan @ 2010-04-08 17:11 UTC (permalink / raw) To: 'Tony Lindgren' Cc: 'Nishanth Menon', 'Ghorai, Sukumar', linux-omap, linux-mmc > -----Original Message----- > From: Tony Lindgren [mailto:tony@atomide.com] > Sent: Wednesday, April 07, 2010 6:50 AM > To: Madhusudhan > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > linux-mmc@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > * Madhusudhan <madhu.cr@ti.com> [100401 15:54]: > > <snip> > > > > Ref [1] I believe tony has the brand new zoom board - I think your > > > assumption here might be flawed.. > > > > > > > Wait, I just looked up the serial number on the board. The one I was > using > > is a pilot version where this problem exists. > > > > I happen to get an other board which is production unit with ser # > 1013089 > > Rev B. The eMMC on this board has no issue. It reports the EXT_CSD Rev 2 > > which is correct and works fine. > > > > http://omappedia.org/wiki/Zoom_Resources > > > > There is a table here which could help. > > > > Tony, do you care to just look up the serial number of your board? > > Sorry for the delay in replying, I've been travelling for a few weeks > and been in meetings quite a bit. Anyways, it's a 1013037 REV A board, > which seems to be production in the table above. > That means we can not assume all production units have a working eMMC. Would you mind sharing your bootup log? When this device is detected something like below is a clear issue. mmcblk1: mmc1:0001 STM16G 1.00 GiB mmcblk1: p1 p2 Regards, Madhu > > But again there are several boards out there which could have this > > non-working eMMC. So what do we do?? It does not make sense to keep > > something enabled which does not work. > > There's arm kernel parameter for ATAG_REVISION that can be passed from > bootloader and then the board-*.c code can initialize things accordingly > based on the board revision. > > Regards, > > Tony > > > > > [1] http://marc.info/?l=linux-omap&m=126938456103707&w=2 > > ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-08 17:11 ` Madhusudhan @ 2010-04-27 18:21 ` Tony Lindgren 2010-04-28 19:23 ` Tony Lindgren 0 siblings, 1 reply; 21+ messages in thread From: Tony Lindgren @ 2010-04-27 18:21 UTC (permalink / raw) To: Madhusudhan Cc: 'Nishanth Menon', 'Ghorai, Sukumar', linux-omap, linux-mmc * Madhusudhan <madhu.cr@ti.com> [100408 10:07]: > > > > > > Tony, do you care to just look up the serial number of your board? > > > > Sorry for the delay in replying, I've been travelling for a few weeks > > and been in meetings quite a bit. Anyways, it's a 1013037 REV A board, > > which seems to be production in the table above. > > > > That means we can not assume all production units have a working eMMC. > Would you mind sharing your bootup log? When this device is detected > something like below is a clear issue. > > mmcblk1: mmc1:0001 STM16G 1.00 GiB > mmcblk1: p1 p2 Hmm, finally got around looking into this again. Looks like the mmc is now working on my zoom3 with the current Linus' tree at commit 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? This is with the debug_ll patch applied: https://patchwork.kernel.org/patch/87532/ Regards, Tony ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-27 18:21 ` Tony Lindgren @ 2010-04-28 19:23 ` Tony Lindgren 2010-04-28 19:34 ` Madhusudhan 0 siblings, 1 reply; 21+ messages in thread From: Tony Lindgren @ 2010-04-28 19:23 UTC (permalink / raw) To: Madhusudhan Cc: 'Nishanth Menon', 'Ghorai, Sukumar', linux-omap, linux-mmc * Tony Lindgren <tony@atomide.com> [100427 11:16]: > * Madhusudhan <madhu.cr@ti.com> [100408 10:07]: > > > > > > > > Tony, do you care to just look up the serial number of your board? > > > > > > Sorry for the delay in replying, I've been travelling for a few weeks > > > and been in meetings quite a bit. Anyways, it's a 1013037 REV A board, > > > which seems to be production in the table above. > > > > > > > That means we can not assume all production units have a working eMMC. > > Would you mind sharing your bootup log? When this device is detected > > something like below is a clear issue. > > > > mmcblk1: mmc1:0001 STM16G 1.00 GiB > > mmcblk1: p1 p2 For the eMMC I seem to have that: [ 0.978363] mmc1: new high speed MMC card at address 0001 [ 0.984344] mmcblk1: mmc1:0001 STM16G 1.00 GiB [ 0.989105] mmcblk1: unknown partition table ... zoom:~# fdisk -l /dev/mmcblk1 [ 120.306396] mmcblk1: retrying using single block read [ 120.503692] mmcblk1: retrying using single block read [ 120.683593] mmcblk1: error -110 transferring data, sector 2097144, nr 8, card status 0x900 [ 120.691894] end_request: I/O error, dev mmcblk1, sector 2097144 [ 120.872680] mmcblk1: error -110 transferring data, sector 2097145, nr 7, card status 0x900 ... > Hmm, finally got around looking into this again. Looks like the mmc > is now working on my zoom3 with the current Linus' tree at commit > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that > we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? > > This is with the debug_ll patch applied: > > https://patchwork.kernel.org/patch/87532/ For the microSD card, turns out the card I used was flakey. So that should explain some of the problems. I'm almost certain I tried with two different cards earlier though. In any case, let's assume the problem is only the eMMC. Regards, Tony ^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-28 19:23 ` Tony Lindgren @ 2010-04-28 19:34 ` Madhusudhan 2010-04-28 19:45 ` Tony Lindgren 0 siblings, 1 reply; 21+ messages in thread From: Madhusudhan @ 2010-04-28 19:34 UTC (permalink / raw) To: 'Tony Lindgren' Cc: 'Nishanth Menon', 'Ghorai, Sukumar', linux-omap, linux-mmc > -----Original Message----- > From: Tony Lindgren [mailto:tony@atomide.com] > Sent: Wednesday, April 28, 2010 2:23 PM > To: Madhusudhan > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > linux-mmc@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > * Tony Lindgren <tony@atomide.com> [100427 11:16]: > > * Madhusudhan <madhu.cr@ti.com> [100408 10:07]: > > > > > > > > > > Tony, do you care to just look up the serial number of your board? > > > > > > > > Sorry for the delay in replying, I've been travelling for a few > weeks > > > > and been in meetings quite a bit. Anyways, it's a 1013037 REV A > board, > > > > which seems to be production in the table above. > > > > > > > > > > That means we can not assume all production units have a working eMMC. > > > Would you mind sharing your bootup log? When this device is detected > > > something like below is a clear issue. > > > > > > mmcblk1: mmc1:0001 STM16G 1.00 GiB > > > mmcblk1: p1 p2 > > For the eMMC I seem to have that: > > [ 0.978363] mmc1: new high speed MMC card at address 0001 > [ 0.984344] mmcblk1: mmc1:0001 STM16G 1.00 GiB > [ 0.989105] mmcblk1: unknown partition table > ... > > zoom:~# fdisk -l /dev/mmcblk1 > [ 120.306396] mmcblk1: retrying using single block read > [ 120.503692] mmcblk1: retrying using single block read > [ 120.683593] mmcblk1: error -110 transferring data, sector 2097144, nr > 8, card status 0x900 > [ 120.691894] end_request: I/O error, dev mmcblk1, sector 2097144 > [ 120.872680] mmcblk1: error -110 transferring data, sector 2097145, nr > 7, card status 0x900 > ... > > > Hmm, finally got around looking into this again. Looks like the mmc > > is now working on my zoom3 with the current Linus' tree at commit > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that > > we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? > > > > This is with the debug_ll patch applied: > > > > https://patchwork.kernel.org/patch/87532/ > > For the microSD card, turns out the card I used was flakey. So > that should explain some of the problems. I'm almost certain > I tried with two different cards earlier though. In any case, > let's assume the problem is only the eMMC. > Sorry, I did not get a complete picture. Your earlier email said that with Linus tree eMMC on your Zoom3 is working. Is that correct? IMHO, an omap level fix can not solve the problem with eMMC because as I can see from the log you provided above that a 16G device is detected as 1G. This is certainly due to the issue I mentioned earlier. Regards, Madhu > Regards, > > Tony ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-28 19:34 ` Madhusudhan @ 2010-04-28 19:45 ` Tony Lindgren 2010-04-30 16:57 ` Madhusudhan 0 siblings, 1 reply; 21+ messages in thread From: Tony Lindgren @ 2010-04-28 19:45 UTC (permalink / raw) To: Madhusudhan Cc: 'Nishanth Menon', 'Ghorai, Sukumar', linux-omap, linux-mmc * Madhusudhan <madhu.cr@ti.com> [100428 12:30]: > > > > -----Original Message----- > > From: Tony Lindgren [mailto:tony@atomide.com] > > Sent: Wednesday, April 28, 2010 2:23 PM > > To: Madhusudhan > > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > > linux-mmc@vger.kernel.org > > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > > > * Tony Lindgren <tony@atomide.com> [100427 11:16]: > > > * Madhusudhan <madhu.cr@ti.com> [100408 10:07]: > > > > > > > > > > > > Tony, do you care to just look up the serial number of your board? > > > > > > > > > > Sorry for the delay in replying, I've been travelling for a few > > weeks > > > > > and been in meetings quite a bit. Anyways, it's a 1013037 REV A > > board, > > > > > which seems to be production in the table above. > > > > > > > > > > > > > That means we can not assume all production units have a working eMMC. > > > > Would you mind sharing your bootup log? When this device is detected > > > > something like below is a clear issue. > > > > > > > > mmcblk1: mmc1:0001 STM16G 1.00 GiB > > > > mmcblk1: p1 p2 > > > > For the eMMC I seem to have that: > > > > [ 0.978363] mmc1: new high speed MMC card at address 0001 > > [ 0.984344] mmcblk1: mmc1:0001 STM16G 1.00 GiB > > [ 0.989105] mmcblk1: unknown partition table > > ... > > > > zoom:~# fdisk -l /dev/mmcblk1 > > [ 120.306396] mmcblk1: retrying using single block read > > [ 120.503692] mmcblk1: retrying using single block read > > [ 120.683593] mmcblk1: error -110 transferring data, sector 2097144, nr > > 8, card status 0x900 > > [ 120.691894] end_request: I/O error, dev mmcblk1, sector 2097144 > > [ 120.872680] mmcblk1: error -110 transferring data, sector 2097145, nr > > 7, card status 0x900 > > ... > > > > > Hmm, finally got around looking into this again. Looks like the mmc > > > is now working on my zoom3 with the current Linus' tree at commit > > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that > > > we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? > > > > > > This is with the debug_ll patch applied: > > > > > > https://patchwork.kernel.org/patch/87532/ > > > > For the microSD card, turns out the card I used was flakey. So > > that should explain some of the problems. I'm almost certain > > I tried with two different cards earlier though. In any case, > > let's assume the problem is only the eMMC. > > > Sorry, I did not get a complete picture. Your earlier email said that with > Linus tree eMMC on your Zoom3 is working. Is that correct? Nope, now the microSD is working, eMMC is not working. > IMHO, an omap level fix can not solve the problem with eMMC because as I can > see from the log you provided above that a 16G device is detected as 1G. > This is certainly due to the issue I mentioned earlier. OK Tony ^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-28 19:45 ` Tony Lindgren @ 2010-04-30 16:57 ` Madhusudhan 2010-05-05 18:27 ` Tony Lindgren 0 siblings, 1 reply; 21+ messages in thread From: Madhusudhan @ 2010-04-30 16:57 UTC (permalink / raw) To: 'Tony Lindgren' Cc: 'Nishanth Menon', 'Ghorai, Sukumar', linux-omap, linux-mmc <snip> > > > > > > > Hmm, finally got around looking into this again. Looks like the mmc > > > > is now working on my zoom3 with the current Linus' tree at commit > > > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that > > > > we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? > > > > > > > > This is with the debug_ll patch applied: > > > > > > > > https://patchwork.kernel.org/patch/87532/ > > > > > > For the microSD card, turns out the card I used was flakey. So > > > that should explain some of the problems. I'm almost certain > > > I tried with two different cards earlier though. In any case, > > > let's assume the problem is only the eMMC. > > > > > Sorry, I did not get a complete picture. Your earlier email said that > with > > Linus tree eMMC on your Zoom3 is working. Is that correct? > > Nope, now the microSD is working, eMMC is not working. > > > IMHO, an omap level fix can not solve the problem with eMMC because as I > can > > see from the log you provided above that a 16G device is detected as 1G. > > This is certainly due to the issue I mentioned earlier. > > OK This means that some production boards still have this issue with eMMC. So my patch disables the support for MMC2 on zoom boards. Would you consider that? Regards, Madhu > > Tony ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH] Disable the non working eMMC on Zoom2/3 2010-04-30 16:57 ` Madhusudhan @ 2010-05-05 18:27 ` Tony Lindgren 2010-05-06 1:35 ` Madhusudhan 0 siblings, 1 reply; 21+ messages in thread From: Tony Lindgren @ 2010-05-05 18:27 UTC (permalink / raw) To: Madhusudhan Cc: 'Nishanth Menon', 'Ghorai, Sukumar', linux-omap, linux-mmc * Madhusudhan <madhu.cr@ti.com> [100430 09:52]: > <snip> > > > > > > > > > > Hmm, finally got around looking into this again. Looks like the mmc > > > > > is now working on my zoom3 with the current Linus' tree at commit > > > > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that > > > > > we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? > > > > > > > > > > This is with the debug_ll patch applied: > > > > > > > > > > https://patchwork.kernel.org/patch/87532/ > > > > > > > > For the microSD card, turns out the card I used was flakey. So > > > > that should explain some of the problems. I'm almost certain > > > > I tried with two different cards earlier though. In any case, > > > > let's assume the problem is only the eMMC. > > > > > > > Sorry, I did not get a complete picture. Your earlier email said that > > with > > > Linus tree eMMC on your Zoom3 is working. Is that correct? > > > > Nope, now the microSD is working, eMMC is not working. > > > > > IMHO, an omap level fix can not solve the problem with eMMC because as I > > can > > > see from the log you provided above that a 16G device is detected as 1G. > > > This is certainly due to the issue I mentioned earlier. > > > > OK > > This means that some production boards still have this issue with eMMC. So > my patch disables the support for MMC2 on zoom boards. Would you consider > that? But is it also broken on zoom2? And what about this "Simulate multi mmc card as one big" patch? Regards, Tony ^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: [PATCH] Disable the non working eMMC on Zoom2/3 2010-05-05 18:27 ` Tony Lindgren @ 2010-05-06 1:35 ` Madhusudhan 2010-05-06 15:30 ` Tony Lindgren 0 siblings, 1 reply; 21+ messages in thread From: Madhusudhan @ 2010-05-06 1:35 UTC (permalink / raw) To: 'Tony Lindgren' Cc: 'Nishanth Menon', 'Ghorai, Sukumar', linux-omap, linux-mmc > -----Original Message----- > From: Tony Lindgren [mailto:tony@atomide.com] > Sent: Wednesday, May 05, 2010 1:27 PM > To: Madhusudhan > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > linux-mmc@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > * Madhusudhan <madhu.cr@ti.com> [100430 09:52]: > > <snip> > > > > > > > > > > > > > Hmm, finally got around looking into this again. Looks like the > mmc > > > > > > is now working on my zoom3 with the current Linus' tree at > commit > > > > > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something > that > > > > > > we had in omap-fixes fixed this. Or maybe some fix for > drivers/mmc? > > > > > > > > > > > > This is with the debug_ll patch applied: > > > > > > > > > > > > https://patchwork.kernel.org/patch/87532/ > > > > > > > > > > For the microSD card, turns out the card I used was flakey. So > > > > > that should explain some of the problems. I'm almost certain > > > > > I tried with two different cards earlier though. In any case, > > > > > let's assume the problem is only the eMMC. > > > > > > > > > Sorry, I did not get a complete picture. Your earlier email said > that > > > with > > > > Linus tree eMMC on your Zoom3 is working. Is that correct? > > > > > > Nope, now the microSD is working, eMMC is not working. > > > > > > > IMHO, an omap level fix can not solve the problem with eMMC because > as I > > > can > > > > see from the log you provided above that a 16G device is detected as > 1G. > > > > This is certainly due to the issue I mentioned earlier. > > > > > > OK > > > > This means that some production boards still have this issue with eMMC. > So > > my patch disables the support for MMC2 on zoom boards. Would you > consider > > that? > > But is it also broken on zoom2? > Yes. > And what about this "Simulate multi mmc card as one big" patch? > Did not get you, what patch are you referring to? Regards, Madhu > Regards, > > Tony ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH] Disable the non working eMMC on Zoom2/3 2010-05-06 1:35 ` Madhusudhan @ 2010-05-06 15:30 ` Tony Lindgren 2010-05-07 21:25 ` Madhusudhan 0 siblings, 1 reply; 21+ messages in thread From: Tony Lindgren @ 2010-05-06 15:30 UTC (permalink / raw) To: Madhusudhan Cc: 'Nishanth Menon', 'Ghorai, Sukumar', linux-omap, linux-mmc * Madhusudhan <madhu.cr@ti.com> [100505 18:31]: > > > > -----Original Message----- > > From: Tony Lindgren [mailto:tony@atomide.com] > > > And what about this "Simulate multi mmc card as one big" patch? > > > Did not get you, what patch are you referring to? Oops sorry forgot the link: https://patchwork.kernel.org/patch/87944/ Tony ^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: [PATCH] Disable the non working eMMC on Zoom2/3 2010-05-06 15:30 ` Tony Lindgren @ 2010-05-07 21:25 ` Madhusudhan 2010-06-22 11:20 ` zhangfei gao 0 siblings, 1 reply; 21+ messages in thread From: Madhusudhan @ 2010-05-07 21:25 UTC (permalink / raw) To: 'Tony Lindgren' Cc: 'Nishanth Menon', 'Ghorai, Sukumar', linux-omap, linux-mmc > -----Original Message----- > From: Tony Lindgren [mailto:tony@atomide.com] > Sent: Thursday, May 06, 2010 10:31 AM > To: Madhusudhan > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > linux-mmc@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > * Madhusudhan <madhu.cr@ti.com> [100505 18:31]: > > > > > > > -----Original Message----- > > > From: Tony Lindgren [mailto:tony@atomide.com] > > > > > And what about this "Simulate multi mmc card as one big" patch? > > > > > Did not get you, what patch are you referring to? > > Oops sorry forgot the link: > > https://patchwork.kernel.org/patch/87944/ > This will not help. I don't know the history of the patch but what this is intended for is to support multiple MMC cards connected to a single controller. But on the Zoom the eMMC we are talking about is connected to MMC2. Regards, Madhu > Tony ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH] Disable the non working eMMC on Zoom2/3 2010-05-07 21:25 ` Madhusudhan @ 2010-06-22 11:20 ` zhangfei gao 2010-06-22 11:43 ` Ghorai, Sukumar 0 siblings, 1 reply; 21+ messages in thread From: zhangfei gao @ 2010-06-22 11:20 UTC (permalink / raw) To: Madhusudhan Cc: Tony Lindgren, Nishanth Menon, Ghorai, Sukumar, linux-omap, linux-mmc On Sat, May 8, 2010 at 5:25 AM, Madhusudhan <madhu.cr@ti.com> wrote: > > >> -----Original Message----- >> From: Tony Lindgren [mailto:tony@atomide.com] >> Sent: Thursday, May 06, 2010 10:31 AM >> To: Madhusudhan >> Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; >> linux-mmc@vger.kernel.org >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 >> >> * Madhusudhan <madhu.cr@ti.com> [100505 18:31]: >> > >> > >> > > -----Original Message----- >> > > From: Tony Lindgren [mailto:tony@atomide.com] >> > >> > > And what about this "Simulate multi mmc card as one big" patch? >> > > >> > Did not get you, what patch are you referring to? >> >> Oops sorry forgot the link: >> >> https://patchwork.kernel.org/patch/87944/ >> > This will not help. I don't know the history of the patch but what this is > intended for is to support multiple MMC cards connected to a single > controller. But on the Zoom the eMMC we are talking about is connected to > MMC2. > > Regards, > Madhu > >> Tony > > -- > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Hi, Guys Just wander whether 16G Micron eMMC works on your platform. I also have such issue, 16G Micron emmc can not work with read and write, with data timeout. While 8G Micron eMMC workable. Do you have the same issue? Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: [PATCH] Disable the non working eMMC on Zoom2/3 2010-06-22 11:20 ` zhangfei gao @ 2010-06-22 11:43 ` Ghorai, Sukumar 2010-06-24 10:55 ` zhangfei gao 0 siblings, 1 reply; 21+ messages in thread From: Ghorai, Sukumar @ 2010-06-22 11:43 UTC (permalink / raw) To: zhangfei gao, Chikkature Rajashekar, Madhusudhan Cc: Tony Lindgren, Menon, Nishanth, linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org > -----Original Message----- > From: zhangfei gao [mailto:zhangfei.gao@gmail.com] > Sent: Tuesday, June 22, 2010 4:51 PM > To: Chikkature Rajashekar, Madhusudhan > Cc: Tony Lindgren; Menon, Nishanth; Ghorai, Sukumar; linux- > omap@vger.kernel.org; linux-mmc@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > On Sat, May 8, 2010 at 5:25 AM, Madhusudhan <madhu.cr@ti.com> wrote: > > > > > >> -----Original Message----- > >> From: Tony Lindgren [mailto:tony@atomide.com] > >> Sent: Thursday, May 06, 2010 10:31 AM > >> To: Madhusudhan > >> Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > >> linux-mmc@vger.kernel.org > >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > >> > >> * Madhusudhan <madhu.cr@ti.com> [100505 18:31]: > >> > > >> > > >> > > -----Original Message----- > >> > > From: Tony Lindgren [mailto:tony@atomide.com] > >> > > >> > > And what about this "Simulate multi mmc card as one big" patch? > >> > > > >> > Did not get you, what patch are you referring to? > >> > >> Oops sorry forgot the link: > >> > >> https://patchwork.kernel.org/patch/87944/ > >> > > This will not help. I don't know the history of the patch but what this > is > > intended for is to support multiple MMC cards connected to a single > > controller. But on the Zoom the eMMC we are talking about is connected > to > > MMC2. > > > > Regards, > > Madhu > > > >> Tony > > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > Hi, Guys > > Just wander whether 16G Micron eMMC works on your platform. > I also have such issue, 16G Micron emmc can not work with read and > write, with data timeout. > While 8G Micron eMMC workable. > Do you have the same issue? [Ghorai] we have 16G eMMC in ZOOM3 and 3630-SDP and its working fine. Let me know what board you are using. mmc1: new high speed MMC card at address 0001 PM: Adding info for mmc:mmc1:0001 mmcblk0: mmc1:0001 STM16G 14.8 GiB PM: Adding info for No Bus:mmcblk0 mmcblk0: p1 p2 > > Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH] Disable the non working eMMC on Zoom2/3 2010-06-22 11:43 ` Ghorai, Sukumar @ 2010-06-24 10:55 ` zhangfei gao 2010-06-24 12:04 ` Ghorai, Sukumar 0 siblings, 1 reply; 21+ messages in thread From: zhangfei gao @ 2010-06-24 10:55 UTC (permalink / raw) To: Ghorai, Sukumar Cc: Chikkature Rajashekar, Madhusudhan, Tony Lindgren, Menon, Nishanth, linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org On Tue, Jun 22, 2010 at 7:43 PM, Ghorai, Sukumar <s-ghorai@ti.com> wrote: > > >> -----Original Message----- >> From: zhangfei gao [mailto:zhangfei.gao@gmail.com] >> Sent: Tuesday, June 22, 2010 4:51 PM >> To: Chikkature Rajashekar, Madhusudhan >> Cc: Tony Lindgren; Menon, Nishanth; Ghorai, Sukumar; linux- >> omap@vger.kernel.org; linux-mmc@vger.kernel.org >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 >> >> On Sat, May 8, 2010 at 5:25 AM, Madhusudhan <madhu.cr@ti.com> wrote: >> > >> > >> >> -----Original Message----- >> >> From: Tony Lindgren [mailto:tony@atomide.com] >> >> Sent: Thursday, May 06, 2010 10:31 AM >> >> To: Madhusudhan >> >> Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; >> >> linux-mmc@vger.kernel.org >> >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 >> >> >> >> * Madhusudhan <madhu.cr@ti.com> [100505 18:31]: >> >> > >> >> > >> >> > > -----Original Message----- >> >> > > From: Tony Lindgren [mailto:tony@atomide.com] >> >> > >> >> > > And what about this "Simulate multi mmc card as one big" patch? >> >> > > >> >> > Did not get you, what patch are you referring to? >> >> >> >> Oops sorry forgot the link: >> >> >> >> https://patchwork.kernel.org/patch/87944/ >> >> >> > This will not help. I don't know the history of the patch but what this >> is >> > intended for is to support multiple MMC cards connected to a single >> > controller. But on the Zoom the eMMC we are talking about is connected >> to >> > MMC2. >> > >> > Regards, >> > Madhu >> > >> >> Tony >> > >> > -- >> > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in >> > the body of a message to majordomo@vger.kernel.org >> > More majordomo info at http://vger.kernel.org/majordomo-info.html >> > >> >> Hi, Guys >> >> Just wander whether 16G Micron eMMC works on your platform. >> I also have such issue, 16G Micron emmc can not work with read and >> write, with data timeout. >> While 8G Micron eMMC workable. >> Do you have the same issue? > > [Ghorai] we have 16G eMMC in ZOOM3 and 3630-SDP and its working fine. Let me know what board you are using. > mmc1: new high speed MMC card at address 0001 > PM: Adding info for mmc:mmc1:0001 > mmcblk0: mmc1:0001 STM16G 14.8 GiB > PM: Adding info for No Bus:mmcblk0 > mmcblk0: p1 p2 >> >> Thanks > Hi, Ghorai Thanks for your valueable info. We also enabled Micron 16G eMMC, two issues stuck us before. 1. The bus_width should be inited otherwise read ext_csd would be fail. 2. The emmc may stay in boot partition and kernel should switch to user partition, where filesystem is located. Thanks ^ permalink raw reply [flat|nested] 21+ messages in thread
* RE: [PATCH] Disable the non working eMMC on Zoom2/3 2010-06-24 10:55 ` zhangfei gao @ 2010-06-24 12:04 ` Ghorai, Sukumar 0 siblings, 0 replies; 21+ messages in thread From: Ghorai, Sukumar @ 2010-06-24 12:04 UTC (permalink / raw) To: zhangfei gao Cc: Chikkature Rajashekar, Madhusudhan, Tony Lindgren, Menon, Nishanth, linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org > -----Original Message----- > From: zhangfei gao [mailto:zhangfei.gao@gmail.com] > Sent: Thursday, June 24, 2010 4:26 PM > To: Ghorai, Sukumar > Cc: Chikkature Rajashekar, Madhusudhan; Tony Lindgren; Menon, Nishanth; > linux-omap@vger.kernel.org; linux-mmc@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > On Tue, Jun 22, 2010 at 7:43 PM, Ghorai, Sukumar <s-ghorai@ti.com> wrote: > > > > > >> -----Original Message----- > >> From: zhangfei gao [mailto:zhangfei.gao@gmail.com] > >> Sent: Tuesday, June 22, 2010 4:51 PM > >> To: Chikkature Rajashekar, Madhusudhan > >> Cc: Tony Lindgren; Menon, Nishanth; Ghorai, Sukumar; linux- > >> omap@vger.kernel.org; linux-mmc@vger.kernel.org > >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > >> > >> On Sat, May 8, 2010 at 5:25 AM, Madhusudhan <madhu.cr@ti.com> wrote: > >> > > >> > > >> >> -----Original Message----- > >> >> From: Tony Lindgren [mailto:tony@atomide.com] > >> >> Sent: Thursday, May 06, 2010 10:31 AM > >> >> To: Madhusudhan > >> >> Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > >> >> linux-mmc@vger.kernel.org > >> >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > >> >> > >> >> * Madhusudhan <madhu.cr@ti.com> [100505 18:31]: > >> >> > > >> >> > > >> >> > > -----Original Message----- > >> >> > > From: Tony Lindgren [mailto:tony@atomide.com] > >> >> > > >> >> > > And what about this "Simulate multi mmc card as one big" patch? > >> >> > > > >> >> > Did not get you, what patch are you referring to? > >> >> > >> >> Oops sorry forgot the link: > >> >> > >> >> https://patchwork.kernel.org/patch/87944/ > >> >> > >> > This will not help. I don't know the history of the patch but what > this > >> is > >> > intended for is to support multiple MMC cards connected to a single > >> > controller. But on the Zoom the eMMC we are talking about is > connected > >> to > >> > MMC2. > >> > > >> > Regards, > >> > Madhu > >> > > >> >> Tony > >> > > >> > -- > >> > To unsubscribe from this list: send the line "unsubscribe linux-mmc" > in > >> > the body of a message to majordomo@vger.kernel.org > >> > More majordomo info at http://vger.kernel.org/majordomo-info.html > >> > > >> > >> Hi, Guys > >> > >> Just wander whether 16G Micron eMMC works on your platform. > >> I also have such issue, 16G Micron emmc can not work with read and > >> write, with data timeout. > >> While 8G Micron eMMC workable. > >> Do you have the same issue? > > > > [Ghorai] we have 16G eMMC in ZOOM3 and 3630-SDP and its working fine. > Let me know what board you are using. > > mmc1: new high speed MMC card at address 0001 > > PM: Adding info for mmc:mmc1:0001 > > mmcblk0: mmc1:0001 STM16G 14.8 GiB > > PM: Adding info for No Bus:mmcblk0 > > mmcblk0: p1 p2 > >> > >> Thanks > > > > Hi, Ghorai > > Thanks for your valueable info. > We also enabled Micron 16G eMMC, two issues stuck us before. > 1. The bus_width should be inited otherwise read ext_csd would be fail. > 2. The emmc may stay in boot partition and kernel should switch to > user partition, where filesystem is located. [Ghorai] 1. If my understanding is not wrong, then the same problem exists in external MMC card too. 2. So, can you share your eMMC log, just to check if I have any clue! Or let me know how I can reproduce the issue. > > Thanks ^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2010-06-24 12:04 UTC | newest] Thread overview: 21+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2010-04-01 0:25 [PATCH] Disable the non working eMMC on Zoom2/3 Madhusudhan Chikkature 2010-04-01 4:03 ` Ghorai, Sukumar 2010-04-01 17:04 ` Madhusudhan 2010-04-01 18:34 ` Ghorai, Sukumar 2010-04-01 21:59 ` Nishanth Menon 2010-04-01 22:58 ` Madhusudhan 2010-04-07 11:49 ` Tony Lindgren 2010-04-08 17:11 ` Madhusudhan 2010-04-27 18:21 ` Tony Lindgren 2010-04-28 19:23 ` Tony Lindgren 2010-04-28 19:34 ` Madhusudhan 2010-04-28 19:45 ` Tony Lindgren 2010-04-30 16:57 ` Madhusudhan 2010-05-05 18:27 ` Tony Lindgren 2010-05-06 1:35 ` Madhusudhan 2010-05-06 15:30 ` Tony Lindgren 2010-05-07 21:25 ` Madhusudhan 2010-06-22 11:20 ` zhangfei gao 2010-06-22 11:43 ` Ghorai, Sukumar 2010-06-24 10:55 ` zhangfei gao 2010-06-24 12:04 ` Ghorai, Sukumar
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).