[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[joancarles]

Hi

We're trying to get our ADC working (actually generic 4-way touchscreen 
support via ADC) on a custom PCB using the i.MX25 infrastructure. It 
seems that there are not a lot of people out there, who have tried the 
Freescale implementation (based on their latest kernel drop: 2.6.31) of 
the ADC driver for touchscreen support. Freescale's support with regard 
to kernel development for out-of-tree implementation, somewhat 
understandably, has so far been close to non-existent.

Here is our crash dump:

[    1.636986] i.MX ADC input touchscreen: trying to load.
[    1.642470] i.MX ADC input touchscreen: ADC ready.
[    1.647530] i.MX ADC input touchscreen: input device allocated.
[    1.653583] usb 2-1: not running at top speed; connect to a high 
speed hub
[    1.661499] input: imx_adc_ts as /devices/virtual/input/input0
[    1.667570] usb 2-1: New USB device found, idVendor=0424, 
idProduct=2513
[    1.674309] usb 2-1: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[    1.685746] i.MX ADC input touchscreen: input device registered.
[    1.692270] i.MX ADC input touchscreen loaded.
[    1.696881] imxdi_rtc imxdi_rtc.0: setting system clock to 
1970-01-01 00:00:00 UTC (0)
[    1.705016] i.MX ADC: imx_adc_read_ts start reading
[    1.711638] i.MX ADC: imx_adc_interrupt handler called
[    1.716805] i.MX ADC: imx_adc_interrupt waking up tsq
[    1.722717] hub 2-1:1.0: USB hub found
[    1.727755] hub 2-1:1.0: 3 ports detected
[    1.731882] i.MX ADC: imx_adc_read_ts before event interruptible
[    1.738197] i.MX ADC: imx_adc_read_ts after event interruptible
[    1.744289] i.MX ADC: imx_adc_read_ts finished reading
[    1.849692] i.MX ADC: imx_adc_read_ts filling samples
[    1.867547] i.MX ADC: imx_adc_read_ts before mutex
[    1.872378] i.MX ADC: imx_adc_read_ts after mutex
[    1.877165] Unable to handle kernel NULL pointer dereference at 
virtual address 00000024
[    1.885280] pgd = c0004000
[    1.887998] [00000024] *pgd=00000000
[    1.891602] Internal error: Oops: 5 [#1] PREEMPT
[    1.896232] last sysfs file:
[    1.899213] Modules linked in:
[    1.902298] CPU: 0    Not tainted  (2.6.39.3-sid1-2.1.8-rc+ #44)
[    1.908357] PC is at input_handle_event+0x244/0x4d0
[    1.913265] LR is at input_event+0x7c/0xac
[    1.917386] pc : [<c02a7934>]    lr : [<c02a7ce8>]    psr: 20000093
[    1.917403] sp : c397ff58  ip : 00000000  fp : 00000000
[    1.928905] r10: 00000000  r9 : 00000000  r8 : 00000013
[    1.934150] r7 : 00000000  r6 : 00000001  r5 : c3965400  r4 : 
00000003
[    1.940699] r3 : 00000018  r2 : 00000018  r1 : 00000003  r0 : 
00000000
[    1.947252] Flags: nzCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  
Segment kernel
[    1.954673] Control: 0005317f  Table: 80004000  DAC: 00000017
[    1.960440] Process imx_adc_ts (pid: 37, stack limit = 0xc397e270)
[    1.966642] Stack: (0xc397ff58 to 0xc3980000)
[    1.971022] ff40:                                                    
   00000003 c397e000
[    1.979240] ff60: c3965400 00000001 00000013 c02a7ce8 c060d620 
00000000 00000000 c060d620
[    1.987458] ff80: c060d620 00000000 00000000 c02aa124 00000000 
000004c8 0000049b 00000593
[    1.995675] ffa0: 00000000 00000840 000008dc 00000870 00000001 
00000001 00000013 c381df78
[    2.003892] ffc0: 00000000 c02aa0b0 00000013 c0056928 00000000 
00000000 00000000 00000001
[    2.012113] ffe0: c397ffe0 c397ffe0 c381df78 c005689c c002a890 
c002a890 fbecc297 f3ffe7e7
[    2.020361] [<c02a7934>] (input_handle_event+0x244/0x4d0) from 
[<c02a7ce8>] (input_event+0x7c/0xac)
[    2.029466] [<c02a7ce8>] (input_event+0x7c/0xac) from [<c02aa124>] 
(ts_thread+0x74/0xd0)
[    2.037629] [<c02aa124>] (ts_thread+0x74/0xd0) from [<c0056928>] 
(kthread+0x8c/0x94)
[    2.045442] [<c0056928>] (kthread+0x8c/0x94) from [<c002a890>] 
(kernel_thread_exit+0x0/0x8)
[    2.053840] Code: 0a00001f e59530fc e0861086 e0833181 (e593300c)
[    2.060090] ---[ end trace 24451e1ee97aa5a2 ]---
[    2.064748] note: imx_adc_ts[37] exited with preempt_count 1

I have attached the modified (adapted due to various kernel changes 
between 2.6.31 and 2.6.39.3 and sprinkled some printk's for better 
understanding in initial forward-port) imx_adc_ts and imx_adc drivers 
for viewing pleasure.

When enabling mutex and spinlock debugging, the machine oopses and 
hangs forever, leaving us with following dump:

[    1.418168] INFO: trying to register non-static key.
[    1.423176] the code is fine but needs lockdep annotation.
[    1.428683] turning off the locking correctness validator.
[    1.434264] [<c002e6a8>] (unwind_backtrace+0x0/0x130) from 
[<c0065ae4>] (__lock_acquire.clone.16+0x5d0/0xc90)
[    1.444255] [<c0065ae4>] (__lock_acquire.clone.16+0x5d0/0xc90) from 
[<c00666d4>] (lock_acquire+0x5c/0x70)
[    1.453896] [<c00666d4>] (lock_acquire+0x5c/0x70) from [<c03f1af0>] 
(_raw_spin_lock_irqsave+0x4c/0x60)
[    1.463269] [<c03f1af0>] (_raw_spin_lock_irqsave+0x4c/0x60) from 
[<c02a4944>] (di_int_enable+0x18/0x38)
[    1.472718] [<c02a4944>] (di_int_enable+0x18/0x38) from [<c02a4a94>] 
(di_write_wait+0x30/0x1b8)
[    1.481472] [<c02a4a94>] (di_write_wait+0x30/0x1b8) from 
[<c02a4e58>] (dryice_rtc_probe+0x17c/0x2b4)
[    1.490663] [<c02a4e58>] (dryice_rtc_probe+0x17c/0x2b4) from 
[<c0209a78>] (platform_drv_probe+0x14/0x18)
[    1.500202] [<c0209a78>] (platform_drv_probe+0x14/0x18) from 
[<c02089f0>] (driver_probe_device+0xd8/0x214)
[    1.509909] [<c02089f0>] (driver_probe_device+0xd8/0x214) from 
[<c0208bc0>] (__driver_attach+0x94/0x98)
[    1.519371] [<c0208bc0>] (__driver_attach+0x94/0x98) from 
[<c0207b30>] (bus_for_each_dev+0x54/0x7c)
[    1.528487] [<c0207b30>] (bus_for_each_dev+0x54/0x7c) from 
[<c020827c>] (bus_add_driver+0xb8/0x25c)
[    1.537592] [<c020827c>] (bus_add_driver+0xb8/0x25c) from 
[<c0208ee0>] (driver_register+0x78/0x13c)
[    1.546692] [<c0208ee0>] (driver_register+0x78/0x13c) from 
[<c0209cf8>] (platform_driver_probe+0x18/0x9c)
[    1.556328] [<c0209cf8>] (platform_driver_probe+0x18/0x9c) from 
[<c00294c4>] (do_one_initcall+0x30/0x16c)
[    1.565962] [<c00294c4>] (do_one_initcall+0x30/0x16c) from 
[<c000891c>] (kernel_init+0x94/0x140)
[    1.574810] [<c000891c>] (kernel_init+0x94/0x140) from [<c002a870>] 
(kernel_thread_exit+0x0/0x8)
[    7.321116] BUG: spinlock lockup on CPU#0, swapper/1, c3862490
[    7.327010] [<c002e6a8>] (unwind_backtrace+0x0/0x130) from 
[<c01d4a04>] (do_raw_spin_lock+0x124/0x140)
[    7.336387] [<c01d4a04>] (do_raw_spin_lock+0x124/0x140) from 
[<c03f1af8>] (_raw_spin_lock_irqsave+0x54/0x60)
[    7.346280] [<c03f1af8>] (_raw_spin_lock_irqsave+0x54/0x60) from 
[<c02a4944>] (di_int_enable+0x18/0x38)
[    7.355728] [<c02a4944>] (di_int_enable+0x18/0x38) from [<c02a4a94>] 
(di_write_wait+0x30/0x1b8)
[    7.364480] [<c02a4a94>] (di_write_wait+0x30/0x1b8) from 
[<c02a4e58>] (dryice_rtc_probe+0x17c/0x2b4)
[    7.373670] [<c02a4e58>] (dryice_rtc_probe+0x17c/0x2b4) from 
[<c0209a78>] (platform_drv_probe+0x14/0x18)
[    7.383207] [<c0209a78>] (platform_drv_probe+0x14/0x18) from 
[<c02089f0>] (driver_probe_device+0xd8/0x214)
[    7.392913] [<c02089f0>] (driver_probe_device+0xd8/0x214) from 
[<c0208bc0>] (__driver_attach+0x94/0x98)
[    7.402371] [<c0208bc0>] (__driver_attach+0x94/0x98) from 
[<c0207b30>] (bus_for_each_dev+0x54/0x7c)
[    7.411480] [<c0207b30>] (bus_for_each_dev+0x54/0x7c) from 
[<c020827c>] (bus_add_driver+0xb8/0x25c)
[    7.420583] [<c020827c>] (bus_add_driver+0xb8/0x25c) from 
[<c0208ee0>] (driver_register+0x78/0x13c)
[    7.429684] [<c0208ee0>] (driver_register+0x78/0x13c) from 
[<c0209cf8>] (platform_driver_probe+0x18/0x9c)
[    7.439317] [<c0209cf8>] (platform_driver_probe+0x18/0x9c) from 
[<c00294c4>] (do_one_initcall+0x30/0x16c)
[    7.448948] [<c00294c4>] (do_one_initcall+0x30/0x16c) from 
[<c000891c>] (kernel_init+0x94/0x140)
[    7.457794] [<c000891c>] (kernel_init+0x94/0x140) from [<c002a870>] 
(kernel_thread_exit+0x0/0x8)

Could someone please help us with the debugging? We're kind of stuck 
right now. It's interesting that we see two interrupts registered to IRQ 
46 in /proc/interrupts after boot and oops.

Best regards
-- 
Joan C. Abelaira
  FQ Ingenier?a Electr?nica, S.A.
Pol?gon Industrial Vilanoveta
Av. de les Roquetes, 9
E-08812 Sant Pere de Ribes (Barcelona)
SPAIN
Telf: +34 932 080 258
Fax: +34 934 592 893
M?vil: +34 638 331 745

http://www.fqingenieria.es/
email: joancarles at fqingenieria.es
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imx_adc_ts.c
Type: text/x-c
Size: 3459 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120220/a09c3ff0/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imx_adc.c
Type: text/x-c
Size: 31383 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120220/a09c3ff0/attachment-0003.bin>

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[Baruch Siach]

Hi joancarles,

On Mon, Feb 20, 2012 at 10:15:42AM +0100, joancarles wrote:
> We're trying to get our ADC working (actually generic 4-way
> touchscreen support via ADC) on a custom PCB using the i.MX25
> infrastructure. It seems that there are not a lot of people out
> there, who have tried the Freescale implementation (based on their
> latest kernel drop: 2.6.31) of the ADC driver for touchscreen
> support. Freescale's support with regard to kernel development for
> out-of-tree implementation, somewhat understandably, has so far been
> close to non-existent.

This list is for mainline kernel only. You should contact Freescale for 
support for out of tree drivers in their kernel code. Unfortunately, it seems 
that Freescale has no interest in mainline kernel support for i.MX25.

You may try a newer kernel drop from Freescale, based on 2.6.38 (tagged 
rel_imx_2.6.38_11.11.01). Get it from 
http://opensource.freescale.com/git?p=imx/linux-2.6-imx.git;a=summary.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[joancarles]

Hi Baruch

Thanks for your reply.

>> We're trying to get our ADC working (actually generic 4-way
>> touchscreen support via ADC) on a custom PCB using the i.MX25
>> infrastructure. It seems that there are not a lot of people out
>> there, who have tried the Freescale implementation (based on their
>> latest kernel drop: 2.6.31) of the ADC driver for touchscreen
>> support. Freescale's support with regard to kernel development for
>> out-of-tree implementation, somewhat understandably, has so far been
>> close to non-existent.
>
> This list is for mainline kernel only. You should contact Freescale 
> for
> support for out of tree drivers in their kernel code. Unfortunately,
> it seems that Freescale has no interest in mainline kernel support 
> for i.MX25.

We have contacted them and all they support is their L2.6.13 freeze 
release for the i.MX25. It's actually even difficult to try to get in 
contact with anyone from their kernel development team. We anticipated 
that using our customized design based on an i.MX25, we'd run into these 
kind of issues.

> You may try a newer kernel drop from Freescale, based on 2.6.38 
> (tagged
> rel_imx_2.6.38_11.11.01). Get it from
> 
> http://opensource.freescale.com/git?p=imx/linux-2.6-imx.git;a=summary.

We have tried all "*rel*" tagged kernel of their repository, but they 
simply (especially touchscreen support) do not work. I wonder if anyone 
ever got the ADC touch screen support working at all with the i.MX25. We 
are also trying a stock 3.3-rc kernel and can't get our i.MX25 to boot 
... yet.

Best regards
-- 
Joan C. Abelaira
  FQ Ingenier?a Electr?nica, S.A.
Pol?gon Industrial Vilanoveta
Av. de les Roquetes, 9
E-08812 Sant Pere de Ribes (Barcelona)
SPAIN
Telf: +34 932 080 258
Fax: +34 934 592 893
M?vil: +34 638 331 745

http://www.fqingenieria.es/
email: joancarles at fqingenieria.es

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[Baruch Siach]

Hi joancarles,

On Mon, Feb 20, 2012 at 11:07:56AM +0100, joancarles wrote:

[snip]

> We are also trying a stock 3.3-rc kernel and can't get
> our i.MX25 to boot ... yet.

This is on-topic here. Can you share more details?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[Eric Bénard]

Hi Joan,

Le Mon, 20 Feb 2012 12:11:58 +0200,
Baruch Siach <baruch@tkos.co.il> a ?crit :
> On Mon, Feb 20, 2012 at 11:07:56AM +0100, joancarles wrote:
> 
> [snip]
> 
> > We are also trying a stock 3.3-rc kernel and can't get
> > our i.MX25 to boot ... yet.
> 
3.3-rc works fine here (at least it was until 2 weeks ago).

I'll send you a dirty patch which works on 3.1 & 3.2 for the ADC.

Eric
-- 
http://eukrea.com/en/news/104-2012

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[Juergen Beisert]

Hi Eric,

Eric B?nard wrote:
> Le Mon, 20 Feb 2012 12:11:58 +0200,
>
> Baruch Siach <baruch@tkos.co.il> a ?crit :
> > On Mon, Feb 20, 2012 at 11:07:56AM +0100, joancarles wrote:
> >
> > [snip]
> >
> > > We are also trying a stock 3.3-rc kernel and can't get
> > > our i.MX25 to boot ... yet.
>
> 3.3-rc works fine here (at least it was until 2 weeks ago).
>
> I'll send you a dirty patch which works on 3.1 & 3.2 for the ADC.

Then we should share it, as I'm also working in the ADC/touchscreen/hwmon 
driver for i.MX25.

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[Eric Bénard]

Hi Juergen,

Le Mon, 20 Feb 2012 12:07:55 +0100,
Juergen Beisert <jbe@pengutronix.de> a ?crit :
> Then we should share it, as I'm also working in the ADC/touchscreen/hwmon 
> driver for i.MX25.
> 
the dirty patch I talk about is only a quick port of the Freescale
driver. I also started to write a new driver for the ADC a few months
ago but didn't progress on that because of lack of time until now.
If you have some code to test I can help when I find some free time.

Eric
-- 
http://eukrea.com/en/news/104-2012

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[joancarles]

>> We are also trying a stock 3.3-rc kernel and can't get
>> our i.MX25 to boot ... yet.
>
> This is on-topic here. Can you share more details?

Right now, the only tree we have to test here is a 3.2.0-rc2, but I 
will try a 3.3-rc kernel soon (slow Internet connection and an even 
slower computer to cross-compile kernels inhibits us perform work 
quicker). In case there is interest, this is the output of where it 
hangs.

I believe it might have something to do with the way of how MTD works, 
or doesn't in our case, with regard to 2.6.x kernels. It can't find a 
list of partitions.

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.0-rc2-ga9098b3 (develop at pc-develop) (gcc version 
4.5.2 20101105 (prerelease) (GCC) ) #2 PREEMPT Mon Feb 20 14:24:16 CET 
2012
CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Freescale MX25PDK (3DS)
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 
16256
Kernel command line: console=ttymxc0,115200 root=/dev/mtdblock2 
rootfstype=jffs2 
mtdparts=physmap-flash.0:0x100000(u-boot),0x300000(kernel),0x3C00000(jffs2) 
bootcmd=tftpboot 0x81000000 /v2.1.8-rc/uImage
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 60380k/60380k available, 5156k reserved, 0K highmem
Virtual kernel memory layout:
     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
     vmalloc : 0xc4800000 - 0xf4000000   ( 760 MB)
     lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)
     modules : 0xbf000000 - 0xc0000000   (  16 MB)
       .text : 0xc0008000 - 0xc041c3c0   (4177 kB)
       .init : 0xc041d000 - 0xc043c000   ( 124 kB)
       .data : 0xc043c000 - 0xc045fd80   ( 144 kB)
        .bss : 0xc045fda4 - 0xc0472e84   (  77 kB)
NR_IRQS:336
MXC IRQ initialized
CPU identified as i.MX25, unknown revision
sched_clock: 32 bits at 66MHz, resolution 15ns, wraps every 64585ms
Console: colour dummy device 80x30
Calibrating delay loop... 199.06 BogoMIPS (lpj=995328)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
print_constraints: dummy:
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
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 named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (extended precision)
NTFS driver 2.1.30 [Flags: R/W].
JFFS2 version 2.2. (NAND) ? 2001-2006 Red Hat, Inc.
fuse init (API version 7.17)
msgmni has been set to 117
io scheduler noop registered (default)
imx-fb imx-fb.0: i.MX Framebuffer driver
Console: switching to colour frame buffer device 80x60
imx-sdma imx35-sdma: initialized
Serial: IMX driver
imx21-uart.0: ttymxc0 at MMIO 0x43f90000 (irq = 45) is a IMX
console [ttymxc0] enabled
loop: module loaded
FEC Ethernet Driver
fec_enet_mii_bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
mxc-ehci mxc-ehci.1: initializing i.MX USB Controller
mxc-ehci mxc-ehci.1: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.1: new USB bus registered, assigned bus number 1
mxc-ehci mxc-ehci.1: irq 35, io mem 0x53ff4400
mxc-ehci mxc-ehci.1: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
imxdi_rtc imxdi_rtc.0: rtc core: registered imxdi_rtc as rtc0
i2c /dev entries driver
Driver for 1-wire Dallas network protocol.
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s 
(nowayout=0)
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
   No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
imxdi_rtc imxdi_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC 
(0)
List of all partitions:
No filesystem could mount root, tried:  jffs2
Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
[<c00181d0>] (unwind_backtrace+0x0/0xf0) from [<c0325f58>] 
(panic+0x60/0x198)
[<c0325f58>] (panic+0x60/0x198) from [<c041db7c>] 
(mount_block_root+0x244/0x294)
[<c041db7c>] (mount_block_root+0x244/0x294) from [<c041dd4c>] 
(prepare_namespace+0x11c/0x180)
[<c041dd4c>] (prepare_namespace+0x11c/0x180) from [<c041d800>] 
(kernel_init+0xe8/0x11c)
[<c041d800>] (kernel_init+0xe8/0x11c) from [<c0013cf4>] 
(kernel_thread_exit+0x0/0x8)

Cheers
-- 
Joan C. Abelaira
  FQ Ingenier?a Electr?nica, S.A.
Pol?gon Industrial Vilanoveta
Av. de les Roquetes, 9
E-08812 Sant Pere de Ribes (Barcelona)
SPAIN
Telf: +34 932 080 258
Fax: +34 934 592 893
M?vil: +34 638 331 745

http://www.fqingenieria.es/
email: joancarles at fqingenieria.es

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[Baruch Siach]

Hi joancarles,

On Mon, Feb 20, 2012 at 02:42:14PM +0100, joancarles wrote:
> >>We are also trying a stock 3.3-rc kernel and can't get
> >>our i.MX25 to boot ... yet.
> >
> >This is on-topic here. Can you share more details?
> 
> Right now, the only tree we have to test here is a 3.2.0-rc2, but I
> will try a 3.3-rc kernel soon (slow Internet connection and an even
> slower computer to cross-compile kernels inhibits us perform work
> quicker). In case there is interest, this is the output of where it
> hangs.
> 
> I believe it might have something to do with the way of how MTD
> works, or doesn't in our case, with regard to 2.6.x kernels. It
> can't find a list of partitions.

[snip]

> Kernel command line: console=ttymxc0,115200 root=/dev/mtdblock2
> rootfstype=jffs2 mtdparts=physmap-flash.0:0x100000(u-boot),0x300000(kernel),0x3C00000(jffs2)
> bootcmd=tftpboot 0x81000000 /v2.1.8-rc/uImage

[snip]

> List of all partitions:
> No filesystem could mount root, tried:  jffs2
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> [<c00181d0>] (unwind_backtrace+0x0/0xf0) from [<c0325f58>]
> (panic+0x60/0x198)
> [<c0325f58>] (panic+0x60/0x198) from [<c041db7c>]
> (mount_block_root+0x244/0x294)
> [<c041db7c>] (mount_block_root+0x244/0x294) from [<c041dd4c>]
> (prepare_namespace+0x11c/0x180)
> [<c041dd4c>] (prepare_namespace+0x11c/0x180) from [<c041d800>]
> (kernel_init+0xe8/0x11c)
> [<c041d800>] (kernel_init+0xe8/0x11c) from [<c0013cf4>]
> (kernel_thread_exit+0x0/0x8)

MTD support in your kernel seems to be missing.

What kind of flash do you have on your board? NOR? NAND?

Please post your kernel .config file.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[joancarles]

Hi Baruch

>> Kernel command line: console=ttymxc0,115200 root=/dev/mtdblock2
>> rootfstype=jffs2 
>> mtdparts=physmap-flash.0:0x100000(u-boot),0x300000(kernel),0x3C00000(jffs2)
>> bootcmd=tftpboot 0x81000000 /v2.1.8-rc/uImage
>
> [snip]
>
>> List of all partitions:
>> No filesystem could mount root, tried:  jffs2
>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(0,0)
>> [<c00181d0>] (unwind_backtrace+0x0/0xf0) from [<c0325f58>]
>> (panic+0x60/0x198)
>> [<c0325f58>] (panic+0x60/0x198) from [<c041db7c>]
>> (mount_block_root+0x244/0x294)
>> [<c041db7c>] (mount_block_root+0x244/0x294) from [<c041dd4c>]
>> (prepare_namespace+0x11c/0x180)
>> [<c041dd4c>] (prepare_namespace+0x11c/0x180) from [<c041d800>]
>> (kernel_init+0xe8/0x11c)
>> [<c041d800>] (kernel_init+0xe8/0x11c) from [<c0013cf4>]
>> (kernel_thread_exit+0x0/0x8)
>
> MTD support in your kernel seems to be missing.

Yep, kind of, even tough:

$> grep "^CONFIG.MTD" .config
CONFIG_MTD=y
CONFIG_MTD_CMDLINE_PARTS=y
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_CFI=y
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_CFI_ADV_OPTIONS=y
CONFIG_MTD_CFI_NOSWAP=y
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_CFI_UTIL=y
CONFIG_MTD_PHYSMAP=y

> What kind of flash do you have on your board? NOR? NAND?

That's most probably the culprit, thanks. We have a NOR flash, so I 
need to find a way to enable it. Funny enough, our working 2.6.39.3 
.config has the same settings for MTD:

linux-2.6.39.3$> grep "^CONFIG.MTD" .config
CONFIG_MTD=y
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_CMDLINE_PARTS=y
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_CFI=y
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_CFI_ADV_OPTIONS=y
CONFIG_MTD_CFI_NOSWAP=y
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_CFI_UTIL=y
CONFIG_MTD_PHYSMAP=y

> Please post your kernel .config file.

Attached is the .config file for the non-working kernel.

Cheers
-- 
Joan C. Abelaira
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: .config
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120220/41b2c97b/attachment-0001.ksh>

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[Baruch Siach]

Hi joancarles,

On Mon, Feb 20, 2012 at 03:40:35PM +0100, joancarles wrote:
> Hi Baruch
> >MTD support in your kernel seems to be missing.
> 
> Yep, kind of, even tough:
> 
> $> grep "^CONFIG.MTD" .config
> CONFIG_MTD=y
> CONFIG_MTD_CMDLINE_PARTS=y
> CONFIG_MTD_CHAR=y
> CONFIG_MTD_BLKDEVS=y
> CONFIG_MTD_BLOCK=y
> CONFIG_MTD_CFI=y
> CONFIG_MTD_GEN_PROBE=y
> CONFIG_MTD_CFI_ADV_OPTIONS=y
> CONFIG_MTD_CFI_NOSWAP=y
> CONFIG_MTD_MAP_BANK_WIDTH_1=y
> CONFIG_MTD_MAP_BANK_WIDTH_2=y
> CONFIG_MTD_MAP_BANK_WIDTH_4=y
> CONFIG_MTD_CFI_I1=y
> CONFIG_MTD_CFI_I2=y
> CONFIG_MTD_CFI_AMDSTD=y
> CONFIG_MTD_CFI_UTIL=y
> CONFIG_MTD_PHYSMAP=y
> 
> >What kind of flash do you have on your board? NOR? NAND?
> 
> That's most probably the culprit, thanks. We have a NOR flash, so I
> need to find a way to enable it. Funny enough, our working 2.6.39.3

Please send the console output of the working kernel.

Just a shot in the dark: have you looked into pin muxing?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

[2.6.39.3] [MX25] oops in driver_register for ADC touchscreen support (imx_adc_ts)

[joancarles]

Hi

>> >What kind of flash do you have on your board? NOR? NAND?
>>
>> That's most probably the culprit, thanks. We have a NOR flash, so I
>> need to find a way to enable it. Funny enough, our working 2.6.39.3
>
> Please send the console output of the working kernel.
>
> Just a shot in the dark: have you looked into pin muxing?

That was it I reckon, plus a few changes on how to initialize the mx25 
in the new kernel. Also, a hint with regard to setting the MACH-ID for 
our device helped with the first working boot of the newest kernel drop:

Booting Linux on physical CPU 0
Linux version 3.3.0-rc4-00000-rc4-dirty (develop at pc-develop) (gcc 
version 4.5.2 20101105 (prerelease) (GCC) ) #8 PREEMPT Tue Feb 21 
09:26:52 CET 2012
CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: FQ Ingenieria SID1 (NOAH)
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 16384
free_area_init_node: node 0, pgdat c046fadc, node_mem_map c0485000
   Normal zone: 128 pages used for memmap
   Normal zone: 0 pages reserved
   Normal zone: 16256 pages, LIFO batch:3
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 
16256
Kernel command line: console=ttymxc0,115200 root=/dev/mtdblock2 
rootfstype=jffs2 
mtdparts=physmap-flash.0:0x100000(u-boot),0x300000(kernel),0x3C00000(jffs2) 
imxfb.enabled=1
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 60304k/60304k available, 5232k reserved, 0K highmem
Virtual kernel memory layout:
     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
     vmalloc : 0xc4800000 - 0xff000000   ( 936 MB)
     lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)
     modules : 0xbf000000 - 0xc0000000   (  16 MB)
       .text : 0xc0008000 - 0xc042c708   (4242 kB)
       .init : 0xc042d000 - 0xc044c000   ( 124 kB)
       .data : 0xc044c000 - 0xc0470160   ( 145 kB)
        .bss : 0xc0470184 - 0xc048481c   (  82 kB)
NR_IRQS:340
MXC IRQ initialized
CPU identified as i.MX25, unknown revision
sched_clock: 32 bits at 66MHz, resolution 15ns, wraps every 64585ms
Console: colour dummy device 80x30
Calibrating delay loop... 199.06 BogoMIPS (lpj=995328)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0x80335340 - 0x80335398
devtmpfs: initialized
print_constraints: dummy:
NET: Registered protocol family 16
gpiochip_add: registered GPIOs 0 to 31 on device: imx31-gpio.0
gpiochip_add: registered GPIOs 32 to 63 on device: imx31-gpio.1
gpiochip_add: registered GPIOs 64 to 95 on device: imx31-gpio.2
gpiochip_add: registered GPIOs 96 to 127 on device: imx31-gpio.3
bio: create slab <bio-0> at 0
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
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 named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (extended precision)
NTFS driver 2.1.30 [Flags: R/W].
JFFS2 version 2.2. (NAND) ? 2001-2006 Red Hat, Inc.
fuse init (API version 7.18)
msgmni has been set to 117
io scheduler noop registered (default)
imx-fb imx-fb.0: i.MX Framebuffer driver
Console: switching to colour frame buffer device 80x60
imx-sdma imx35-sdma: initialized
Serial: IMX driver
imx21-uart.0: ttymxc0 at MMIO 0x43f90000 (irq = 45) is a IMX
console [ttymxc0] enabled
loop: module loaded
at24 0-0050: 65024 byte at24 EEPROM, writable, 128 bytes/write
physmap platform flash device: 04000000 at a0000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank. 
Manufacturer ID 0x000001 Chip ID 0x002301
Amd/Fujitsu Extended Query Table at 0x0040
   Amd/Fujitsu Extended Query version 1.3.
number of CFI chips: 1
3 cmdlinepart partitions found on MTD device physmap-flash.0
Creating 3 MTD partitions on "physmap-flash.0":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000400000 : "kernel"
0x000000400000-0x000004000000 : "jffs2"
FEC Ethernet Driver
fec_enet_mii_bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
usbcore: registered new interface driver fq_cpr40
FQ cpr40 driver: driver started: v1.0.6 (2010/10/15)
imxdi_rtc imxdi_rtc.0: rtc core: registered imxdi_rtc as rtc0
i2c /dev entries driver
Driver for 1-wire Dallas network protocol.
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s 
(nowayout=0)
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
   No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
imxdi_rtc imxdi_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC 
(0)
VFS: Mounted root (jffs2 filesystem) on device 31:2.
devtmpfs: mounted
Freeing init memory: 124K
eth0: Freescale FEC PHY driver [Generic PHY] 
(mii_bus:phy_addr=imx25-fec-1:00, irq=-1)
PHY: imx25-fec-1:00 - Link is Up - 100/Full
imx-sdma imx35-sdma: firmware not found

A long way to go still, but it's a start ...

I'll now try to get the touchscreen and the remaining interfaces (i2c, 
uarts, sdma, others) to work.

Thanks for the pointers and cheers
-- 
Joan C. Abelaira