From: Valentin Longchamp <valentin.longchamp@epfl.ch>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: "linux-fbdev-devel@lists.sourceforge.net"
<linux-fbdev-devel@lists.sourceforge.net>,
Dan Williams <dan.j.williams@intel.com>,
"linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>,
Longchamp Valentin <valentin.longchamp@epfl.ch>
Subject: Re: [PATCH 2/4 v8] i.MX31: Image Processing Unit DMA and IRQ drivers
Date: Fri, 23 Jan 2009 12:22:50 +0100 [thread overview]
Message-ID: <4979A88A.5010102@epfl.ch> (raw)
In-Reply-To: <Pine.LNX.4.64.0901231040420.4463@axis700.grange>
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 ?
Thanks
Val
--
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
next prev parent reply other threads:[~2009-01-23 11:22 UTC|newest]
Thread overview: 35+ 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 ` 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 [this message]
2009-01-23 11:34 ` Russell King - ARM Linux
2009-01-23 12:13 ` Guennadi Liakhovetski
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-08 18:05 ` 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-08 18:05 ` 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=4979A88A.5010102@epfl.ch \
--to=valentin.longchamp@epfl.ch \
--cc=dan.j.williams@intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.