Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | uhd: Add callback for setting sync_sources | Grant Meyerhoff | 2021-06-17 | 1 | -0/+6 |
| | |||||
* | uhd: Apply clang-format against all .cpp and .hpp files in host/ | Martin Braun | 2020-03-03 | 1 | -3/+4 |
| | | | | | Note: template_lvbitx.{cpp,hpp} need to be excluded from the list of files that clang-format gets applied against. | ||||
* | rfnoc: Allow MB controllers to init after blocks have initialized | Martin Braun | 2019-11-26 | 1 | -1/+120 |
| | | | | | | | | | | | | | | | | | | | | | This allows mb_controller childs to implement an init() call which rfnoc_graph will call after the block initialization is complete. rfnoc: graph/mb_controller: Add synchronization routine This adds two new API calls: * rfnoc_graph::synchronize_devices() and * mb_controller::synchronize(). The purpose is to synchronize devices in time and/or phase, depending on device capabilities. mb_controller childs can override or extend the default implementation, which is to simply set time next PPS and verify (similar to the set_time_unknown_pps() call in multi_usrp). rfnoc: mb_controller: Add gpio_src API Adds new API calls (get_gpio_src, get_gpio_srcs, set_gpio_src, get_gpio_banks) to mb_controllers | ||||
* | rfnoc: Add mb_controller API | Martin Braun | 2019-11-26 | 1 | -0/+73 |
The mb_controller is an interface to hardware-specific functions of the motherboard. The API works in two ways: - The user can request access to it, and thus interact directly with the motherboard - RFNoC blocks can request access to it, if they need to interact with the motherboard themselves. |