| /f-stack/freebsd/contrib/device-tree/Bindings/arm/marvell/ |
| H A D | mvebu-system-controller.txt | 8 - "marvell,orion-system-controller" 9 - "marvell,armada-370-xp-system-controller" 10 - "marvell,armada-375-system-controller" 11 - reg: Should contain system controller registers location and length. 15 system-controller@d0018200 { 16 compatible = "marvell,armada-370-xp-system-controller";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/sram/ |
| H A D | allwinner,sun4i-a10-system-control.yaml | 29 - const: allwinner,sun4i-a10-system-control 30 - const: allwinner,sun5i-a13-system-control 32 - const: allwinner,sun7i-a20-system-control 33 - const: allwinner,sun4i-a10-system-control 34 - const: allwinner,sun8i-a23-system-control 35 - const: allwinner,sun8i-h3-system-control 38 - const: allwinner,sun50i-a64-system-control 39 - const: allwinner,sun50i-h5-system-control 41 - const: allwinner,sun50i-h6-system-control 45 - const: allwinner,sun4i-a10-system-control [all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/power/ |
| H A D | power-controller.txt | 1 * Generic system power control capability 4 sometimes able to control the system power. The device driver associated with these 6 it can be used to switch off the system. The corresponding device must have the 7 standard property "system-power-controller" in its device node. This property 8 marks the device as able to control the system power. In order to test if this 16 system-power-controller;
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/ |
| H A D | berlin,pinctrl.txt | 3 Pin control registers are part of both chip controller and system 5 either the chip controller or system controller node. The pins 19 "marvell,berlin2-system-pinctrl", 21 "marvell,berlin2cd-system-pinctrl", 23 "marvell,berlin2q-system-pinctrl", 26 "marvell,berlin4ct-system-pinctrl", 36 compatible = "marvell,berlin2q-system-pinctrl";
|
| H A D | sprd,pinctrl.txt | 8 pad driving level, system control select and so on ("domain pad 11 slect 3.0v, then the pin can output 3.0v. "system control" is used 12 to choose one function (like: UART0) for which system, since we 32 Now we have 4 systems for sleep mode on SC9860 SoC: AP system, 33 PUBCP system, TGLDSP system and AGDSP system. And the pin sleep 44 by hardware when the system specified by sleep mode goes into deep 47 means when PUBCP system goes into deep sleep mode, this pin will be set 51 PUBCP system) do not run linux kernel OS (only AP system run linux 53 when the PUBCP system goes into deep sleep mode. Thus we introduce
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/hisilicon/ |
| H A D | hisilicon.txt | 59 Hisilicon system controller 72 - reboot-offset : offset in sysctrl for system reboot 77 sysctrl: system-controller@fc802000 { 109 Hisilicon Hi6220 system controller 208 Hisilicon HiP01 system controller 222 sysctrl: system-controller@10000000 { 239 /* for HiP05 PCIe-SAS sub system */ 245 Hisilicon HiP05/HiP06 PERI sub system controller 256 /* for HiP05 sub peri system */ 262 Hisilicon HiP05/HiP06 DSA sub system controller [all …]
|
| /f-stack/freebsd/arm/broadcom/bcm2835/ |
| H A D | bcm2835_machdep.c | 79 phandle_t system; in bcm2835_late_init() local 83 system = OF_finddevice("/system"); in bcm2835_late_init() 84 if (system != -1) { in bcm2835_late_init() 85 len = OF_getencprop(system, "linux,serial", cells, in bcm2835_late_init() 90 len = OF_getencprop(system, "linux,revision", cells, in bcm2835_late_init()
|
| /f-stack/freebsd/contrib/openzfs/config/ |
| H A D | user-systemd.m4 | 10 [install systemd unit files in dir [[/usr/lib/systemd/system]]]), 11 systemdunitdir=$withval,systemdunitdir=/usr/lib/systemd/system) 15 [install systemd preset files in dir [[/usr/lib/systemd/system-preset]]]), 16 systemdpresetdir=$withval,systemdpresetdir=/usr/lib/systemd/system-preset) 25 [install systemd generators in dir [[/usr/lib/systemd/system-generators]]]), 26 systemdgeneratordir=$withval,systemdgeneratordir=/usr/lib/systemd/system-generators)
|
| H A D | always-system.m4 | 2 dnl # Set the target system 5 AC_MSG_CHECKING([for system type ($host_os)]) 9 [True if ZFS is to be compiled for a Linux system]) 14 [True if ZFS is to be compiled for a FreeBSD system])
|
| /f-stack/freebsd/contrib/device-tree/Bindings/soc/rockchip/ |
| H A D | grf.txt | 4 is composed of many registers for system control. 7 - GRF, used for general non-secure system, 8 - SGRF, used for general secure system, 9 - PMUGRF, used for always on system 14 - GRF, used for general non-secure system, 15 - SGRF, used for general secure system, 16 - DETECTGRF, used for audio codec system,
|
| /f-stack/freebsd/contrib/device-tree/src/arm/ |
| H A D | imx27-phytec-phycore-rdk.dts | 223 label = "system:red1:user"; 228 label = "system:green1:user"; 233 label = "system:blue1:user"; 238 label = "system:red2:user"; 243 label = "system:green2:user"; 248 label = "system:blue2:user"; 253 label = "system:red3:nand"; 259 label = "system:green3:live"; 265 label = "system:blue3:cpu";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/socionext/ |
| H A D | socionext,uniphier-system-cache.yaml | 4 $id: http://devicetree.org/schemas/arm/socionext/socionext,uniphier-system-cache.yaml# 11 controller system. All of them have a level 2 cache controller, and some 19 const: socionext,uniphier-system-cache 69 compatible = "socionext,uniphier-system-cache"; 82 compatible = "socionext,uniphier-system-cache"; 94 compatible = "socionext,uniphier-system-cache";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mfd/ |
| H A D | twl4030-power.txt | 5 binding only supports the complete shutdown of the system after poweroff. 27 - ti,system-power-controller: This indicates that TWL4030 is the 28 power supply master of the system. With this flag, the chip will 30 system poweroffs. 32 - ti,use_poweroff: Deprecated name for ti,system-power-controller
|
| H A D | syscon.yaml | 37 - allwinner,sun8i-a83t-system-controller 38 - allwinner,sun8i-h3-system-controller 39 - allwinner,sun8i-v3s-system-controller 40 - allwinner,sun50i-a64-system-controller 75 compatible = "allwinner,sun8i-h3-system-controller", "syscon";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/interrupt-controller/ |
| H A D | ti,sci-inta.yaml | 17 which handles the termination of system events to that they can 18 be coherently processed by the host(s) in the system. A maximum 38 done by a system controller (like the Device Memory and Security Controller 39 on AM654 SoC). Driver should request the system controller to get the range 42 system controller to map specific global event to vint, bit pair. 44 Communication between the host processor running an OS and the system
|
| H A D | ti,sci-inta.txt | 5 which handles the termination of system events to that they can 6 be coherently processed by the host(s) in the system. A maximum 27 by a system controller (like the Device Memory and Security Controller on K3 28 AM654 SoC). Driver should request the system controller to get the range 31 system controller to map specific global event to vint, bit pair. 33 Communication between the host processor running an OS and the system
|
| /f-stack/freebsd/contrib/device-tree/Bindings/watchdog/ |
| H A D | armada-37xx-wdt.txt | 8 - marvell,system-controller : reference to syscon node for the CPU Miscellaneous 13 cpu_misc: system-controller@d000 { 21 marvell,system-controller = <&cpu_misc>;
|
| H A D | aspeed-wdt.txt | 14 - aspeed,reset-type = "cpu|soc|system|none" 23 If 'aspeed,reset-type=' is not specfied the default is to enable system 32 - system: Reset system on watchdog timeout 55 aspeed,reset-type = "system";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/omap/ |
| H A D | mpu.txt | 25 - For an OMAP5 SMP system: 32 - For an OMAP4 SMP system: 40 - For an OMAP3 monocore system: 47 - For an AM335x system:
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/freescale/ |
| H A D | fsl,imx7ulp-sim.txt | 3 The system integration module (SIM) provides system control and chip configuration 6 objective to maintain its value between system resets.
|
| /f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/tmpfile/ |
| H A D | tmpfile_002_pos.c | 61 if ((ret = system("sudo zpool freeze $TESTPOOL"))) { in main() 72 if ((ret = system("sudo zpool export $TESTPOOL"))) { in main() 81 if ((ret = system("sudo zpool import $TESTPOOL"))) { in main()
|
| /f-stack/app/nginx-1.16.1/auto/ |
| H A D | endianness | 6 echo $ngx_n "checking for system byte ordering ...$ngx_c" 11 checking for system byte ordering 48 echo "$0: error: cannot detect system byte ordering"
|
| /f-stack/freebsd/contrib/device-tree/Bindings/cpu/ |
| H A D | cpu-topology.txt | 9 In a SMP system, the hierarchy of CPUs is defined through three entities that 10 are used to describe the layout of physical CPUs in the system: 23 in the system and map to the hierarchy level "core" above. 63 - one or more socket nodes in a multi-socket system 103 per physical socket in the system. A system can 109 This node is optional for a single socket system. 121 per cluster. A system can contain several layers of 138 the cluster. If the system does not support SMT, core 164 in the core if the system supports SMT. Thread nodes are 405 Example 2 (ARM 32-bit, dual-cluster, 8-cpu system, no SMT): [all …]
|
| /f-stack/freebsd/contrib/openzfs/etc/systemd/ |
| H A D | Makefile.am | 1 SUBDIRS = system system-generators subdir
|
| /f-stack/freebsd/contrib/device-tree/Bindings/clock/ |
| H A D | arm,syscon-icst.yaml | 16 oscillators to their system controllers. 18 The various ARM system controllers contain logic to serialize and initialize 20 into the system controller. Furthermore, to even be able to alter one of 21 these frequencies, the system controller must first be unlocked by 22 writing a special token to another offset in the system controller. 52 The ICST oscillator must be provided inside a system controller node.
|