From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Valentin Longchamp <valentin.longchamp@epfl.ch>
Cc: "linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>,
Sascha Hauer <s.hauer@pengutronix.de>,
Dan Williams <dan.j.williams@intel.com>,
"linux-fbdev-devel@lists.sourceforge.net"
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH 2/4 v8] i.MX31: Image Processing Unit DMA and IRQ drivers
Date: Fri, 23 Jan 2009 13:13:26 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0901231308040.4463@axis700.grange> (raw)
In-Reply-To: <4979A88A.5010102@epfl.ch>
On Fri, 23 Jan 2009, Valentin Longchamp wrote:
> Guennadi Liakhovetski wrote:
> > On Fri, 23 Jan 2009, Valentin Longchamp wrote:
> >> So the devices are registered fine. My problem is that the driver is not
> >> registered for me: This should be done by the subsys_initcall but
> >> ipu_init is never called.
> >
> > Are you sure you have CONFIG_MX3_IPU=y?... sorry, I don't see any other
> > possibility why a subsys_initcall() would not be called. You can also
> > check if it's being compiled and linked, and if you do
> >
> > arm-linux-objdump -Dr vmlinux |grep ipu_init
> >
> > you should see something like
> >
> > c0014c94 <ipu_init>:
> > c0014c94: e1a0c00d mov ip, sp
> > --
> > c0019c70 <__initcall_ipu_init4>:
> > c0019c70: c0014c94 mulgt r1, r4, ip
> >
>
> Well I have all of them ... Taht's why I really don't understand what's
> going on.
>
> However I don't have the same asm instruction for the initcall:
>
> c00192b4 <__initcall_ipu_init4>:
> c00192b4: c00141e8 .word 0xc00141e8
>
> But that's the address of my ipu_init
> c00141e8 <ipu_init>:
> c00141e8: e1a0c00d mov ip, sp
> c00141ec: e92dd800 push {fp, ip, lr, pc}
> c00141f0: e24cb004 sub fp, ip, #4 ; 0x4
>
> I think something is working badly with the initcall (subsys). Has
> someone already experienced something similar ?
Strange, try to look which initcalls are before and after ipu_init in your
kernel:
arm-linux-objdump -Dr vmlinux |grep __initcall_ |less
which on my kernel produces
...
c0019c6c <__initcall_input_init4>:
c0019c70 <__initcall_ipu_init4>:
c0019c74 <__initcall_proto_init4>:
...
and see whether those other two initcalls get called, if they do, then
either you're running a different kernel from the one you're looking at,
or it _does_ get called and you're debugging wrongly, or you have a very
selective memory corruption, or... a miracle is taking place.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
next prev parent reply other threads:[~2009-01-23 12:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 18:04 [PATCH 0/4 v8] i.MX31: dmaengine and framebuffer drivers Guennadi Liakhovetski
2009-01-08 18:04 ` [PATCH 1/4 v8] dmaengine: add async_tx_clear_ack() macro Guennadi Liakhovetski
2009-01-08 18:04 ` [PATCH 2/4 v8] i.MX31: Image Processing Unit DMA and IRQ drivers Guennadi Liakhovetski
2009-01-16 9:59 ` Sascha Hauer
2009-01-22 18:51 ` Valentin Longchamp
2009-01-22 19:04 ` Guennadi Liakhovetski
2009-01-22 19:48 ` Valentin Longchamp
2009-01-22 20:27 ` Guennadi Liakhovetski
2009-01-23 9:30 ` Valentin Longchamp
2009-01-23 9:46 ` Guennadi Liakhovetski
2009-01-23 11:22 ` Valentin Longchamp
2009-01-23 11:34 ` Russell King - ARM Linux
2009-01-23 12:13 ` Guennadi Liakhovetski [this message]
2009-01-23 13:01 ` Valentin Longchamp
2009-01-23 13:08 ` Russell King - ARM Linux
2009-01-23 13:12 ` Guennadi Liakhovetski
2009-01-23 13:18 ` Russell King - ARM Linux
2009-01-23 13:21 ` Valentin Longchamp
2009-01-23 13:25 ` Russell King - ARM Linux
2009-01-23 13:27 ` Guennadi Liakhovetski
2009-01-23 13:54 ` Holger Schurig
2009-01-23 20:55 ` Robert Schwebel
2009-01-23 13:22 ` Guennadi Liakhovetski
2009-01-23 13:26 ` Russell King - ARM Linux
2009-01-23 14:51 ` Valentin Longchamp
2009-01-23 15:09 ` Valentin Longchamp
2009-01-08 18:05 ` [PATCH 3/4 v8] i.MX31: framebuffer driver Guennadi Liakhovetski
2009-01-16 10:00 ` Sascha Hauer
2009-01-08 18:05 ` [PATCH 4/4 v8] i.MX31: platform bindings and initialisation for IPU and framebuffer drivers Guennadi Liakhovetski
2009-01-09 8:17 ` [PATCH 0/4 v8] i.MX31: dmaengine " Sascha Hauer
2009-01-09 8:27 ` Guennadi Liakhovetski
2009-01-09 10:09 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0901231308040.4463@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=dan.j.williams@intel.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=s.hauer@pengutronix.de \
--cc=valentin.longchamp@epfl.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox