| author | Misael Lopez Cruz <misael.lopez@ti.com> | |
| Thu, 29 Apr 2021 20:45:50 +0000 (15:45 -0500) | ||
| committer | Ankur <ankurbaranwal@ti.com> | |
| Sun, 2 May 2021 14:13:34 +0000 (09:13 -0500) | ||
| commit | 7838afb094e05e28c49cf4ff94f0414854942257 | |
| tree | f70c1b674e09d7a37110a8386e1c207c3f090a5e | tree | snapshot (tar.xz tar.gz zip) |
| parent | 63238bb7aef515dce407a6b3f016ac3d46771198 | commit | diff |
board: am65xx: Use PDK-relative path for pinmux.h
If an application wants to set their own pinmux, it has to include board
library's internal am65xx_idk_pinmux.h header file as the header files
in its component include/ directory are not enough.
The internal header files included in am65xx_idk_pinmux.h would need to
include the pah relative to PDK, otherwise applications will not be able
to find them. That's the case of pinmux.h which is included, but path
is not relative to PDK base dir.
Signed-off-by: Misael Lopez Cruz <misael.lopez@ti.com>
If an application wants to set their own pinmux, it has to include board
library's internal am65xx_idk_pinmux.h header file as the header files
in its component include/ directory are not enough.
The internal header files included in am65xx_idk_pinmux.h would need to
include the pah relative to PDK, otherwise applications will not be able
to find them. That's the case of pinmux.h which is included, but path
is not relative to PDK base dir.
Signed-off-by: Misael Lopez Cruz <misael.lopez@ti.com>