Hi.
On Mon, Jan 21, 2013 at 12:07 PM, Alexander Nestorov
wrote:
> Hi,
>
> I see. Maybe you already saw it, but just in case, I found this[1] I
> hope it helps.
Thanks. It s looks like code from 2.6.28, I'll take a closer look.
> Do you plan sharing your code in GitHub or equivalent? I'm working
Hi.
On Mon, Jan 21, 2013 at 12:46 AM, Alexander Nestorov
wrote:
> Hi,
>
> I have been playing for a week with the board. Both audio and video
> work correctly, but I haven't
> been able to set the mic settings in alsamixer (so I can't test the mic).
> The touchscreen isn't working, so I'll try to
Hi,
On Sat, Jan 12, 2013 at 9:07 PM, Alexander Nestorov
wrote:
> Hi,
>
> it's finally working! :)
>
> This is my entire diff: http://pastie.org/5674242 (note: it doesn't include
> sound/soc/samsung/mini6410_wm9713.c file, which is a copy of the
> smdk6410_wm9713.c file)
> Here's the mini6410_wm9
Hi.
I also had some problems with WM9714 on mini6410. The problem was
write to register 0x00 of coded. That is SW reset command. I had no
time to deal with it, so I just filter out all writes to register 0x00
in samsung AC97 driver. May be it can help you.
http://comments.gmane.org/gmane.linux.als
Hi.
Just have time to test. I apologize for delay.
> I'd like to squash all the s3c-camif patches before sending upstream,
> if you don't mind. And to add your Signed-off at the final patch.
Ok. Squash.
> I might have introduced bugs in the image effects handling, hopefully
> there is none. I co
Hi.
Patch v2 attached. Comments taken into account.
>> I often get "VIDIOC_QUERYCAP: failed: Inappropriate ioctl for device"
> This is an issue in the v4l2-ctl, it is going to be fixed by adding
> VIDIOC_SUBDEV_QUERYCAP ioctl for subdevs. It has been just discussed today.
> I guess you get it whe
Hi.
On Fri, Nov 9, 2012 at 12:32 PM, Sylwester Nawrocki
wrote:
> The "camera" clock defined in arch/arm/mach-s3c64xx/clock.c has null
> clock source mux control register as it can have only one parent
> clock. In such cases there is a need to configure the parent clock
> statically, otherwise s3c
Hi.
I think .reg_src can be removed? This clock have only one source.
On Thu, Nov 8, 2012 at 2:00 AM, Sylwester Nawrocki
wrote:
> The "camera" clock defined in arch/arm/mach-s3c64xx/clock.c has null
> clock source mux control register as it can have only one parent
> clock. In such cases there i
Hi.
On Thu, Nov 8, 2012 at 1:57 AM, Sylwester Nawrocki
wrote:
> 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 d
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.
> Do you have CONFIG_PM_RU
Hi.
Thanks all!
I make it work! Have to comment out write { REG_GRCOM, 0x3f }, /*
Analog BLC & regulator */ and have to enable gate clock for fimc at
probe.
> 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 v
Hi.
>> But documentation on ov9650 is too conflicting and did not cover all
>> registers used in driver.
> Do you mean the OV9650 datasheet, version 1.3, from September 24, 2004 ?
Yes. Also I have datasheet version 1.91 from January 28, 2005 and
Application note 1.1 from 7 December 2004
All can be
Hi
Tested-by: Andrey Gusakov
Tested on custom S3C2416 hardware.
Boot tested. Freq scalling tested. Core voltage scalling (1.3V and
1.05 V) tested.
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majord...@vger.kernel.org
More
13 matches
Mail list logo
