linux-kernel - Re: [PATCH] ARM: at91/dt: ov2640: add hsync/vsync-active property

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <56001221.6020604@atmel.com>
Date:	Mon, 21 Sep 2015 16:20:17 +0200
From:	Nicolas Ferre <nicolas.ferre@...el.com>
To:	Josh Wu <josh.wu@...el.com>
CC:	<linux-arm-kernel@...ts.infradead.org>,
	Russell King <linux@....linux.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	"Jean-Christophe Plagniol-Villard" <plagnioj@...osoft.com>,
	<linux-kernel@...r.kernel.org>,
	"Ian Campbell" <ijc+devicetree@...lion.org.uk>,
	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	<devicetree@...r.kernel.org>, "Rob Herring" <robh+dt@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH] ARM: at91/dt: ov2640: add hsync/vsync-active property

Le 21/09/2015 03:19, Josh Wu a écrit :
> Hi, Nicolas
> 
> On 9/18/2015 10:09 PM, Nicolas Ferre wrote:
>> Le 18/09/2015 13:28, Josh Wu a écrit :
>>> On at91sam9x5ek/at91sam9m10g45ek/sama5d3xek boards, we use the parallel
>>> connection for ov2640. So we must set the hsync/vsync property (1 means
>>> active high).
>>> Otherwise, the connection would be seen as BT.656 or BT.1120.
>>>
>>> Signed-off-by: Josh Wu <josh.wu@...el.com>
>> Hi Josh,
>>
>> Does this patch apply because of the new enhancement that you had
>> proposed in "media: atmel-isi: parse the DT parameters for
>> vsync/hsync/pixclock polarity" or does it apply even before?
>> Is it a fix that applies to older kernels?
> It's is a fix, according to the dt binding of video interface.
> So it should be applied before:
> 
> "media: atmel-isi: parse the DT parameters for
> vsync/hsync/pixclock polarity".
> 
> 
> it has no impact in older kernel as the driver doesn't parse that 
> property yet.
> 
>>
>> So, should I wait for the enhancements to enter media git tree or can I
>> take them anyway?
> 
> yes, you can take it without waiting for the media tree. Thanks.

Fair enough.

Acked-by: Nicolas Ferre <nicolas.ferre@...el.com>

Thanks for the information. Bye,

> Best Regards,
> Josh Wu
> 
>>
>> Bye,
>>
>>> ---
>>>
>>>   arch/arm/boot/dts/at91sam9m10g45ek.dts | 2 ++
>>>   arch/arm/boot/dts/at91sam9x5ek.dtsi    | 2 ++
>>>   arch/arm/boot/dts/sama5d3xmb.dtsi      | 2 ++
>>>   3 files changed, 6 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/at91sam9m10g45ek.dts b/arch/arm/boot/dts/at91sam9m10g45ek.dts
>>> index d1ae60a..9d16ef8 100644
>>> --- a/arch/arm/boot/dts/at91sam9m10g45ek.dts
>>> +++ b/arch/arm/boot/dts/at91sam9m10g45ek.dts
>>> @@ -198,6 +198,8 @@
>>>   					isi_0: endpoint {
>>>   						remote-endpoint = <&ov2640_0>;
>>>   						bus-width = <8>;
>>> +						vsync-active = <1>;
>>> +						hsync-active = <1>;
>>>   					};
>>>   				};
>>>   			};
>>> diff --git a/arch/arm/boot/dts/at91sam9x5ek.dtsi b/arch/arm/boot/dts/at91sam9x5ek.dtsi
>>> index d237c46..479f200 100644
>>> --- a/arch/arm/boot/dts/at91sam9x5ek.dtsi
>>> +++ b/arch/arm/boot/dts/at91sam9x5ek.dtsi
>>> @@ -66,6 +66,8 @@
>>>   					isi_0: endpoint@0 {
>>>   						remote-endpoint = <&ov2640_0>;
>>>   						bus-width = <8>;
>>> +						vsync-active = <1>;
>>> +						hsync-active = <1>;
>>>   					};
>>>   				};
>>>   			};
>>> diff --git a/arch/arm/boot/dts/sama5d3xmb.dtsi b/arch/arm/boot/dts/sama5d3xmb.dtsi
>>> index 83bee7a..8901042 100644
>>> --- a/arch/arm/boot/dts/sama5d3xmb.dtsi
>>> +++ b/arch/arm/boot/dts/sama5d3xmb.dtsi
>>> @@ -87,6 +87,8 @@
>>>   					isi_0: endpoint {
>>>   						remote-endpoint = <&ov2640_0>;
>>>   						bus-width = <8>;
>>> +						vsync-active = <1>;
>>> +						hsync-active = <1>;
>>>   					};
>>>   				};
>>>   			};
>>>
>>
> 
> 


-- 
Nicolas Ferre
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/