Re: [PATCH v2] dt-bindings: rng: clocks property on omap_rng not always mandatory

2017-03-24 Thread Rob Herring
On Fri, Mar 24, 2017 at 09:19:05AM -0500, Rob Herring wrote: > On Fri, Mar 24, 2017 at 08:52:00AM -0500, Rob Herring wrote: > > On Fri, Mar 17, 2017 at 01:58:39PM +0100, Thomas Petazzoni wrote: > > > Commit 52060836f79 ("dt-bindings: omap-rng: Document SafeXcel IP-76 > > > device variant") update

Re: [PATCH v2] dt-bindings: rng: clocks property on omap_rng not always mandatory

2017-03-24 Thread Rob Herring
On Fri, Mar 24, 2017 at 08:52:00AM -0500, Rob Herring wrote: > On Fri, Mar 17, 2017 at 01:58:39PM +0100, Thomas Petazzoni wrote: > > Commit 52060836f79 ("dt-bindings: omap-rng: Document SafeXcel IP-76 > > device variant") update the omap_rng Device Tree binding to add support > > for the IP-76

Re: [PATCH v2] dt-bindings: rng: clocks property on omap_rng not always mandatory

2017-03-24 Thread Herbert Xu
On Fri, Mar 17, 2017 at 01:58:39PM +0100, Thomas Petazzoni wrote: > Commit 52060836f79 ("dt-bindings: omap-rng: Document SafeXcel IP-76 > device variant") update the omap_rng Device Tree binding to add support > for the IP-76 variation of the IP. As part of this change, a "clocks" > property was

Re: [PATCH v2] dt-bindings: rng: clocks property on omap_rng not always mandatory

2017-03-24 Thread Rob Herring
On Fri, Mar 17, 2017 at 01:58:39PM +0100, Thomas Petazzoni wrote: > Commit 52060836f79 ("dt-bindings: omap-rng: Document SafeXcel IP-76 > device variant") update the omap_rng Device Tree binding to add support > for the IP-76 variation of the IP. As part of this change, a "clocks" > property was