All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Janusz Uzycki <janusz.uzycki@elproma.com.pl>
Cc: g.daniluk@elproma.com.pl,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: SoC Camera driver and TV decoder
Date: Tue, 1 Feb 2011 15:32:58 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.1102011532360.6673@axis700.grange> (raw)
In-Reply-To: <18BE1662A1F04B6C8B39AA46440A3FBB@laptop2>

On Tue, 1 Feb 2011, Janusz Uzycki wrote:

> camera 0-0: Probing 0-0
> sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver attached to camera 0
> tvp5150 0-005d: chip found @ 0xba (i2c-sh_mobile)
> tvp5150 0-005d: tvp5150am1 detected.
> sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver detached from camera 0
> 
> There is no error 515 but the driver is still detached.

Good, this is correct. It will be re-attached when you open it.

Thanks
Guennadi

> drivers/media/video/sh_mobile_ceu_camera.c:
> sh_mobile_ceu_remove_device() is called /* Called with .video_lock held */
> static struct soc_camera_host_ops sh_mobile_ceu_host_ops = {
>        .owner          = THIS_MODULE,
>        .add            = sh_mobile_ceu_add_device,
>        .remove         = sh_mobile_ceu_remove_device,
> It seems sh_mobile_ceu_add_device() was failed.
> I will try to explore that.
> 
> Janusz
> 
> ----- Original Message ----- From: "Guennadi Liakhovetski"
> <g.liakhovetski@gmx.de>
> To: "Janusz Uzycki" <janusz.uzycki@elproma.com.pl>
> Cc: <g.daniluk@elproma.com.pl>; "Linux Media Mailing List"
> <linux-media@vger.kernel.org>
> Sent: Tuesday, February 01, 2011 2:21 PM
> Subject: Re: SoC Camera driver and TV decoder
> 
> 
> > On Tue, 1 Feb 2011, Janusz Uzycki wrote:
> > 
> > > include/linux/errno.h:#define ENOIOCTLCMD       515     /* No ioctl
> > > command */
> > > 
> > > What did I forget below?
> > > static const struct v4l2_subdev_video_ops tvp5150_video_ops = {
> > >        .s_routing = tvp5150_s_routing,
> > > 
> > >        /* SoC camera: */
> > >        .s_stream       = tvp5150_s_stream,
> > >        .g_mbus_fmt     = tvp5150_g_fmt,
> > >        .s_mbus_fmt     = tvp5150_s_fmt,
> > >        .try_mbus_fmt   = tvp5150_try_fmt,
> > >        .enum_mbus_fmt  = tvp5150_enum_fmt,
> > > /*      .cropcap        = tw9910_cropcap,
> > >        .g_crop         = tw9910_g_crop,
> > >        .s_crop         = tw9910_s_crop,*/
> > > };
> > > 
> > > cropcap/g_crop/s_cros are necessary? why and when?
> > 
> > cropcap and g_crop might be necessary - at least minimal static versions.
> > 
> > Thanks
> > Guennadi
> > 
> > > 
> > > thanks
> > > Janusz
> > > 
> > > 
> > > > On Thu, 27 Jan 2011, Janusz Uzycki wrote:
> > > >
> > > > > Hello Guennadi again.
> > > > >
> > > > > I patched tvp5150.c according to tw9910 driver (without real cropping
> > > > > support yet).
> > > > > Unfortunately I got the messages:
> > > > > camera 0-0: Probing 0-0
> > > > > sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver attached to >
> > > > camera
> > > > > 0
> > > > > tvp5150 0-005d: chip found @ 0xba (i2c-sh_mobile)
> > > > > tvp5150 0-005d: tvp5150am1 detected.
> > > >
> > > > This looks good - i2c to the chip works!
> > > >
> > > > > sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver detached from
> > > > > camera 0
> > > > > camera: probe of 0-0 failed with error -515
> > > >
> > > > This is strange, however - error code 515... Can you try to find out >
> > > where
> > > > it is coming from?
> > > >
> > > > Thanks
> > > > Guennadi
> > > >
> > > 
> > 
> > ---
> > Guennadi Liakhovetski, Ph.D.
> > Freelance Open-Source Software Developer
> > http://www.open-technology.de/
> > 
> 

---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

  reply	other threads:[~2011-02-01 14:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1E539FC23CF84B8A91428720570395E0@laptop2>
     [not found] ` <Pine.LNX.4.64.1101241720001.17567@axis700.grange>
     [not found]   ` <AD14536027B946D6B4504D4F43E352A5@laptop2>
     [not found]     ` <Pine.LNX.4.64.1101262045550.3989@axis700.grange>
2011-01-27 16:21       ` SoC Camera driver and TV decoder Janusz Uzycki
     [not found]       ` <F95361ABAE1D4A70A10790A798004482@laptop2>
2011-01-27 17:10         ` Guennadi Liakhovetski
2011-01-27 18:15           ` Janusz Uzycki
2011-02-01 13:17           ` Janusz Uzycki
2011-02-01 13:21             ` Guennadi Liakhovetski
2011-02-01 14:29               ` Janusz Uzycki
2011-02-01 14:32                 ` Guennadi Liakhovetski [this message]
     [not found]                   ` <2F2263A44E0F466F898DD3E2F1D19F12@laptop2>
     [not found]                     ` <Pine.LNX.4.64.1102081427500.1393@axis700.grange>
2012-06-04 17:32                       ` SH7724, VOU, PAL mode Janusz Uzycki
2012-06-05 15:47                         ` Guennadi Liakhovetski
2012-06-05 22:37                           ` Janusz Uzycki
2012-06-06 14:22                             ` Guennadi Liakhovetski
2012-06-06 17:39                               ` Janusz Uzycki
2012-06-08  8:43                                 ` Guennadi Liakhovetski
2012-06-06  1:56                           ` Laurent Pinchart

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.1102011532360.6673@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=g.daniluk@elproma.com.pl \
    --cc=janusz.uzycki@elproma.com.pl \
    --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.