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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL8zT=goqUXzK+HhxrJf=ZRTGgcT4agyR+QY9BYV3gtfWvZH4g@mail.gmail.com>
Date:	Fri, 9 Jan 2015 09:38:38 +0100
From:	Jean-Michel Hautbois <jean-michel.hautbois@...alys.com>
To:	Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc:	Linux Media Mailing List <linux-media@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	wsa@...-dreams.de, Lars-Peter Clausen <lars@...afoo.de>,
	Hans Verkuil <hverkuil@...all.nl>
Subject: Re: [PATCH] adv7604: Add DT parsing support

Hi,

2014-10-27 0:30 GMT+01:00 Laurent Pinchart <laurent.pinchart@...asonboard.com>:
> Hi Jean-Michel,
>
> On Thursday 23 October 2014 07:51:50 Jean-Michel Hautbois wrote:
>> 2014-10-23 1:53 GMT+02:00 Laurent Pinchart:
>> > On Wednesday 22 October 2014 17:34:21 Jean-Michel Hautbois wrote:
>> >> This patch adds support for DT parsing of ADV7604 as well as ADV7611.
>> >> It needs to be improved in order to get ports parsing too.
>> >
>> > Let's improve it then :-) The DT bindings as proposed by this patch are
>> > incomplete, that's just asking for trouble.
>> >
>> > How would you model the adv7604 ports ?
>>
>> I am opened to suggestions :).
>> But it has to remain as simple as possible, ideally allowing for giving
>> names to the ports.
>> As done today, it works, ports are parsed but are all the same...
>
> The ADV7611 was easy, it had a single HDMI input only. The ADV7612 is easy as
> well as it just has two separate HDMI inputs.
>
> The ADV7604 is a more complex beast. The HDMI inputs shouldn't be much of an
> issue as they're independent and multiplexed internally. You can just create
> one pad per HDMI input.
>
> The analog inputs, however, can't be modeled as easily. A naive approach would
> be to create one pad for each of the 12 analog inputs, but the chip has three
> separate ADCs and can combine 3 inputs in a single digital video stream. I
> don't know how we should model support for that. Lars-Peter, Hans, would you
> have a revolutionary idea to same the world today ?

I get back to working on this specific part, but I don't know how
these analog inputs should be modeled.
On page 68 of ADV7604_HW_RevF there is Figure 11 showing typical
configurations using AIN_SEL[2:0].
I can see 4 inputs muxed : this would suggest to have 4 pads for analog inputs.
Not sure it makes sense though...

Thanks,
JM
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ