From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Andrey Gusakov <dron0gus@gmail.com>
Cc: "Tomasz Figa" <tomasz.figa@gmail.com>,
"In-Bae Jeong" <kukyakya@gmail.com>,
"Heiko Stübner" <heiko@sntech.de>,
LMML <linux-media@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: S3C244X/S3C64XX SoC camera host interface driver questions
Date: Wed, 07 Nov 2012 22:57:43 +0100 [thread overview]
Message-ID: <509AD957.5070301@gmail.com> (raw)
In-Reply-To: <CAA11ShDAscm8snYzjnC3Fe1MaVXc-FJqhWM677iJwgbgu2_J1Q@mail.gmail.com>
On 11/06/2012 10:34 PM, Andrey Gusakov wrote:
> Hi.
>
>> Does the sensor still hang after 0x2f is written to REG_GRCOM instead ?
> Work!
> I'm looking at drivers/media/usb/gspca/m5602/m5602_ov9650.h
> It use significantly different init sequence. Some of settings
> described in Application note for ov9650, some look like magic.
I guess there are many ways the sensor can be configured initially.
I'd like to keep this initialization sequence as thin as possible,
and to move relevant settings to corresponding v4l2 controls.
Then after v4l2_control_handler_setup() is called, following the initial
register list write, the sensor would be configured into some known
state. I realize it might be more difficult in practice than it sounds
now. :-)
>> Do you have CONFIG_PM_RUNTIME enabled ? Can you try and see it works
>> if you enable it, without additional changes to the clock handling ?
> Work. With CONFIG_PM_RUNTIME and without enabling CLK_GATE at probe.
Ok, thanks. I will add the missing CONFIG_PM_RUNTIME dependency in Kconfig.
The driver has to have PM_RUNTIME enabled since on s3c64xx SoCs there are
power domains and the camera power domain needs to be enabled for the CAMIF
operation. The pm_runtime_* calls in the driver are supposed to ensure
that.
I wonder why it works for you without PM_RUNTIME, i.e. how comes the power
domain is enabled. It is supposed to be off by default.
>> I hope to eventually prepare the ov9650 sensor driver for mainline. Your
>> help in making it ready for VER=0x52 would be very much appreciated. :-)
> I'll try to helpful.
>
>
>>> Next step is to make ov2460 work.
>> For now I can only recommend you to make the ov2460 driver more similar
>> to the ov9650 one.
> Thanks, I'll try.
>
> P.S. I add support of image effects just for fun. And found in DS that
> s3c2450 also support effects. It's FIMC in-between of 2440 and
> 6400/6410. Does anyone have s3c2450 hardware to test it?
Patches adding image effect are welcome. I'm bit to busy to play with these
things, other than I don't have hardware to test it.
I wasn't really aware of CAMIF in s3c2450. I think a separate variant data
structure would need to be defined for s3c2450. If anyone ever needs it
it could be added easily. For now I'll pretend this version doesn't
exist. :-)
--
Regards,
Sylwester
next prev parent reply other threads:[~2012-11-07 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA11ShCpH7Z8eLok=MEh4bcSb6XjtVFfLQEYh2icUtYc-j5hEQ@mail.gmail.com>
[not found] ` <5096C561.5000108@gmail.com>
[not found] ` <CAA11ShCKFfdmd_ydxxCYo9Sv0VhgZW9kCk_F7LAQDg3mr5prrw@mail.gmail.com>
2012-11-04 22:14 ` S3C244X/S3C64XX SoC camera host interface driver questions Sylwester Nawrocki
2012-11-04 22:23 ` Tomasz Figa
2012-11-05 9:44 ` Andrey Gusakov
2012-11-05 10:48 ` Sylwester Nawrocki
2012-11-05 11:11 ` Andrey Gusakov
2012-11-05 22:26 ` Sylwester Nawrocki
2012-11-06 21:34 ` Andrey Gusakov
2012-11-07 21:57 ` Sylwester Nawrocki [this message]
2012-11-08 18:47 ` Andrey Gusakov
2012-11-09 8:14 ` Sylwester Nawrocki
2012-11-11 13:26 ` Andrey Gusakov
2012-11-13 22:54 ` Sylwester Nawrocki
2012-11-17 12:07 ` Andrey Gusakov
2012-11-17 17:24 ` Sylwester Nawrocki
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=509AD957.5070301@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=dron0gus@gmail.com \
--cc=heiko@sntech.de \
--cc=kukyakya@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tomasz.figa@gmail.com \
/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.