Linux Samsung SOC development
 help / color / mirror / Atom feed
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: Mon, 05 Nov 2012 23:26:05 +0100	[thread overview]
Message-ID: <50983CFD.2030104@gmail.com> (raw)
In-Reply-To: <CAA11ShD6Qug_=t8vGE5LwSpfXW2FsceTonxnF8aO6i2b=inibw@mail.gmail.com>

Hi Andrey,

On 11/05/2012 12:11 PM, Andrey Gusakov wrote:
> Hi.
>
> Thanks all!
> I make it work! Have to comment out write { REG_GRCOM, 0x3f },	/*

Great news!

Does the sensor still hang after 0x2f is written to REG_GRCOM instead ?

> Analog BLC&  regulator */ and have to enable gate clock for fimc at
> probe.

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 ?

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. :-)

>> Hmm, in my case VER was 0x50. PID, VER = 0x96, 0x50. And this a default
>> value
>> after reset according to the datasheet, ver. 1.3. For ver. 1.91 it is
>> PID, VER = 0x96, 0x52. Perhaps it just indicates ov9652 sensor ov9652.
>> Obviously I didn't test the driver with this one. Possibly the differences
>> can be resolved by comparing the documentation. Not sure if those are
>> significant and how much it makes sense to have single driver for both
>> sensor versions. I'll try to have a look at that.
> Ok. I also try to compate init sequenses from different sources on web.
>
> 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.

--
Regards,
Sylwester

  reply	other threads:[~2012-11-05 22:26 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 [this message]
2012-11-06 21:34               ` Andrey Gusakov
2012-11-07 21:57                 ` Sylwester Nawrocki
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=50983CFD.2030104@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox