Home
last modified time | relevance | path

Searched refs:specific (Results 1 – 25 of 2044) sorted by relevance

12345678910>>...82

/freebsd/lib/libthr/thread/
H A Dthr_spec.c114 if (curthread->specific == NULL) in _thread_cleanupspecific()
124 (curthread->specific[key].data != NULL)) { in _thread_cleanupspecific()
125 if (curthread->specific[key].seqno == in _thread_cleanupspecific()
127 data = curthread->specific[key].data; in _thread_cleanupspecific()
131 curthread->specific[key].data = NULL; in _thread_cleanupspecific()
133 } else if (curthread->specific[key].data != NULL) { in _thread_cleanupspecific()
142 curthread->specific[key].data = NULL; in _thread_cleanupspecific()
158 __thr_free(curthread->specific); in _thread_cleanupspecific()
159 curthread->specific = NULL; in _thread_cleanupspecific()
180 if (pthread->specific == NULL) { in _thr_setspecific()
[all …]
/freebsd/sys/contrib/device-tree/Bindings/hwlock/
H A Dhwlock.txt4 Generic bindings that are common to all the hwlock platform specific driver
7 Please also look through the individual platform specific hwlock binding
8 documentations for identifying any additional properties specific to that
16 specific lock.
21 Consumers that require specific hwlock(s) should specify them using the
34 use the hwlock-names to match and get a specific hwlock.
37 1. Example of a node using a single specific hwlock:
49 2. Example of a node using multiple specific hwlocks:
/freebsd/sys/contrib/device-tree/Bindings/mmc/
H A Dexynos-dw-mshc.txt1 * Samsung Exynos specific extensions to the Synopsys Designware Mobile
7 by synopsys-dw-mshc.txt and the properties used by the Samsung Exynos specific
14 specific extensions.
16 specific extensions.
18 specific extensions.
20 specific extensions.
22 specific extensions.
24 specific extensions having an SMU.
25 - "axis,artpec8-dw-mshc": for controllers with ARTPEC-8 specific
71 The MSHC controller node can be split into two portions, SoC specific and
[all …]
H A Dk3-dw-mshc.txt1 * Hisilicon specific extensions to the Synopsys Designware Mobile
9 by synopsys-dw-mshc.txt and the properties used by the Hisilicon specific
15 - "hisilicon,hi3660-dw-mshc": for controllers with hi3660 specific extensions.
17 with hi3670 specific extensions.
18 - "hisilicon,hi4511-dw-mshc": for controllers with hi4511 specific extensions.
19 - "hisilicon,hi6220-dw-mshc": for controllers with hi6220 specific extensions.
H A Dsamsung-sdhci.txt30 Note: This example shows both SoC specific and board specific properties
32 into SoC specific node and board specific node.
H A Dbluefield-dw-mshc.txt1 * Mellanox Bluefield SoC specific extensions to the Synopsys Designware
10 specific extensions to the Synopsys Designware Mobile Storage Host Controller.
16 specific extensions.
/freebsd/sys/contrib/device-tree/Bindings/sifive/
H A Dsifive-blocks-ip-versioning.txt9 IP block-specific DT compatible strings are contained within the HDL,
26 match on these IP block-specific compatible strings.
29 continue to specify an SoC-specific compatible string value, such as
30 "sifive,fu540-c000-uart". This way, if SoC-specific
31 integration-specific bug fixes or workarounds are needed, the kernel
33 IP block-specific compatible string (such as "sifive,uart0") should
/freebsd/lib/libc/softfloat/
H A Dsoftfloat-source.txt101 is slightly scattered between target-specific and target-independent
118 processors - Target-specific header files that are not specific to
130 are not within these target-specific subdirectories are intended to be
133 The naming convention used for the target-specific directories is
148 Alongside the supplied target-specific directories is a `templates'
149 directory containing a set of ``generic'' target-specific source files. A
162 the `*' symbol is used in place of the name of a specific target, such as
169 The target-specific `processors' header file defines integer types
198 The target-specific `softfloat.h' header file defines the SoftFloat
205 target-specific declarations in `softfloat.h' must match what `softfloat.c'
[all …]
/freebsd/sys/contrib/device-tree/Bindings/clock/ti/
H A Dinterface.txt17 "ti,omap3-hsotgusb-interface-clock" - interface clock with USB specific HW
19 "ti,omap3-dss-interface-clock" - interface clock with DSS specific HW handling
20 "ti,omap3-ssi-interface-clock" - interface clock with SSI specific HW handling
21 "ti,am35xx-interface-clock" - interface clock with AM35xx specific HW handling
22 "ti,omap2430-interface-clock" - interface clock with OMAP2430 specific HW
/freebsd/sys/contrib/device-tree/Bindings/powerpc/fsl/
H A Dmpic.txt39 specifiers do not contain the interrupt-type or type-specific
110 type-specific cell is undefined. The
123 the error interrupt. The type-specific
124 cell identifies the specific error
130 the MPIC IPI number. The type-specific
136 the MPIC timer number. The type-specific
139 <4th-cell> type-specific information
141 The type-specific cell is encoded as follows:
144 the type-specific cell contains the
223 * SoC interrupt number is 16 and the specific error
/freebsd/libexec/rc/rc.d/
H A Ddhclient41 specific=$(get_if_var $ifn dhclient_flags_IF)
42 if [ -z "$flags" -a -n "$specific" ]; then
43 rc_flags=$specific
/freebsd/sys/contrib/device-tree/Bindings/arm/freescale/
H A Dfsl,layerscape-scfg.txt3 SCFG is the supplemental configuration unit, that provides SoC specific
8 - compatible: Should contain a chip-specific compatible string,
9 Chip-specific strings are of the form "fsl,<chip>-scfg",
/freebsd/tools/tools/
H A DREADME11 ath Tools specific to the Atheros 802.11 support
18 drm Tools specific to the DRM/KMS device drivers.
36 iwi Tools specific to the Intel PRO/Wireless 2200BG/2225BG/2915ABG
46 mwl Tools specific to the Marvell 88W8363 support
50 npe Tools specific to the Intel IXP4XXX NPE device
56 sysdoc Build a manual page with available sysctls for a specific
/freebsd/sys/contrib/device-tree/Bindings/net/nfc/
H A Dnfcmrvl.txt9 Optional SoC specific properties:
15 Optional UART-based chip specific properties:
17 - break-control: Specifies that the chip needs specific break management.
19 Optional I2C-based chip specific properties:
/freebsd/contrib/llvm-project/llvm/lib/Support/Unix/
H A DREADME.txt9 Posix - code that is specific to Posix variants of UNIX
10 SUS - code that is specific to the Single Unix Specification
11 SysV - code that is specific to System V variants of UNIX
/freebsd/sys/contrib/device-tree/Bindings/usb/
H A Domap-usb.txt7 multipoint. This is a MUSB configuration-specific setting.
9 MUSB configuration-specific setting. Should be set to "16"
11 - interface-type : This is a board specific setting to describe the type of
27 SOC specific device node entry
39 Board specific device node entry
/freebsd/contrib/llvm-project/llvm/include/llvm/BinaryFormat/
H A DDynamicTags.def5 // Add separate macros for the architecture specific tags and the markers
93 DYNAMIC_TAG_MARKER(LOOS, 0x60000000) // Start of environment specific tags.
94 DYNAMIC_TAG_MARKER(HIOS, 0x6FFFFFFF) // End of environment specific tags.
95 DYNAMIC_TAG_MARKER(LOPROC, 0x70000000) // Start of processor specific tags.
96 DYNAMIC_TAG_MARKER(HIPROC, 0x7FFFFFFF) // End of processor specific tags.
129 // AArch64 specific dynamic table entries
139 // AArch64 specific dynamic table entries for RELR auth relocations as described here:
145 // Hexagon specific dynamic table entries
150 // Mips specific dynamic table entry tags.
229 // PPC specific dynamic table entries.
[all …]
/freebsd/sys/contrib/device-tree/Bindings/pinctrl/
H A Dpinctrl-mt8183.txt65 For I2C pins, there are existing generic driving setup and the specific
67 adjustment in generic driving setup. But in specific driving setup,
68 they can support 0.125/0.25/0.5/1mA adjustment. If we enable specific
70 disabled. For some special features, we need the I2C pins specific
71 driving setup. The specific driving setup is controlled by E1E0EN.
74 We can add "mediatek,drive-strength-adv = <XXX>;" to describe the specific
76 It is used to enable or disable the specific driving setup.
/freebsd/contrib/wpa/wpa_supplicant/
H A DREADME-NAN-USD29 …ist=<comma separate list of MHz>] [srv_proto_type=<type>] [ssi=<service specific information (hexd…
54 NAN_UPDATE_PUBLISH publish_id=<id from NAN_PUBLISH> [ssi=<service specific information (hexdump)>]
59 …-to-live-in-sec>] [freq=<in MHz>] [srv_proto_type=<type>] [ssi=<service specific information (hexd…
78 … req_instance_id=<peer's id> address=<peer's MAC address> [ssi=<service specific information (hexd…
84 …MAC address> fsd=<0/1> fsd_gas=<0/1> srv_proto_type=<type> ssi=<service specific information (hexd…
89 …r MAC address> subscribe_id=<peer id> srv_proto_type=<ype> ssi=<service specific information (hexd…
103 NAN-RECEIVE id=<own id> peer_instance_id=<peer id> address=<peer MAC adress> ssi=<service specific …
/freebsd/sys/contrib/device-tree/Bindings/arm/
H A Dste-u300.txt3 For various board the "board" node may contain specific properties
4 that pertain to this particular board, such as board-specific GPIOs
21 This contains the board-specific information.
/freebsd/sys/contrib/device-tree/Bindings/clock/
H A Dlpc1850-ccu.txt23 from the CGU to the specific CCU. See mapping of base clocks
27 from the CGU to the specific CCU. Valid CCU clock names:
36 specific LPC part. Check the user manual for your specific part.
/freebsd/contrib/ofed/include/
H A Dudma_barrier.h112 #error No architecture specific memory barrier defines found!
150 #error No architecture specific memory barrier defines found!
220 #error No architecture specific memory barrier defines found!
/freebsd/contrib/llvm-project/llvm/tools/llvm-readobj/
H A DOpts.td20 def arch_specific : FF<"arch-specific", "Display architecture-specific information">;
51 // ELF specific options.
52 def grp_elf : OptionGroup<"kind">, HelpText<"OPTIONS (ELF specific)">;
67 // Mach-O specific options.
68 def grp_mach_o : OptionGroup<"kind">, HelpText<"OPTIONS (Mach-O specific)">;
76 // PE/COFF specific options.
77 def grp_coff : OptionGroup<"kind">, HelpText<"OPTIONS (PE/COFF specific)">;
91 // XCOFF specific options.
92 def grp_xcoff : OptionGroup<"kind">, HelpText<"OPTIONS (XCOFF specific)">;
124 def : F<"A", "Alias for --arch-specific">, Alias<arch_specific>;
/freebsd/sys/contrib/device-tree/Bindings/i2c/
H A Di2c-opal.txt4 Most of the device node and properties layout is specific to the firmware and
12 - ibm,opal-id: Refers to a specific bus and used to identify it when calling
22 and depend on the specific hardware implementation. The example below depicts
/freebsd/crypto/openssl/providers/
H A Dencoders.inc14 #define ENCODER_STRUCTURE_type_specific_keypair "type-specific"
15 #define ENCODER_STRUCTURE_type_specific_params "type-specific"
16 #define ENCODER_STRUCTURE_type_specific "type-specific"
17 #define ENCODER_STRUCTURE_type_specific_no_pub "type-specific"
70 * Entries for key type specific output formats. The structure name on these
78 * OSSL_ENCODER_CTX_new_for_pkey(pkey, selection, "DER", "type-specific",
86 * OSSL_ENCODER_CTX_new_for_pkey(pkey, selection, "PEM", "type-specific",
223 * Entries for key type specific output formats. These are exactly the
224 * same as the type specific above, except that they use the key type
225 * name as structure name instead of "type-specific", in the call on

12345678910>>...82