Searched refs:go (Results 1 – 16 of 16) sorted by relevance
| /rk3399_ARM-atf/drivers/ti/clk/include/ |
| H A D | ti_clk_div.h | 70 uint8_t go; member
|
| /rk3399_ARM-atf/drivers/ti/clk/ |
| H A D | ti_clk_div.c | 500 reg_val &= (uint32_t) ~BIT(data_reg->go); in ti_clk_div_reg_go_set_div() 506 reg_val |= BIT(data_reg->go); in ti_clk_div_reg_go_set_div() 508 reg_val &= (uint32_t) ~BIT(data_reg->go); in ti_clk_div_reg_go_set_div()
|
| /rk3399_ARM-atf/tools/cot_dt2c/cot_dt2c/ |
| H A D | cot_parser.py | 227 import plotly.graph_objects as go namespace 228 fig = go.Figure() 229 fig.add_trace(go.Scatter(x = Xe, 235 fig.add_trace(go.Scatter(x = Xn,
|
| /rk3399_ARM-atf/plat/ti/k3low/common/pm/ |
| H A D | ti_clocks.c | 709 .go = 16, 905 .go = 16, 913 .go = 16, 921 .go = 16, 929 .go = 16, 937 .go = 16, 945 .go = 16, 953 .go = 16,
|
| /rk3399_ARM-atf/plat/allwinner/common/ |
| H A D | arisc_off.S | 12 # The encoded instructions go into an array defined in
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | faq.rst | 44 How long will it take for my changes to go from ``integration`` to ``master``?
|
| H A D | code-review-guidelines.rst | 73 - Be patient and resilient. It is quite common for patches to go through 92 meet your exact needs, go the extra mile and extend the code with the missing
|
| H A D | contributing.rst | 184 patches go through a series of checks before they get merged on to the master
|
| /rk3399_ARM-atf/docs/threat_model/ |
| H A D | supply_chain_threat_model.rst | 314 | | is still possible for a malicious commit to go unnoticed | 330 | Mitigations | Yes, contributions go through the thorough review, | 368 | | | - Internal dependencies go through the normal code review |
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | xlat-tables-lib-v2-design.rst | 79 The granularity controls the translation table level to go down to when mapping 333 one go, rather than having to edit them every time while the MMU is disabled.
|
| H A D | ffa-manifest-binding.rst | 146 - 0x2: Only when the SP attempts to go back to the waiting state while
|
| H A D | rmm-el3-comms-spec.rst | 855 ``E_RMM_OK``,The Key set go is successful. 856 ``E_RMM_FAULT``,The Key set go is not successful.
|
| /rk3399_ARM-atf/docs/about/ |
| H A D | lts.rst | 204 on TF-A 2.8. This means new features going in 2.8 won’t go in the LTS branch. 211 related patches go into TF-A master branch. Since these patches fall under
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | rse.rst | 441 need to go through BL31. The RMM dispatcher module of the BL31 is responsible
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model.rst | 476 | | code including platform code go through manual |
|
| /rk3399_ARM-atf/docs/ |
| H A D | change-log.md | 12248 machine to go from COPYING, COPIED or AUTHENTICATED states to RESET state.
|