fsi: Match fsi slaves and engines to available dt nodes
authorJeremy Kerr <jk@ozlabs.org>
Mon, 12 Feb 2018 05:15:45 +0000 (15:45 +1030)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 14 Mar 2018 18:11:00 +0000 (19:11 +0100)
commitf6a2f8eb73f0dfa7e9293a3ba08f6fcb61dfbbe1
tree826f37587c95ddda72a228a9cf287ce68c090d40
parent889ee9fe472af1a2407e3e604498a5edaf7f98ce
fsi: Match fsi slaves and engines to available dt nodes

This change populates device tree nodes for scanned FSI slaves and
engines. If the master populates ->of_node of the FSI master device,
we'll look for matching slaves, and under those slaves we'll look for
matching engines.

This means that FSI drivers will have their ->of_node pointer populated
if there's a corresponding DT node, which they can use for further
device discover.

Presence of device tree nodes is optional, and only required for
fsi device drivers that need extra properties, or subordinate devices,
to be enumerated.

Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/fsi/Kconfig
drivers/fsi/fsi-core.c
drivers/fsi/fsi-master-gpio.c
drivers/fsi/fsi-master-hub.c