Re: adv7281m and rcar-vin problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Naman,

On 2017-07-24 22:43:06 +0530, Naman Jain wrote:
> On Mon, Jul 24, 2017 at 3:11 PM, Niklas Söderlund
> <niklas.soderlund@xxxxxxxxxxxx> wrote:
> > Hi Naman,
> >
> > On 2017-07-24 14:30:52 +0530, Naman Jain wrote:
> >> i am using renesas soc with video decoder adv7281m
> >> i have done thr device tree configuration by following dt bindings
> >> i am getting timeout of reading the phy clock lane, after i start streaming
> >> and nothing is displayed on the screen
> >> kindly help me in configuration
> >
> > To be able to try and help you I would need a lot more information. For
> > starters:
> >
> > - Which kernel version are you using?
> >
> > - How dose the device tree nodes for VIN and ADV7281m look like?
> >
> > --
> > Regards,
> > Niklas Söderlund
> 
> Hi Niklas,
> 
> I am using kernel version  - 4.9

The VIN driver which supports CSI-2 and the R-Car CSI-2 driver is not a 
part of the upstream kernel yet, and the latest patches with contains 
the most fixes are based on newer kernels then v4.9. So I assume you are 
using a BSP of some sort, if possible could you tell me which one?

If you want to try with later increments of the VIN and CSI-2 patches 
please see:

http://elinux.org/R-Car/Tests:rcar-vin


> 
> following is the device tree configuration :
> 
> &i2c6 {
> status = "okay";
> clock-frequency = <400000>;
> adv7281m@21{
>                    compatible = "adi,adv7281-m";
>                    reg = <0x20>;
>                    interrupt-parent = <&gpio6>;
>                    interrupts = <4 IRQ_TYPE_LEVEL_LOW>
>                    adv7281m_out: endpoint {
>                                 clock-lanes = <0>;
>                                 data-lanes = <1>;
>                                 remote-endpoint = <&csi20_in>;
>                                  };
>                };
> 
> }
> 
> &csi20 {
>   status = "okay";
>   ports {
>          #address-cells = <1>;
>          #size-cells = <0>;
> 
>          port@0 {
>                         reg = <0>;
>                         csi20_in: endpoint {
>                                                    clock-lanes = <0>;
>                                                    data-lanes = <1>;
>                                                     virtual-channel-number=<0>;

This is interesting for me, I have not worked with any driver for the 
R-Car CSI-2 driver which understands the virtual-channel-number 
property.

>                                                    remote-endpoint =
> <&adv7281m_out>;
>                                             };
>                        };
>             };
> };
> 
> &vin0 {
> status = "okay";
> };
> 
> &vin1 {
> status = "okay";
> };
> 
> &vin2 {
> status = "okay";
> };
> 
> &vin3 {
> status = "okay";
> };
> 
> &vin4 {
> status = "okay";
> };
> 
> &vin5 {
> status = "okay";
> };
> 
> &vin6 {
> status = "okay";
> };
> 
> &vin7 {
> status = "okay";
> };

-- 
Regards,
Niklas Söderlund



[Index of Archives]     [Linux Samsung SOC]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux