From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Darius Augulis <augulis.darius@gmail.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: soc_camera_open() not called
Date: Wed, 01 Apr 2009 20:37:27 +0200 [thread overview]
Message-ID: <87r60cmd94.fsf@free.fr> (raw)
In-Reply-To: <49D3AE13.9070201@gmail.com> (Darius Augulis's message of "Wed\, 01 Apr 2009 21\:10\:27 +0300")
Darius Augulis <augulis.darius@gmail.com> writes:
>>> Darius Augulis wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm trying to launch mx1_camera based on new v4l and soc-camera tree.
>>>> After loading mx1_camera module, I see that .add callback is not called.
>>>> In debug log I see that soc_camera_open() is not called too.
>>>> What should call this function? Is this my driver problem?
>>>> p.s. loading sensor driver does not change situation.
>>>>
>>
>> Are you by any chance using last 2.6.29 kernel ?
>> If so, would [1] be the answer to your question ?
>>
>> [1] http://lkml.org/lkml/2009/3/24/625
> thanks. it means we should expect soc-camera fix for this?
> I'm using 2.6.29-git8, but seems it's not fixed yet.
No, I don't think so.
The last time I checked there had to be an amendement to the patch which
introduced the driver core regression, as it touches other areas as well
(sound/soc and mtd from memory).
I think Guennadi can confirm this, as he's the one who raised the issue in the
first place.
Cheers.
--
Robert
next prev parent reply other threads:[~2009-04-01 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 14:04 soc_camera_open() not called Darius Augulis
2009-04-01 14:22 ` Darius Augulis
2009-04-01 17:55 ` Robert Jarzmik
2009-04-01 18:10 ` Darius Augulis
2009-04-01 18:37 ` Robert Jarzmik [this message]
2009-04-01 22:36 ` Guennadi Liakhovetski
2009-04-02 12:35 ` Darius Augulis
2009-04-02 13:15 ` Ming Lei
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=87r60cmd94.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=augulis.darius@gmail.com \
--cc=g.liakhovetski@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox