Thread (1 message) flat view 1 message, 1 author, 2013-05-24

Re: [PATCH 5/6] crypto: ux500/cryp - Enable DT probing of the driver

From: Linus Walleij <hidden>
Date: 2013-05-24 11:16:46
Also in: linux-arm-kernel, linux-crypto, lkml

On Fri, May 24, 2013 at 10:32 AM, Lee Jones [off-list ref] wrote:
On Fri, 24 May 2013, Linus Walleij wrote:
quoted
On Thu, May 16, 2013 at 1:27 PM, Lee Jones [off-list ref] wrote:
quoted
By providing an OF match table with a suitable compatible string, we
can ensure the ux500-crypt driver is probed by supplying an associated
DT node in a given platform's Device Tree.

Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Signed-off-by: Lee Jones <redacted>
Herbert, can I have your ACK on patch 5 & 6 in this series to take it
through the ARM SoC tree?
Right, there are no bindings, so they don't need a document.
Surely the requirement that the node must have <reg>,
<irqs> and <regulator> for the driver to even probe is a
binding?

The fact that the drivers/of/* core on Linux will auto-populate
platform devices with those properties is a pure Linux
pecularity, and the bindings are there for OS independence.

Whether we need to document it for such standard things
is another thing, hopefully Rob or someone can answer that?

Yours,
Linus Walleij
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help