This change introduces the "_rtc_timer" suffix for the system tick timer
driver "compatible" property and aligns naming conventions with the
actual CC13/26xx SoC series product policy.
This frees up the "_rtc" namespace to introduce additional APIs based on
the same peripheral in the future (not part of this PR):
rtc: rtc@... {
compatible = "ti,cc13xx-cc26xx-rtc";
...
timer {
compatible = "ti,cc13xx-cc26xx-rtc-timer";
...
};
counter {
compatible = "ti,cc13xx-cc26xx-rtc-counter";
...
};
pps {
compatible = "ti,cc13xx-cc26xx-rtc-pps";
...
};
};
Or alternatively an MFD pattern with similar requirements.
Fixing the namespacing now makes sense standalone as it reduces the
chance of custom drivers being broken in the future.
Redundant extension of the mandatory system clock devicetree node is
replaced with a single `status = "okay"` which seems to be the more
sensible default to avoid user error when defining custom boards.
Knowledgeable users can still override this if really needed.
Signed-off-by: Florian Grandel <fgrandel@code-for-humans.de>
Add support for BeagleConnect Freedom, a TI CC1352P7 based development
board with enclosure and antenna featuring BLE and SubGHz wireless, 2x
mikroBUS sockets, external flash, light, temperature/humidity sensors,
USB-to-UART bridge, buzzer and battery charger.
See https://beagleconnect.org for details.
Previous closed pull requests:
* https://github.com/zephyrproject-rtos/zephyr/pull/38718
* https://github.com/zephyrproject-rtos/zephyr/pull/36703
Cc: Chris Friedt <chris@friedt.co>
Signed-off-by: Jason Kridner <jkridner@beagleboard.org>
Signed-off-by: Vaishnav Achath <vaishnav@beagleboard.org>
Signed-off-by: Erik Larson <erik@statropy.com>
Signed-off-by: Yadnik Bendale <yadnik22@gmail.com>
Signed-off-by: Baozhu Zuo <zuobaozhu@gmail.com>
