Home
last modified time | relevance | path

Searched refs:kind (Results 1 – 10 of 10) sorted by relevance

/rk3399_ARM-atf/make_helpers/
H A Dutilities.mk278 with.bind.kind = $(word 1,$(subst :, ,$(call with.bind.norm,$(1))))
285 $(with.ns).bind.kinds := $(foreach b,$(1),$(call with.bind.kind,$(b)))
306 $(foreach bind.kind,$(sort $($(with.ns).bind.kinds)),$\
307 $(eval $(with.ns).bind.kind[$(bind.kind)] := ))
311 $(foreach bind.kind,$(word $(bind.i),$($(with.ns).bind.kinds)),$\
312 $(eval $(with.ns).bind.kind[$(bind.kind)] += $(bind.i))))
315 $(foreach bind.kind,$(sort $($(with.ns).bind.kinds)),$\
316 $(foreach bind.kind.ns,$(with.ns).bind.kind[$(bind.kind)],$\
317 $(eval $(value with.core.$(bind.kind)))))
322 $(foreach bind.kind,$(word $(bind.i),$($(with.ns).bind.kinds)),$\
[all …]
/rk3399_ARM-atf/include/lib/libc/sys/
H A Dcdefs.h819 #define __datatype_type_tag(kind, type) \ argument
820 __attribute__((__type_tag_for_datatype__(kind, type)))
823 #define __datatype_type_tag(kind, type) argument
/rk3399_ARM-atf/fdts/
H A Darm_fpga.dts6 * Number and kind of CPU cores differs from image to image, so the
/rk3399_ARM-atf/docs/plat/
H A Drpi5.rst12 not seem to feature a secure memory controller of any kind, so portions of
H A Drpi4.rst14 not seem to feature a secure memory controller of any kind, so portions of
H A Drcar-gen3.rst78 mode (some kind of self-refresh mode). This means that BL2 is always
/rk3399_ARM-atf/docs/process/
H A Dcontributing.rst279 group which holds all build tests for all platforms. So be kind enough to
/rk3399_ARM-atf/docs/components/
H A Dcontext-management-library.rst129 are no clear guidelines what kind of mismatch is allowed but following
H A Dexception-handling.rst561 #. The platform provides handlers for the specific kind of exception.
/rk3399_ARM-atf/docs/threat_model/firmware_threat_model/
H A Dthreat_model.rst1075 | | use this kind of attack to leak sensitive |