| /freebsd/lib/libthr/thread/ |
| H A D | thr_spec.c | 114 if (curthread->specific == 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()
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()
185 pthread->specific = tmp; in _thr_setspecific()
192 pthread->specific[key].data = value; in _thr_setspecific()
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/hwlock/ |
| H A D | hwlock.txt | 4 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 D | exynos-dw-mshc.txt | 1 * 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 D | k3-dw-mshc.txt | 1 * 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 D | samsung-sdhci.txt | 30 Note: This example shows both SoC specific and board specific properties
32 into SoC specific node and board specific node.
|
| H A D | bluefield-dw-mshc.txt | 1 * Mellanox Bluefield SoC specific extensions to the Synopsys Designware
10 specific extensions to the Synopsys Designware Mobile Storage Host Controller.
16 specific extensions.
|
| H A D | arm,pl18x.yaml | 107 description: ST Micro-specific property, bus signal direction pins used for
112 description: ST Micro-specific property, bus signal direction pins used for
117 description: ST Micro-specific property, bus signal direction pins used for
122 description: ST Micro-specific property, bus signal direction pins used for
127 description: ST Micro-specific property, CMD signal direction used for
132 description: ST Micro-specific property, feedback clock FBCLK signal pin
137 description: ST Micro-specific property, signal direction polarity used for
142 description: ST Micro-specific property, data and command phase relation,
147 description: ST Micro-specific property, use CKIN pin from an external
|
| /freebsd/sys/contrib/device-tree/Bindings/sifive/ |
| H A D | sifive-blocks-ip-versioning.txt | 9 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/libexec/rc/rc.d/ |
| H A D | dhclient | 41 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/clock/ti/ |
| H A D | interface.txt | 19 "ti,omap3-hsotgusb-interface-clock" - interface clock with USB specific HW
21 "ti,omap3-dss-interface-clock" - interface clock with DSS specific HW handling
22 "ti,omap3-ssi-interface-clock" - interface clock with SSI specific HW handling
23 "ti,am35xx-interface-clock" - interface clock with AM35xx specific HW handling
24 "ti,omap2430-interface-clock" - interface clock with OMAP2430 specific HW
|
| /freebsd/lib/libc/softfloat/ |
| H A D | softfloat-source.txt | 101 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'
169 The target-specific `processors' header file defines integer types
198 The target-specific `softfloat.h' header file defines the SoftFloat
231 This target-specific C source fragment defines:
304 5. In the target-specific subdirectory, edit the files `milieu.h' and
307 6. In the target-specific subdirectory, execute `make'.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/powerpc/fsl/ |
| H A D | mpic.txt | 39 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/sys/contrib/device-tree/Bindings/memory-controllers/ |
| H A D | mc-peripheral-props.yaml | 7 title: Peripheral-specific properties for a Memory Controller bus.
12 specific like delay in clock or data lines, etc. These properties need
15 those properties are listed here. The controller specific properties
34 # The controller specific properties go here.
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/freescale/ |
| H A D | fsl,layerscape-scfg.txt | 3 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/sys/contrib/device-tree/Bindings/net/nfc/ |
| H A D | nfcmrvl.txt | 9 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/include/llvm/BinaryFormat/ |
| H A D | DynamicTags.def | 5 // Add separate macros for the architecture specific tags and the markers
89 DYNAMIC_TAG_MARKER(LOOS, 0x60000000) // Start of environment specific tags.
90 DYNAMIC_TAG_MARKER(HIOS, 0x6FFFFFFF) // End of environment specific tags.
91 DYNAMIC_TAG_MARKER(LOPROC, 0x70000000) // Start of processor specific tags.
92 DYNAMIC_TAG_MARKER(HIPROC, 0x7FFFFFFF) // End of processor specific tags.
125 // AArch64 specific dynamic table entries
141 // Hexagon specific dynamic table entries
146 // Mips specific dynamic table entry tags.
225 // PPC specific dynamic table entries.
229 // PPC64 specific dynamic table entries.
[all …]
|
| /freebsd/tools/tools/ |
| H A D | README | 11 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
55 sysdoc Build a manual page with available sysctls for a specific
|
| /freebsd/contrib/llvm-project/llvm/lib/Support/Unix/ |
| H A D | README.txt | 9 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/pci/ |
| H A D | snps,dw-pcie-ep.yaml | 17 # and make sure it's assigned with the vendor-specific compatible string.
64 be accessed over some platform-specific means (for instance
78 Platform-specific eDMA registers. Some platforms may have eDMA
89 platform-specific method.
93 generate various application-specific traffic on the PCIe bus
99 Vendor-specific CSR names. Consider using the generic names above
151 Application-specific IRQ raised depending on the vendor-specific
155 Vendor-specific IRQ names. Consider using the generic names above
|
| /freebsd/sys/contrib/device-tree/Bindings/usb/ |
| H A D | omap-usb.txt | 7 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/sys/contrib/device-tree/Bindings/arm/ |
| H A D | ste-u300.txt | 3 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/pinctrl/ |
| H A D | pinctrl-mt8183.txt | 65 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/sys/contrib/device-tree/Bindings/clock/ |
| H A D | lpc1850-ccu.txt | 23 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 D | udma_barrier.h | 112 #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/sys/contrib/device-tree/Bindings/i2c/ |
| H A D | i2c-opal.txt | 4 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
|