Home
last modified time | relevance | path

Searched refs:accessors (Results 1 – 24 of 24) sorted by relevance

/Linux-v5.10/tools/build/feature/
Dtest-libunwind-aarch64.c13 static unw_accessors_t accessors; variable
19 addr_space = unw_create_addr_space(&accessors, 0); in main()
Dtest-libunwind-arm.c14 static unw_accessors_t accessors; variable
20 addr_space = unw_create_addr_space(&accessors, 0); in main()
Dtest-libunwind-x86.c14 static unw_accessors_t accessors; variable
20 addr_space = unw_create_addr_space(&accessors, 0); in main()
Dtest-libunwind-x86_64.c14 static unw_accessors_t accessors; variable
20 addr_space = unw_create_addr_space(&accessors, 0); in main()
Dtest-libunwind.c14 static unw_accessors_t accessors; variable
20 addr_space = unw_create_addr_space(&accessors, 0); in main()
/Linux-v5.10/arch/arm/common/
DMakefile10 obj-$(CONFIG_KRAIT_L2_ACCESSORS) += krait-l2-accessors.o
/Linux-v5.10/drivers/soc/qcom/
DMakefile28 obj-$(CONFIG_QCOM_KRYO_L2_ACCESSORS) += kryo-l2-accessors.o
/Linux-v5.10/Documentation/core-api/
Dtimekeeping.rst1 ktime accessors
174 some drivers may actually want the higher resolution accessors
Dassoc_array.rst249 The caller should lock exclusively against other modifiers and accessors
/Linux-v5.10/tools/perf/util/
Dunwind-libunwind-local.c608 static unw_accessors_t accessors = { variable
621 maps->addr_space = unw_create_addr_space(&accessors, 0); in _unwind__prepare_access()
/Linux-v5.10/Documentation/driver-api/gpio/
Dconsumer.rst241 To access such GPIOs, a different set of accessors is defined::
247 IRQ handler, and those accessors must be used instead of spinlock-safe
248 accessors without the cansleep() name suffix.
250 Other than the fact that these accessors might sleep, and will work on GPIOs
Dlegacy.rst210 To access such GPIOs, a different set of accessors is defined::
220 a threaded IRQ handler, and those accessors must be used instead of
221 spinlock-safe accessors without the cansleep() name suffix.
223 Other than the fact that these accessors might sleep, and will work
/Linux-v5.10/Documentation/process/
Dvolatile-considered-harmful.rst58 architectures. Those accessors are written to prevent unwanted
/Linux-v5.10/drivers/net/mdio/
DKconfig28 OpenFirmware MDIO bus (Ethernet PHY) accessors
/Linux-v5.10/drivers/gpio/
DTODO48 numberspace accessors from <linux/gpio.h> and eventually delete
/Linux-v5.10/drivers/mtd/maps/
DKconfig87 platforms, some detection and setting up ROMs-specific accessors.
/Linux-v5.10/lib/
DKconfig98 I/O accessors.
/Linux-v5.10/Documentation/
Dmemory-barriers.txt1935 relaxed I/O accessors and the Documentation/core-api/dma-api.rst file for
2533 The readX() and writeX() MMIO accessors take a pointer to the
2593 The readsX() and writesX() MMIO accessors are designed for accessing
2600 The inX() and outX() accessors are intended to access legacy port-mapped
2618 As above, the insX() and outsX() accessors provide the same ordering
2627 With the exception of the string accessors (insX(), outsX(), readsX() and
/Linux-v5.10/LICENSES/preferred/
DLGPL-2.0257 layouts and accessors, and small macros and small inline functions (ten
DLGPL-2.1267 layouts and accessors, and small macros and small inline functions (ten
/Linux-v5.10/drivers/mmc/host/
DKconfig76 need to overwrite SDHCI IO memory accessors.
/Linux-v5.10/Documentation/kernel-hacking/
Dlocking.rst311 function call (except accessors like readb()).
/Linux-v5.10/Documentation/security/keys/
Dcore.rst1375 usage. This is called key->payload.rcu_data0. The following accessors
/Linux-v5.10/Documentation/admin-guide/
Dkernel-parameters.txt1083 the driver will use only 32-bit accessors to read/write