[EXT_EP-10544] Split Display library by DeviceFamily Created: 15/Sep/21 Updated: 15/Sep/21 Resolved: 15/Sep/21 |
|
| Status: | Implemented |
| Project: | Embedded Software & Tools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Enhancement | Priority: | High |
| Reporter: | TI User | Assignee: | TI User |
| Resolution: | Implemented | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Product: | TI Device Drivers |
| Internal ID: | TIDRIVERS-5029 |
| Fix In Release: | TIDRIVERS_5_70_00 |
| Affected Platform/Device: | CC32xx CC13x1 CC26x1 CC13x2 CC26x2 CC13x2x7 CC26x2x7 CC13x4 CC26x4 CC23x0 |
| Description |
|
The Display library today is built once for each CPU architecture we support. This means it does not have a DeviceFamily define, which breaks the new GPIO driver - Display uses GPIO for interacting with the LED when configured. We should ship all the permutations of display_ccXXXX as we do for drivers. This means a compatibility break, since we can no longer link the different display.a libraries that we have today. |