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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 08 Mar 2014 01:20:57 +0800
From:	Grant Likely <>
To:	Tomi Valkeinen <>,
	Philipp Zabel <>
Cc:	Russell King - ARM Linux <>,
	Mauro Carvalho Chehab <>,
	Rob Herring <>,
	Sylwester Nawrocki <>,
	Laurent Pinchart <>,
	Kyungmin Park <>,,,,
	Guennadi Liakhovetski <>
Subject: Re: [PATCH v4 3/3] Documentation: of: Document graph bindings

On Wed, 26 Feb 2014 15:14:17 +0200, Tomi Valkeinen <> wrote:
> On 25/02/14 16:58, Philipp Zabel wrote:
> > +Optional endpoint properties
> > +----------------------------
> > +
> > +- remote-endpoint: phandle to an 'endpoint' subnode of a remote device node.
> Why is that optional? What use is an endpoint, if it's not connected to
> something?
> Also, if this is being worked on, I'd like to propose the addition of
> simpler single-endpoint cases which I've been using with OMAP DSS. So if
> there's just a single endpoint for the device, which is very common, you
> can have just:
> device {
> 	...
> 	endpoint { ... };
> };
> However, I guess that the patch just keeps growing and growing, so maybe
> it's better to add such things later =).

It's good to talk about it now while boiling down the core behaviour
into a useful pattern. That said, I think if the stuff I've commented on
already is addressed then it will probably be sufficient for me to ack
or merge the change.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists