Searched refs:year (Results 1 – 10 of 10) sorted by relevance
| /rk3399_ARM-atf/plat/imx/common/include/sci/svc/timer/ |
| H A D | sci_timer_api.h | 210 sc_err_t sc_timer_set_rtc_time(sc_ipc_t ipc, uint16_t year, uint8_t mon, 227 sc_err_t sc_timer_get_rtc_time(sc_ipc_t ipc, uint16_t *year, uint8_t *mon, 259 sc_err_t sc_timer_set_rtc_alarm(sc_ipc_t ipc, uint16_t year, uint8_t mon,
|
| /rk3399_ARM-atf/include/lib/cpus/ |
| H A D | errata.h | 110 #define CVE(year, id) year, id argument
|
| /rk3399_ARM-atf/plat/imx/common/sci/svc/timer/ |
| H A D | timer_rpc_clnt.c | 191 sc_err_t sc_timer_set_rtc_time(sc_ipc_t ipc, uint16_t year, uint8_t mon, in sc_timer_set_rtc_time() argument 201 RPC_U16(&msg, 0U) = (uint16_t)year; in sc_timer_set_rtc_time() 215 sc_err_t sc_timer_get_rtc_time(sc_ipc_t ipc, uint16_t *year, uint8_t *mon, in sc_timer_get_rtc_time() argument 229 if (year != NULL) in sc_timer_get_rtc_time() 230 *year = RPC_U16(&msg, 0U); in sc_timer_get_rtc_time() 270 sc_err_t sc_timer_set_rtc_alarm(sc_ipc_t ipc, uint16_t year, uint8_t mon, in sc_timer_set_rtc_alarm() argument 280 RPC_U16(&msg, 0U) = (uint16_t)year; in sc_timer_set_rtc_alarm()
|
| /rk3399_ARM-atf/include/drivers/brcm/ |
| H A D | fru.h | 111 unsigned int year; member
|
| /rk3399_ARM-atf/licenses/ |
| H A D | LICENSE.MIT | 3 Copyright (c) [year] [fullname]
|
| /rk3399_ARM-atf/docs/about/ |
| H A D | lts.rst | 89 the year should the releases be made. 97 There are many challenges that may influence the 7 year support from CI 105 3. Which time(s) of the year should the releases be made? 107 TF-A releases are cut twice a year: May and November. Basing LTS release 109 LTS releases which happen towards the end of each year. Second, it aligns 110 with Android releases which tend to fall in Q3 each year. Since product 113 Q3 following year. On the other hand, if the May release of TF-A is chosen as 118 To summarize, there will be one LTS release per year. It will be supported for
|
| /rk3399_ARM-atf/plat/brcm/board/stingray/src/ |
| H A D | bl2_setup.c | 441 fru_tm.year, fru_tm.month, fru_tm.day, in board_detect_fru()
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | contributing.rst | 82 where XXXX is the year of first contribution (if different to YYYY) and YYYY 83 is the year of most recent contribution. <OWNER> is your name or your company
|
| /rk3399_ARM-atf/docs/ |
| H A D | architecture_features.rst | 5 almost every year listed in `Feature_description`_. While most of these features require no control
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | firmware-design.rst | 1597 CVEs have the format ``CVE_<year>_<number>``. To fit them in the framework, the 1600 registration should instead be ``CVE(<year>, <number>)``. In the extremely 1604 Also, their build flag should be ``WORKAROUND_CVE_<year>_<number>``. 1613 For CVEs the ``erratum_id`` also becomes ``cve_<year>_<number>``.
|