| /trusted-firmware-a/drivers/nxp/ddr/nxp-ddr/ |
| A D | dimm.c | 197 pdimm->rc = spd->mod_section.registered.ref_raw_card & 0x8f; 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()
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/fconf/ |
| A D | index.rst.txt | 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.
|
| /trusted-firmware-a/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.
|
| /trusted-firmware-a/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()
|
| /trusted-firmware-a/include/drivers/nxp/ddr/ |
| A D | dimm.h | 150 } registered; member
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | sdei.rst.txt | 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.txt | 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 | xlat-tables-lib-v2-design.rst.txt | 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.txt | 1085 Payload Dispatcher for events the latter has statically registered to.
1091 (svc_off) hooks are registered.
|
| /trusted-firmware-a/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 | 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 | 1085 Payload Dispatcher for events the latter has statically registered to.
1091 (svc_off) hooks are registered.
|
| /trusted-firmware-a/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 | 607 registered function to initialize BL32 before running BL33. This initialization
897 A runtime service is registered using the ``DECLARE_RT_SVC()`` macro, specifying
1065 registered with the generic PSCI code to be supported.
1068 hooks to be registered with the generic PSCI code to be supported.
1143 and is registered using the ``bl31_register_bl32_init()`` function.
1432 registered for highest level is invoked.
1501 registered itself with, using ``declare_cpu_ops``;
2365 There may be arbitrary number of handlers registered to the same event. The
2440 timestamps by registered services and provides interfaces to retrieve them
2500 Having registered the service, the ``PMF_CAPTURE_TIMESTAMP()`` macro can be
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/ |
| A D | interrupt-framework-design.rst.txt | 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.txt | 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.txt | 607 registered function to initialize BL32 before running BL33. This initialization
897 A runtime service is registered using the ``DECLARE_RT_SVC()`` macro, specifying
1065 registered with the generic PSCI code to be supported.
1068 hooks to be registered with the generic PSCI code to be supported.
1143 and is registered using the ``bl31_register_bl32_init()`` function.
1432 registered for highest level is invoked.
1501 registered itself with, using ``declare_cpu_ops``;
2365 There may be arbitrary number of handlers registered to the same event. The
2440 timestamps by registered services and provides interfaces to retrieve them
2500 Having registered the service, the ``PMF_CAPTURE_TIMESTAMP()`` macro can be
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/about/ |
| A D | features.rst.txt | 69 interrupts to their registered handlers, to facilitate firmware-first
|
| /trusted-firmware-a/docs/about/ |
| A D | features.rst | 69 interrupts to their registered handlers, to facilitate firmware-first
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | psci-lib-integration-guide.rst | 443 ``plat_psci_ops_t`` callbacks registered by the platform when
446 :ref:`Porting Guide`. If any these callbacks are not registered, then the
456 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
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/getting_started/ |
| A D | psci-lib-integration-guide.rst.txt | 443 ``plat_psci_ops_t`` callbacks registered by the platform when
446 :ref:`Porting Guide`. If any these callbacks are not registered, then the
456 populated and registered by using ``psci_register_spd_pm_hook()`` PSCI
|
| A D | rt-svc-writers-guide.rst.txt | 91 A runtime service is registered using the ``DECLARE_RT_SVC()`` macro, specifying
|