Documentation: dt: keystone: provide SoC specific compatible flags
authorNishanth Menon <nm@ti.com>
Sun, 4 Oct 2015 00:02:56 +0000 (17:02 -0700)
committerSantosh Shilimkar <ssantosh@kernel.org>
Tue, 6 Oct 2015 16:51:08 +0000 (09:51 -0700)
commit2df7b0f0d2268ecbcd59323fd09955e93d3fefbd
tree4d958b5635e97e4536f8c060b31df9e4bb96fbce
parent1a344e9b7557a819b8143d7d7d4365b9694bb5e3
Documentation: dt: keystone: provide SoC specific compatible flags

Keystone2 devices are used on more platforms than just Texas
Instruments reference evaluation platforms called EVMs. Providing a
generic compatible "ti,keystone" is not sufficient to differentiate
various SoC definitions possible on various platforms for the
following reasons:
a) Userspace applications have no way of knowing which SoC they are
functioning, providing the compatible matches provide a mechanism for
them to enable SoC specific functionality. Such userspace applications
are typically automated test framework or SoC custom hardware
acceleration entitlement from a common file system.
b) Provides an accurate hardware description. This allows
SoC specific logic to be run time handled based on
of_machine_is_compatible("ti,k2hk") or as needed for the dependent
processor instead of needing to use board dependent compatibles that
are needed now.

Hence, provide compatible matches for each SoC in the Keystone family.

Acked-By: Murali Karicheri <m-karicheri2@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Santosh Shilimkar <ssantosh@kernel.org>
Documentation/devicetree/bindings/arm/keystone/keystone.txt