Searched refs:registered (Results 1 – 17 of 17) sorted by relevance
/arm-trusted-firmware-2.8.0/drivers/nxp/ddr/nxp-ddr/ |
A D | dimm.c | 197 pdimm->rc = spd->mod_section.registered.ref_raw_card & 0x9f; in cal_dimm_params() 198 if ((spd->mod_section.registered.reg_map & 0x1) != 0) { in cal_dimm_params() 201 val = spd->mod_section.registered.ca_stren; in cal_dimm_params() 204 val = spd->mod_section.registered.clk_stren; in cal_dimm_params()
|
/arm-trusted-firmware-2.8.0/docs/components/fconf/ |
A D | index.rst | 47 Hence each ``populate()`` function must be registered with a specific 59 Hence the ``populate()`` callback must be registered to the (|FCONF|) framework 106 registered with ``FCONF_REGISTER_POPULATOR()`` as described above.
|
/arm-trusted-firmware-2.8.0/include/drivers/nxp/ddr/ |
A D | dimm.h | 150 } registered; member
|
/arm-trusted-firmware-2.8.0/services/std_svc/sdei/ |
A D | sdei_main.c | 557 bool registered; in sdei_event_get_info() local 571 registered = GET_EV_STATE(se, REGISTERED); in sdei_event_get_info() 591 if (!registered) in sdei_event_get_info() 598 if (!registered) in sdei_event_get_info()
|
/arm-trusted-firmware-2.8.0/docs/components/ |
A D | sdei.rst | 13 asynchronous exceptions and, in response, arranges for the registered handler to 18 client receives the event notification at the registered handler even when it 39 execute the registered handler [10]. The client terminates its execution with 242 dispatch an event [10] (which the client had already registered for [1]). The 263 - The event must have been registered for and enabled.
|
A D | exception-handling.rst | 110 priority of the acknowledged interrupt is used to match its registered handler. 257 - The priority level for which the handler is being registered; 259 - The handler to be registered. The handler must be aligned to 4 bytes. 268 - There are no handlers already registered by a previous call to the API.
|
A D | el3-spmc.rst | 413 Payload Dispatcher for events the latter has statically registered to. 420 hooks are registered.
|
A D | xlat-tables-lib-v2-design.rst | 346 they only get registered in the internal mmap region list. It is only when the 348 in memory based on the list of mmap regions registered so far. This is an
|
A D | secure-partition-manager.rst | 1336 Payload Dispatcher for events the latter has statically registered to. 1342 (svc_off) hooks are registered.
|
/arm-trusted-firmware-2.8.0/docs/design/ |
A D | interrupt-framework-design.rst | 224 registered handler when the interrupt is generated. 366 registered. If the ``type`` is unrecognised or the ``flags`` or the ``handler`` are 459 function is registered with the EL3 runtime firmware using the 476 registered with the EL3 runtime firmware using the 550 call the handler registered by the SPD service for Secure-EL1 interrupts. 663 It returns the reference to the registered handler for this interrupt 666 registered for this type of interrupt. This scenario is reported as an 669 #. Calling the registered handler function for the interrupt type generated. 1004 interrupt causes an IRQ exception and the IRQ handler registered at the
|
A D | auth-framework.rst | 242 These functions are registered in the CM using the macro: 409 An IPL for each type must be registered using the following macro: 626 registered in the framework using the macro ``REGISTER_COT(cot_desc)``, where 922 The library is registered in the framework using the macro 937 ``drivers/auth/mbedtls/mbedtls_crypto.c``. This library is registered in the
|
A D | firmware-design.rst | 610 registered function to initialize BL32 before running BL33. This initialization 900 A runtime service is registered using the ``DECLARE_RT_SVC()`` macro, specifying 1069 registered with the generic PSCI code to be supported. 1072 hooks to be registered with the generic PSCI code to be supported. 1147 and is registered using the ``bl31_register_bl32_init()`` function. 1436 registered for highest level is invoked. 1505 registered itself with, using ``declare_cpu_ops``; 2388 There may be arbitrary number of handlers registered to the same event. The 2463 timestamps by registered services and provides interfaces to retrieve them 2523 Having registered the service, the ``PMF_CAPTURE_TIMESTAMP()`` macro can be [all …]
|
/arm-trusted-firmware-2.8.0/docs/about/ |
A D | features.rst | 69 interrupts to their registered handlers, to facilitate firmware-first
|
/arm-trusted-firmware-2.8.0/docs/getting_started/ |
A D | psci-lib-integration-guide.rst | 433 ``plat_psci_ops_t`` callbacks registered by the platform when 436 :ref:`Porting Guide`. If any these callbacks are not registered, then the 446 populated and registered by using ``psci_register_spd_pm_hook()`` PSCI
|
A D | rt-svc-writers-guide.rst | 91 A runtime service is registered using the ``DECLARE_RT_SVC()`` macro, specifying
|
A D | porting-guide.rst | 494 Defines the maximum number of registered IO devices. Attempting to register 505 Defines the maximum number of registered IO block devices. Attempting to 3333 function iterates through RAS handlers registered by the platform. If any of the
|
/arm-trusted-firmware-2.8.0/docs/ |
A D | change-log.md | 336 …- ensure that no SDEI event registered during dynamic launch ([b1392f4](https://review.trustedfirm… 477 …- add a function to return total number of events registered ([e6381f9](https://review.trustedfirm… 5422 interrupts to their registered handlers which are registered based on their 5876 - Enhanced the CPU operations framework to allow power handlers to be registered
|
Completed in 49 milliseconds