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>
Subject: Re: [PATCH 2/4 v8] i.MX31: Image Processing Unit DMA and IRQ drivers
Date: Fri, 23 Jan 2009 10:30:50 +0100 [thread overview]
Message-ID: <49798E4A.4030709@epfl.ch> (raw)
In-Reply-To: <Pine.LNX.4.64.0901222122150.7935@axis700.grange>
Guennadi Liakhovetski wrote:
> On Thu, 22 Jan 2009, Valentin Longchamp wrote:
>
>> Guennadi Liakhovetski wrote:
>>> On Thu, 22 Jan 2009, Valentin Longchamp wrote:
>>>
>>> You need the patch 4/4 - platform bindings, which is not in that queue and
>>> will only be merged in the next kernel version. You can so far pick it up
>>> here:
>>>
>>> http://marc.info/?l=linux-arm-kernel&m=123143901514438&w=2
>>>
>> I have the platform bindings, the ipu-core platform_device (from patch 4/4) is
>> registered on my system. It's only the ipu-core platform_driver (from patch
>> 2/4) that is not registered and I don't understand why.
>
> Ok, you didn't mention this in your previous mail. I don't think the
> platform-driver is not registered. Can you check whether the ipu_init()
> function gets called? Looks like the ipu platform device is not registered
> on your system. Look at patch 4/4. In your board code you do something
> like
>
> + mx3_register_fb(fb_modedb[0].name, fb_modedb, ARRAY_SIZE(fb_modedb));
Yes I do this in my board initialisation code. Yes I have it and it also
works, see below.
>
> in that function
>
> + if (!ipu_registered) {
> + int ret = platform_device_register(&mx3_ipu);
Yes I also have this in my devices.c file (just as you proposed it in
your 4/4 patch). And if works, see below.
>
> Do you have the ipu platform device under /sys/devices/platform/?
>
Yes I do have it. But I do not it under /sys/bus/platform/drivers.
> root@mx31moboard:~# ls -al /sys/devices/platform/
> drwxr-xr-x 8 root root 0 Oct 16 14:04 .
> drwxr-xr-x 4 root root 0 Oct 16 14:04 ..
> drwxr-xr-x 2 root root 0 Oct 16 14:04 imx-uart.0
> drwxr-xr-x 2 root root 0 Oct 16 14:04 imx-uart.1
> drwxr-xr-x 2 root root 0 Oct 16 14:04 imx-uart.4
> drwxr-xr-x 2 root root 0 Oct 16 14:04 ipu_core
> drwxr-xr-x 2 root root 0 Oct 16 14:04 mx3_sdc_fb
> drwxr-xr-x 2 root root 0 Oct 16 14:04 physmap-flash.0
> -rw-r--r-- 1 root root 4096 Oct 16 14:04 uevent
> root@mx31moboard:~# ls -al /sys/bus/platform/drivers
> drwxr-xr-x 6 root root 0 Oct 16 13:50 .
> drwxr-xr-x 4 root root 0 Jan 1 1970 ..
> drwxr-xr-x 2 root root 0 Jan 1 1970 generic-bl
> drwxr-xr-x 2 root root 0 Jan 1 1970 imx-uart
> drwxr-xr-x 2 root root 0 Oct 16 14:05 mx3_sdc_fb
> drwxr-xr-x 2 root root 0 Jan 1 1970 physmap-flash
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.
Thanks for your help.
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 9:31 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 [this message]
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
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=49798E4A.4030709@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 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).