diff options
author | Nishanth Menon <nm@ti.com> | 2015-10-03 17:02:56 -0700 |
---|---|---|
committer | Santosh Shilimkar <ssantosh@kernel.org> | 2015-10-06 09:51:08 -0700 |
commit | 2df7b0f0d2268ecbcd59323fd09955e93d3fefbd (patch) | |
tree | 4d958b5635e97e4536f8c060b31df9e4bb96fbce /arch/arm/mach-keystone | |
parent | 1a344e9b7557a819b8143d7d7d4365b9694bb5e3 (diff) |
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>
Diffstat (limited to 'arch/arm/mach-keystone')
0 files changed, 0 insertions, 0 deletions