* omap3isp - set_xclk dont work
@ 2013-02-06 13:26 Adriano Martins
2013-02-07 17:03 ` Laurent Pinchart
0 siblings, 1 reply; 3+ messages in thread
From: Adriano Martins @ 2013-02-06 13:26 UTC (permalink / raw)
To: linux-media, Laurent Pinchart
Hi,
I have 2 boards with DM3730 processor, a beagleboard and a custom
board. The omap3isp is working in both boards, any error is seen. On
beagleboard I can see the xclka, then the sensor is detected and the
driver is load correctly.
But, in the custom board, every seem work, there are no errors too.
But I can't see the xclka signal.
The hardware is ok. Because, I load another driver that uses the
camera bus. The xclka is working.
it is the same processor, same kernel version, same driver.
Why, it work in one, and not another.
Someone can help me? please.
Thanks
Regards
Adriano Martins
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: omap3isp - set_xclk dont work
2013-02-06 13:26 omap3isp - set_xclk dont work Adriano Martins
@ 2013-02-07 17:03 ` Laurent Pinchart
2013-02-07 17:24 ` Adriano Martins
0 siblings, 1 reply; 3+ messages in thread
From: Laurent Pinchart @ 2013-02-07 17:03 UTC (permalink / raw)
To: Adriano Martins; +Cc: linux-media
Hi Adriano,
On Wednesday 06 February 2013 11:26:43 Adriano Martins wrote:
> Hi,
>
> I have 2 boards with DM3730 processor, a beagleboard and a custom board.
> The omap3isp is working in both boards, any error is seen. On beagleboard I
> can see the xclka, then the sensor is detected and the driver is load
> correctly. But, in the custom board, every seem work, there are no errors
> too. But I can't see the xclka signal.
>
> The hardware is ok. Because, I load another driver that uses the camera bus.
> The xclka is working.
>
> it is the same processor, same kernel version, same driver. Why, it work in
> one, and not another.
>
> Someone can help me? please.
The XCLK clocks currently require special handling in board code, with the
sensor calling back to board code when it wants to turn the clock on/off, and
board code calling the set_xclk isp operation. Does your board code perform
that operation ?
--
Regards,
Laurent Pinchart
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: omap3isp - set_xclk dont work
2013-02-07 17:03 ` Laurent Pinchart
@ 2013-02-07 17:24 ` Adriano Martins
0 siblings, 0 replies; 3+ messages in thread
From: Adriano Martins @ 2013-02-07 17:24 UTC (permalink / raw)
To: Laurent Pinchart; +Cc: linux-media
Hi Laurent,
2013/2/7 Laurent Pinchart <laurent.pinchart@ideasonboard.com>:
> Hi Adriano,
>
> On Wednesday 06 February 2013 11:26:43 Adriano Martins wrote:
>> Hi,
>>
>> I have 2 boards with DM3730 processor, a beagleboard and a custom board.
>> The omap3isp is working in both boards, any error is seen. On beagleboard I
>> can see the xclka, then the sensor is detected and the driver is load
>> correctly. But, in the custom board, every seem work, there are no errors
>> too. But I can't see the xclka signal.
>>
>> The hardware is ok. Because, I load another driver that uses the camera bus.
>> The xclka is working.
>>
>> it is the same processor, same kernel version, same driver. Why, it work in
>> one, and not another.
>>
>> Someone can help me? please.
>
> The XCLK clocks currently require special handling in board code, with the
> sensor calling back to board code when it wants to turn the clock on/off, and
> board code calling the set_xclk isp operation. Does your board code perform
> that operation ?
Yes, my board code has implemented the function.
I do a stupid mistake. My board code have not the mux settings in
these pins, including the XCLKA.
Now, I can see the clock.
Sorry for spend your time.
Thank you.
Regards
Adriano Martins
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-02-07 17:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-02-06 13:26 omap3isp - set_xclk dont work Adriano Martins
2013-02-07 17:03 ` Laurent Pinchart
2013-02-07 17:24 ` Adriano Martins
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox