All of lore.kernel.org
 help / color / mirror / Atom feed
From: Agustin <gatoguan-os@yahoo.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Arm Kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH/RFC 1/4] ipu_idmac: code clean-up and robustness improvements
Date: Mon, 2 Mar 2009 06:50:04 -0800 (PST)	[thread overview]
Message-ID: <26939.71342.qm@web32107.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0902282253210.20549@axis700.grange>


--- On 28/2/09, Guennadi Liakhovetski wrote:
> On Sat, 28 Feb 2009, Agustin wrote:
>> 
>> Hi Guennadi,
>> 
>> I am having trouble while probing ipu idmac:
>> 
>> At boot:
>> ipu-core: probe of ipu-core failed with error -22
>> 
>> Which is apparently happening at ipu_idmac:1706:
>>    1695 static int __init ipu_probe(struct platform_device *pdev)
>>    ...
>>    1703         mem_ipu = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>>    1704         mem_ic  = platform_get_resource(pdev, IORESOURCE_MEM, 1);
>>    1705         if (!pdata || !mem_ipu || !mem_ic)
>>    1706                 return -EINVAL;
>> 
>> Later on, I get error 16, "Device or resource busy" on
VIDIOC_S_FMT, apparently because mx3_camera can't get its dma channel.
>> 
>> Any clue?
>
>Are you sure it is failing here, have you verified with a printk? If it is 
>indeed this place, then you probably didn't register all required 
>resources in your platfom code. Look at my platform-bindings patch.
>
>Thanks
>Guennadi

Thanks, I was missing "mx3_ipu_data" struct at devices.c file. It happened because I had git-pulled Valentin's older patch from mxc-master which made your patch fail a few chunks, then the code was very similar when I checked it visually.

Now let's see if I can get back on track with my new hardware design and take those pics...

Regards,
--Agustín.


  reply	other threads:[~2009-03-02 14:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 18:36 Rv: mx3-camera on current mxc kernel tree Agustin
     [not found] ` <499B2A60.9080009@epfl.ch>
2009-02-17 22:12   ` Guennadi Liakhovetski
2009-02-18  0:02   ` [PATCH/RFC 0/4] i.MX31 camera host driver + IPU updates Guennadi Liakhovetski
2009-02-18  0:03     ` [PATCH/RFC 1/4] ipu_idmac: code clean-up and robustness improvements Guennadi Liakhovetski
2009-02-18 15:09       ` Agustin
2009-02-18 15:21         ` Guennadi Liakhovetski
2009-02-18 20:07         ` Russell King - ARM Linux
2009-02-18 21:32           ` Agustin
2009-02-28 21:31       ` Agustin
2009-02-28 21:55         ` Guennadi Liakhovetski
2009-03-02 14:50           ` Agustin [this message]
2009-02-18  0:03     ` [PATCH 2/4] soc-camera: camera host driver for i.MX3x SoCs Guennadi Liakhovetski
2009-02-19 10:57       ` Sascha Hauer
2009-02-18  0:03     ` [PATCH/FYI 3/4] soc-camera: board bindings for " Guennadi Liakhovetski
2009-02-18  0:04     ` [PATCH 4/4] mt9t031: fix gain and hflip controls, register update, and scaling Guennadi Liakhovetski
2009-02-18  9:13 ` Rv: mx3-camera on current mxc kernel tree Sascha Hauer
2009-02-18 11:32   ` Agustin

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=26939.71342.qm@web32107.mail.mud.yahoo.com \
    --to=gatoguan-os@yahoo.com \
    --cc=dan.j.williams@intel.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-media@vger.kernel.org \
    /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.