Home
last modified time | relevance | path

Searched full:states (Results 1 – 25 of 2090) sorted by relevance

12345678910>>...84

/freebsd/usr.bin/calendar/calendars/
H A Dcalendar.freebsd11 01/01 Zach Leslie <zleslie@FreeBSD.org> born in Grand Junction, Colorado, United States, 1985
28 01/15 Anne Dickison <anne@FreeBSD.org> born in Madison, Indiana, United States, 1976
34 01/19 Marshall Kirk McKusick <mckusick@FreeBSD.org> born in Wilmington, Delaware, United States, 19…
46 01/26 Andrew Gallatin <gallatin@FreeBSD.org> born in Buffalo, New York, United States, 1970
47 01/27 Nick Sayer <nsayer@FreeBSD.org> born in San Diego, California, United States, 1968
48 01/27 Jacques Anthony Vidrine <nectar@FreeBSD.org> born in Baton Rouge, Louisiana, United States, 1…
50 01/27 Enji Cooper <ngie@FreeBSD.org> born in Seattle, Washington, United States, 1984
54 02/01 Paul Saab <ps@FreeBSD.org> born in Champaign-Urbana, Illinois, United States, 1978
57 02/01 Steven Kreuzer <skreuzer@FreeBSD.org> born in Oceanside, New York, United States, 1982
58 02/01 Juli Mallett <jmallett@FreeBSD.org> born in Washington, Pennsylvania, United States, 1985
[all …]
/freebsd/sys/contrib/device-tree/Bindings/arm/
H A Didle-states.yaml4 $id: http://devicetree.org/schemas/arm/idle-states.yaml#
7 title: ARM idle states binding description
18 where cores can be put in different low-power states (ranging from simple wfi
19 to power gating) according to OS PM policies. The CPU states representing the
20 range of dynamic idle states that a processor can enter at run-time, can be
22 enter/exit specific idle states on a given processor.
25 power states an ARM CPU can be put into are identified by the following list:
33 The power states described in the SBSA document define the basic CPU states on
35 PM implementation to put the processor in different idle states (which include
36 states listed above; "off" state is not an idle state since it does not have
[all …]
H A Dpsci.yaml98 [1] Kernel documentation - ARM idle states bindings
99 Documentation/devicetree/bindings/cpu/idle-states.yaml
111 own specific power states and can be better represented hierarchically.
113 For these cases, the definitions of the idle states for the CPUs and the
114 CPU topology, must conform to the binding in [3]. The idle states
188 // Case 4: CPUs and CPU idle states described using the hierarchical model.
212 idle-states {
223 domain-idle-states {
249 domain-idle-states = <&CPU_PWRDN>;
255 domain-idle-states
[all...]
/freebsd/sys/contrib/device-tree/Bindings/cpu/
H A Didle-states.yaml4 $id: http://devicetree.org/schemas/cpu/idle-states.yaml#
7 title: Idle states
19 dynamically, where cores can be put in different low-power states (ranging
20 from simple wfi to power gating) according to OS PM policies. The CPU states
21 representing the range of dynamic idle states that a processor can enter at
23 parameters required to enter/exit specific idle states on a given processor.
26 2 - ARM idle states
30 power states an ARM CPU can be put into are identified by the following list:
38 The power states described in the SBSA document define the basic CPU states on
40 PM implementation to put the processor in different idle states (which include
[all …]
/freebsd/tests/sys/netpfil/pf/
H A Dsctp.py295 states = ToolsHelper.get_output("/sbin/pfctl -ss")
296 assert re.search(r"all sctp 192.0.2.1:.*192.0.2.3:1234", states)
297 assert re.search(r"all sctp 192.0.2.1:.*192.0.2.2:1234", states)
342 # Ensure we have the states we'd expect
343 states = ToolsHelper.get_output("/sbin/pfctl -ss")
344 assert re.search(r"all sctp 192.0.2.1:.*192.0.2.3:1234", states)
345 assert re.search(r"all sctp 192.0.2.10:.*192.0.2.3:1234", states)
362 states = ToolsHelper.get_output("/sbin/pfctl -ss")
363 assert re.search(r"all sctp 192.0.2.1:.*192.0.2.3:1234.*SHUTDOWN", states)
369 # Assign two addresses to each end, and check for the expected states
[all...]
H A Dsrc_track.sh55 atf_check -s exit:0 -o match:'192.0.2.2 -> 0.0.0.0 \( states 1,.*' \
62 atf_check -s exit:0 -o not-match:'192.0.2.2 -> 0.0.0.0 \( states 1,.*' \
106 atf_check -s exit:0 -o match:'192.0.2.2 -> 0.0.0.0 \( states 1,.*' \
108 atf_check -s exit:0 -o match:'192.0.2.3 -> 0.0.0.0 \( states 1,.*' \
118 atf_check -s exit:0 -o match:'192.0.2.3 -> 0.0.0.0 \( states 1,.*' \
122 atf_check -s exit:0 -o not-match:'192.0.2.2 -> 0.0.0.0 \( states 1,.*' \
167 states=$(mktemp) || exit 1
168 jexec router pfctl -qss | normalize_pfctl_s | grep 'tcp 2001:db8:43::2\[9\] <-' > $states
170 …grep -qE '2001:db8:44::1\[4201\] ESTABLISHED:ESTABLISHED' $states || atf_fail "State for port 4201…
171 …grep -qE '2001:db8:44::1\[4202\] ESTABLISHED:ESTABLISHED' $states || atf_fail "State for port 4202…
[all …]
H A Dkillstate.sh48 atf_set descr 'Test killing states by IPv4 address'
111 atf_set descr 'Test killing states by IPv6 address'
178 atf_set descr 'Test killing states by label'
242 atf_set descr 'Test killing states with multiple labels by label'
322 atf_set descr 'Test killing states by route-to/reply-to address'
364 # Killing states with the relevant gateway does terminate our state
380 atf_set descr 'Test killing matching states'
425 # Expect two states
426 states=$(jexec alcatraz pfctl -s s | grep 192.0.2.1 | wc -l)
427 if [ $states -ne 2 ] ;
[all …]
H A Dsyncookie.sh347 # Now syn flood to create many states
353 states=$(jexec alcatraz pfctl -ss | grep tcp)
354 if [ -n "$states" ];
356 echo "$states"
393 # Now syn flood to create many states
400 states=$(jexec alcatraz pfctl -ss | grep tcp)
401 if [ -n "$states" ];
403 echo "$states"
433 "set limit states 100" \
448 # Now syn flood to create many states
[all …]
/freebsd/sys/contrib/device-tree/Bindings/powerpc/opal/
H A Dpower-mgt.txt5 idle states. The description of these idle states is exposed via the
14 - flags: indicating some aspects of this idle states such as the
16 idle states and so on. The flag bits are as follows:
27 The following properties provide details about the idle states. These
32 If idle-states are defined, then the properties
38 Array of strings containing the names of the idle states.
42 flags associated with the aforementioned idle-states. The
62 exit-latencies (in ns) for the idle states in
67 target-residency (in ns) for the idle states in
75 PSSCR for each of the idle states in ibm,cpu-idle-state-names.
[all …]
/freebsd/contrib/llvm-project/llvm/utils/TableGen/
H A DDFAEmitter.h9 // states that represent a nondeterministic finite state automaton (NFA) and
37 /// a function of the cardinality of the set of states.
63 /// The state type of deterministic states. These are only used internally to
68 /// NFA states.
71 /// A DFA transition consists of a set of NFA states transitioning to a
72 /// new set of NFA states. The DfaTransitionInfo tracks, for every
73 /// transitioned-from NFA state, a set of valid transitioned-to states.
84 /// transition to multiple target states.
90 /// The set of deterministic states. DfaStates.getId(DfaState) returns an ID,
100 /// Visit all NFA states and construct the DFA.
[all …]
/freebsd/sys/contrib/device-tree/Bindings/mux/
H A Dmux-consumer.yaml29 be set to, the property "mux-states" must be used. An optional property
31 each of the multiplixer states listed in the "mux-states" property.
33 Properties "mux-controls" and "mux-states" can be used depending on how
35 needs to set multiple states in a mux controller, then property
37 controller to a given state then property "mux-states" can be used.
49 mux-states:
62 controller to an index into the list given by the "mux-states"
/freebsd/sys/contrib/device-tree/Bindings/power/
H A Dpower-domain.yaml31 domain-idle-states:
36 Phandles of idle states that defines the available states for the
40 Note that, the domain-idle-state property reflects the idle states of this
41 PM domain and not the idle states of the devices or sub-domains in the PM
42 domain. Devices and sub-domains have their own idle states independent of
43 the parent domain's idle states. In the absence of this property, the
110 domain-idle-states = <&DOMAIN_RET>, <&DOMAIN_PWR_DN>;
118 domain-idle-states = <&DOMAIN_PWR_DN>;
121 domain-idle-states {
[all...]
/freebsd/sys/contrib/device-tree/Bindings/arm/msm/
H A Dqcom,idle-state.txt1 QCOM Idle States for cpuidle driver
3 ARM provides idle-state node to define the cpuidle states, as defined in [1].
5 states. Idle states have different enter/exit latency and residency values.
6 The idle states supported by the QCOM SoC are defined as -
18 hierarchy to enter standby states, when all cpus are idle. An interrupt brings
59 the idle-states device node.
75 idle-states {
84 [1]. Documentation/devicetree/bindings/cpu/idle-states.yaml
/freebsd/sys/dev/gpio/
H A Dgpioregulator.c58 struct gpioregulator_state *states; member
134 if (sc->def->states[n].val >= min_uvolt && in gpioregulator_regnode_set_voltage()
135 sc->def->states[n].val <= max_uvolt) { in gpioregulator_regnode_set_voltage()
136 state = &sc->def->states[n]; in gpioregulator_regnode_set_voltage()
174 if (sc->def->states[n].mask == mask) { in gpioregulator_regnode_get_voltage()
175 *uvolt = sc->def->states[n].val; in gpioregulator_regnode_get_voltage()
212 /* "states" property (required) */ in gpioregulator_parse_fdt()
213 len = OF_getencprop_alloc_multi(node, "states", sizeof(*pstates), in gpioregulator_parse_fdt()
216 device_printf(sc->dev, "invalid 'states' property\n"); in gpioregulator_parse_fdt()
221 sc->init_def.states = malloc(sc->init_def.nstates * in gpioregulator_parse_fdt()
[all …]
/freebsd/contrib/unbound/services/
H A Dmesh.h2 * services/mesh.h - deal with mesh of query states and handle events for that.
40 * query states. This mesh is supposed to be thread-specific.
41 * It consists of query states (per qname, qtype, qclass) and connections
42 * between query states and the super and subquery states, and replies to
80 * Mesh of query states
85 /** environment for new states */
100 * an empty set of super-states, thus are 'toplevel' or detached
103 /** number of reply states in the forever list */
106 /** max total number of reply states to have */
108 /** max forever number of reply states to have */
[all …]
/freebsd/sys/contrib/device-tree/Bindings/regulator/
H A Drohm,bd71815-regulator.yaml56 PMIC "RUN" state voltage in uV when PMIC HW states are used. See
76 PMIC "SUSPEND" state voltage in uV when PMIC HW states are used. See
85 PMIC "LPSR" state voltage in uV when PMIC HW states are used. See
92 # Bucks 1 and 2 support giving separate voltages for operational states
93 # (RUN /CLEAN according to data-sheet) and non operational states
100 # Given RUN voltage is used at all states if regulator is enabled at
102 # Values given for other states are regarded as enable/disable at
106 # for each of the HW states (RUN/SNVS/SUSPEND/LPSR). HW defaults can
H A Dgpio-regulator.yaml35 voltage/current listed in "states".
39 gpios-states:
56 states:
59 no states in the "states" array, use a fixed regulator instead.
97 - states
114 states = <1800000 0x3>,
/freebsd/sys/contrib/device-tree/Bindings/pinctrl/
H A Dpinctrl-bindings.txt17 states. The number and names of those states is defined by the client device's
22 configuration used by those states.
31 they require certain specific named states for dynamic pin configuration.
41 Each client device's own binding determines the set of states that must be
61 the binding for that IP block requires certain pin states to
70 pinctrl-names: The list of names to assign states. List entry 0 defines the
76 /* For a client device requiring named states */
/freebsd/contrib/libxo/libxo/
H A Dxo_explicit.h17 * explicit transition between libxo states on its internal stack.
23 * A word about states: We use a finite state machine (FMS) approach
31 * You can think of states as either states or events, since they
33 * persist as states, since the matching stack frame will be popped.
38 /* Stack frame states */
/freebsd/share/doc/psd/15.yacc/
H A Dss460 The states of the finite state machine are given
82 This may result in states being pushed onto the stack, or popped off of
140 To reduce, first pop off the top three states
142 (In general, the number of states popped equals the number of symbols on the
144 In effect, these states were the ones
151 After popping these states, a state is uncovered
173 popping the states off the stack to go back to the
177 no states are popped off of the stack: the uncovered state
184 In addition to the stack holding the states, another stack,
321 two states, 6 and 3, are popped off of the stack, uncovering state 0.
[all …]
/freebsd/contrib/llvm-project/llvm/include/llvm/TableGen/
H A DAutomaton.td15 // generic finite-state automaton over a set of actions and states.
23 // Q: A set of possible states.
26 // F: The set of final (accepting) states.
28 // Because generating all possible states is tedious, we instead define the
29 // transition function only and crawl all reachable states starting from the
32 // We define F = S, that is, all valid states are accepting.
40 // Instead of defining all possible states (which would be cumbersome), the user
53 // sequence of states traversed to accept that input.
/freebsd/sys/contrib/device-tree/src/arm64/freescale/
H A Dfsl-ls2088a.dtsi28 cpu-idle-states = <&CPU_PW20>;
38 cpu-idle-states = <&CPU_PW20>;
48 cpu-idle-states = <&CPU_PW20>;
58 cpu-idle-states = <&CPU_PW20>;
69 cpu-idle-states = <&CPU_PW20>;
78 cpu-idle-states = <&CPU_PW20>;
88 cpu-idle-states = <&CPU_PW20>;
98 cpu-idle-states = <&CPU_PW20>;
/freebsd/contrib/bc/include/
H A Drand.h106 * @return The product of the PCG states.
114 * @return The sum of the PCG states.
119 * Multiply two PCG states.
122 * @return The product of the PCG states.
127 * Add two PCG states.
130 * @return The sum of the PCG states.
195 * @return The product of the PCG states.
203 * @return The sum of the PCG states.
208 * Multiply two PCG states.
211 * @return The product of the PCG states
[all...]
/freebsd/sbin/pfctl/
H A Dpfctl.8217 .It Fl F Cm states
288 To kill all states originating from 192.168.1.0/24 to 172.16.0.0/16:
293 To kill all states with the target
298 It is also possible to kill states by rule label or state ID.
303 The following command would kill all states that have been created
323 It is also possible to kill states created from a rule with the route-to/reply-to
327 To kill all states using a gateway of 192.168.0.1 use:
332 To kill all states using a gateway in 192.168.0.0/24:
336 States can also be killed based on their pre-NAT address:
341 Kill matching states i
[all...]
/freebsd/sys/contrib/device-tree/src/arm64/sprd/
H A Dums9620.dtsi53 cpu-idle-states = <&LIT_CORE_PD>;
61 cpu-idle-states = <&LIT_CORE_PD>;
69 cpu-idle-states = <&LIT_CORE_PD>;
77 cpu-idle-states = <&LIT_CORE_PD>;
85 cpu-idle-states = <&BIG_CORE_PD>;
93 cpu-idle-states = <&BIG_CORE_PD>;
101 cpu-idle-states = <&BIG_CORE_PD>;
109 cpu-idle-states = <&BIG_CORE_PD>;
113 idle-states {

12345678910>>...84