Kumar Gala

> @galak Currently there are no expectations for the USBC APIs to work with userspace, although this feature could be added at a later date. So my comment earlier about...

+1

Did some bisecting and got this commit causing issues: commit ee5a651aacaf2c3fbcd539789574618a425d1a06 (refs/bisect/bad) Author: Scott Shumate Date: Sun May 21 09:58:01 2017 -0500 Refactored to encapsulate all device-specific knowledge into the...

Here's a more runtime version of `dai_get_zephyr_driver`: ``` #define GET_DEVICE_LIST(node) DEVICE_DT_GET(node), const struct device * z_dev[] = { DT_FOREACH_STATUS_OKAY(intel_ssp_dai, GET_DEVICE_LIST) DT_FOREACH_STATUS_OKAY(intel_dmic, GET_DEVICE_LIST) DT_FOREACH_STATUS_OKAY(intel_alh_dai, GET_DEVICE_LIST) }; const struct device *dai_get_zephyr_driver(uint32_t type,...

> We've done a _lot_ of this sort of work for ZMK in https://github.com/zmkfirmware/zmk-docker if you want to see some strategies we've taken. > > We have separate build (for...

Does this really belong in the SDK? We have not included other such tools for other platforms in the past.

Please make sure to get @dcpleung for the UART driver.

I think part of the question here is what is considered part of the Zephyr "interface" beyond APIs? Is the build system, Kconfig, devicetree/devicetree bindings? Each of these areas could...

Various thoughts/comments: * So for devicetree this means that any change to an existing binding would possibly be a breaking API change. * How do we track the stability of...

@carlescufi mentioned this, but does API mean application facing or broader?