| /Documentation/networking/dsa/ |
| D | b53.rst | 61 The configuration can only be set up via VLAN tagging and bridge setup.
71 # The conduit interface needs to be brought up before the user ports.
72 ip link set eth0 up
73 ip link set eth0.1 up
74 ip link set eth0.2 up
75 ip link set eth0.3 up
77 # bring up the user interfaces
78 ip link set wan up
79 ip link set lan1 up
80 ip link set lan2 up
[all …]
|
| D | configuration.rst | 37 The user interfaces depend on the conduit interface being up in order for them
42 - when a DSA user interface is brought up, the conduit interface is
43 automatically brought up.
100 # brought up manually before the user ports.
101 ip link set eth0 up
103 # bring up the user interfaces
104 ip link set lan1 up
105 ip link set lan2 up
106 ip link set lan3 up
112 # brought up manually before the user ports.
[all …]
|
| /Documentation/admin-guide/aoe/ |
| D | aoe.rst | 76 state, mac, and netif. The state attribute is "up" when the device
79 cannot come up again until it has been closed.
90 e10.0 eth3 up
91 e10.1 eth3 up
92 e10.2 eth3 up
93 e10.3 eth3 up
94 e10.4 eth3 up
95 e10.5 eth3 up
96 e10.6 eth3 up
97 e10.7 eth3 up
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | ams,as3711.yaml | 15 two step-up DC/DC converters are defined.
26 Step-up converter configuration, to be used as a backlight source
34 description: Framebuffer phandle for the first step-up converter
38 description: Maximum current for the first step-up converter
42 description: Framebuffer phandle for the second step-up converter
46 description: Maximum current for the second step-up converter
50 description: Second step-up converter uses voltage feedback
55 Second step-up converter uses CURR1 input for current feedback
60 Second step-up converter uses CURR2 input for current feedback
65 Second step-up converter uses CURR3 input for current feedback
[all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | atmel,sama5d2-shdwc.yaml | 14 and VDDCORE and the wake-up detection on debounced input lines.
40 Minimum wake-up inputs debouncer period in microseconds. It is usually a
44 description: enable real-time clock wake-up
48 description: enable real-time timer wake-up
54 Wake-up input nodes. These are usually described in the "board" part of
55 the Device Tree. Note also that input 0 is linked to the wake-up pin and
60 description: contains the wake-up input index
66 The corresponding wake-up input described by the child forces the
67 wake-up of the core power supply on a high level. The default is to
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,mxs-pinctrl.txt | 6 voltage and pull-up.
20 information about pull-up. For this reason, even seemingly boolean values are
26 One is to set up a group of pins for a function, both mux selection and pin
52 since config node is only meant to set up pin configurations.
69 - fsl,pull-up: Integer.
70 0: MXS_PULL_DISABLE - Disable the internal pull-up
71 1: MXS_PULL_ENABLE - Enable the internal pull-up
73 Note that when enabling the pull-up, the internal pad keeper gets disabled.
74 Also, some pins doesn't have a pull up, in that case, setting the fsl,pull-up
102 fsl,pull-up = <MXS_PULL_ENABLE>;
[all …]
|
| D | samsung,pinctrl-wakeup-interrupt.yaml | 7 title: Samsung S3C/S5P/Exynos SoC pin controller - wake-up interrupt controller
18 External wake-up interrupts for Samsung S3C/S5P/Exynos SoC pin controller.
19 For S3C24xx, S3C64xx, S5PV210 and Exynos4210 compatible wake-up interrupt
20 controllers, only one pin-controller device node can include external wake-up
21 interrupts child node (in other words, only one External wake-up interrupts
24 external wake-up interrupts child node.
55 Interrupt used by multiplexed external wake-up interrupts.
|
| D | sprd,sc9860-pinctrl.txt | 20 - bias-pull-up: Pull up on pin. Supported values: 20000 for pull-up resistor
21 is 20K and 4700 for pull-up resistor is 4.7K.
63 bias-pull-up = <4700>;
67 bias-pull-up;
|
| D | ste,nomadik.txt | 18 parameters, such as input, output, pull up, pull down...
30 set-up.
40 1: input with pull up,
54 1: sleep input with pull up,
56 3: sleep input and keep last input configuration (no pull, pull up or pull down).
68 0: wake-up detection enabled,
69 1: wake-up detection disabled.
72 0: GPIO pull-up or pull-down resistor is enabled, when pin is an input,
73 1: GPIO pull-up and pull-down resistor are disabled.
|
| D | samsung,pinctrl-gpio-bank.yaml | 31 For GPIO banks supporting external GPIO interrupts or external wake-up
37 For GPIO banks supporting external GPIO interrupts or external wake-up
42 For GPIO banks supporting direct external wake-up interrupts (without
43 multiplexing). Number of interrupts must match number of wake-up capable
|
| D | mediatek,mt8195-pinctrl.yaml | 57 Identifying i2c pins pull up/down type which is RSEL. It can support RSEL
153 bias-pull-up:
157 description: mt8195 pull up PUPD/R0/R1 type define value.
159 description: mt8195 pull up RSEL type define value.
161 description: mt8195 pull up RSEL type si unit value(ohm).
163 For pull up type is normal, it don't need add RSEL & R1R0 define
165 For pull up type is PUPD/R0/R1 type, it can add R1R0 define to
169 For pull up type is RSEL, it can add RSEL define & resistance
184 bias-pull-up = <MTK_PULL_SET_RSEL_001>;
196 bias-pull-up = <1000>;
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ntc-thermistor.yaml | 17 up table and interpolation to get from resistance to temperature.
20 pull-up resistor or/and a pull-down resistor and a fixed voltage like this:
22 + e.g. 5V = pull-up voltage (puv)
26 | | Pull-up resistor
49 the cases when either pull-up or pull-down resistance is zero.
51 If the pull-up resistance is 0 one end of the thermistor is connected to the
56 connected to ground and we get the thermistor under the pull-up resistor
57 and we take the measure between the pull-up resistor and the thermistor.
59 We can use both pull-up and pull-down resistors at the same time, and then
97 description: Pull-up voltage in micro volts. Must always be specified.
[all …]
|
| /Documentation/networking/ |
| D | vrf.rst | 70 ip link set dev vrf-blue up
188 …11: mgmt: <NOARP,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default…
191 …12: red: <NOARP,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default …
194 …13: blue: <NOARP,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default…
197 …14: green: <NOARP,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group defaul…
205 mgmt UP 72:b3:ba:91:e2:24 <NOARP,MASTER,UP,LOWER_UP>
206 red UP b6:6f:6e:f6:da:73 <NOARP,MASTER,UP,LOWER_UP>
207 blue UP 36:62:e8:7d:bb:8c <NOARP,MASTER,UP,LOWER_UP>
208 green UP e6:28:b8:63:70:bb <NOARP,MASTER,UP,LOWER_UP>
237 …3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master red state UP mode DEFA…
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-power | 14 space to check if the device is enabled to wake up the system
33 be enabled to wake up the system from sleep states.
52 the device is suspended causes it to be woken up.
86 attribute is read-only. If the device is not capable to wake up
88 If the device is not enabled to wake up the system from sleep
98 is read-only. If the device is not capable to wake up the
100 the device is not enabled to wake up the system from sleep
111 is not capable to wake up the system from sleep states, this
113 up the system from sleep states, this attribute is empty.
122 read-only. If the device is not capable to wake up the system
[all …]
|
| D | sysfs-devices-platform-ACPI-TAD | 16 BIT(5): The AC timer wakes up from S4 if set
17 BIT(6): The AC timer wakes up from S5 if set
18 BIT(7): The DC timer wakes up from S4 if set
19 BIT(8): The DC timer wakes up from S5 if set
31 "disabled", if the AC alarm is not set to wake up the system.
37 expires, it will immediately wake up the system from the S3
69 Bit(1): The timer has woken up the system from a sleep state
81 it will immediately wake up the system from the S3 sleep state
|
| /Documentation/mm/ |
| D | z3fold.rst | 6 It is designed to store up to three compressed pages per physical page.
12 * unlike zbud, z3fold allows for up to PAGE_SIZE allocations
13 * z3fold can hold up to 3 compressed pages in its page
19 up to 3 pages unlike zbud which can store at most 2. Therefore the
|
| /Documentation/arch/arm/ |
| D | cluster-pm-race-avoidance.rst | 2 Cluster-wide Power-up/power-down race avoidance algorithm
34 are not immediately enabled when a cluster powers up. Since enabling or
38 power-down and power-up at the cluster level.
52 - UP
57 +---------> UP ----------+
71 The CPU or cluster has committed to moving to the UP state.
75 UP:
153 a) an explicit hardware power-up operation, resulting
161 cluster is set up and coherent. If the cluster is not ready,
163 cluster has been set up.
[all …]
|
| /Documentation/power/ |
| D | swsusp-dmcrypt.rst | 16 Now your system is properly set up, your disk is encrypted except for
26 up dm-crypt and then asks swsusp to resume from the encrypted
29 The most important thing is that you set up dm-crypt in such
33 to always set up this swap device first with dmsetup, so that
38 Now set up your kernel to use /dev/mapper/swap0 as the default
64 /dev/hda1 contains an unencrypted mini system that sets up all
125 Then we need to set up dmcrypt with the setup data from the
134 mini system on /dev/hda1 to set the whole crypto up (it is up to
139 the initrd prior to continue booting but it is up to you to modify
|
| /Documentation/misc-devices/ |
| D | spear-pcie-gadget.rst | 56 link write UP to enable ltsmm DOWN to disable
120 go for link up now::
122 # echo UP >> link
124 It will have to be insured that, once link up is done on gadget, then only host
129 /*wait till link is up*/
132 Wait till it returns UP.
150 go for link up now::
152 # echo UP >> link
154 wait till link is up::
158 An application can repetitively read this node till link is found UP. It can
|
| /Documentation/devicetree/bindings/regulator/ |
| D | rohm,bd71847-regulator.yaml | 123 # V FB-pull-up
133 # Vpu is the pull-up voltage V FB-pull-up in the picture
136 rohm,fb-pull-up-microvolt:
138 Feedback-pin has pull-up connection to adjust voltage range. This is
139 the used pull-up voltage before R1.
141 rohm,feedback-pull-up-r1-ohms:
143 Feedback-pin has pull-up connection to adjust voltage range. This is
146 rohm,feedback-pull-up-r2-ohms:
148 Feedback-pin has pull-up connection to adjust voltage range. This is
|
| D | rohm,bd71837-regulator.yaml | 128 # V FB-pull-up
138 # Vpu is the pull-up voltage V FB-pull-up in the picture
141 rohm,fb-pull-up-microvolt:
143 Feedback-pin has pull-up connection to adjust voltage range. This is
144 the used pull-up voltage before R1.
146 rohm,feedback-pull-up-r1-ohms:
148 Feedback-pin has pull-up connection to adjust voltage range. This is
151 rohm,feedback-pull-up-r2-ohms:
153 Feedback-pin has pull-up connection to adjust voltage range. This is
|
| /Documentation/admin-guide/ |
| D | lcd-panel-cgram.rst | 5 Some LCDs allow you to define up to 8 characters, mapped to ASCII
8 number, and up to 8 couples of hex digits terminated by a semi-colon
17 printf "\e[LG1040E1F0000000000;" => 1 = [up]
19 printf "\e[LG3040E1F001F0E0400;" => 3 = [up-down]
|
| /Documentation/trace/ |
| D | debugging.rst | 61 It can be very useful in knowing what happened up to the point of the crash.
64 the ring buffer will be all the events that lead up to the crash.
76 Note, the tracing buffer is made up of per CPU buffers where each of these
77 buffers is broken up into sub-buffers that are by default PAGE_SIZE. The
100 reserved. As the ring buffer is broke up into per CPU buffers, the 12
101 megabytes will be broken up evenly between those CPUs. If you have 8 CPUs,
112 boot up, and align it by 4096 bytes. It will label this memory as "trace"
128 On boot up, the memory reserved for the ring buffer is validated. It will go
130 data. If it is, it will then set it up to be available to read from the
145 destination from the kernel command line, or set it after boot up via the
[all …]
|
| /Documentation/filesystems/ |
| D | idmappings.rst | 64 mapping ``k11000`` up to ``u1000``. Afterwards, we can map ``u1000`` down using
99 left" we can also say "up". Obviously mapping down and up invert each other.
109 idmapping. So we're mapping up in the first idmapping::
203 If we've been given ``k11000`` from one idmapping we can map that id up in
215 /* Map the kernel id up into a userspace id in the second idmapping. */
224 /* Map the kernel id up into a userspace id in the first idmapping. */
240 ownership information about the file the kernel can't simply map the id back up
244 So the kernel will map the id back up in the idmapping of the caller. Let's
246 ``u3000:k20000:r10000`` then ``k21000`` would map back up to ``u4000``.
265 1. Map the kernel id up into a userspace id in the first idmapping::
[all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | nvidia,tegra20-sdhci.yaml | 140 nvidia,pad-autocal-pull-up-offset-1v8:
145 nvidia,pad-autocal-pull-up-offset-1v8-timeout:
150 nvidia,pad-autocal-pull-up-offset-3v3:
162 nvidia,pad-autocal-pull-up-offset-3v3-timeout:
167 nvidia,pad-autocal-pull-up-offset-sdr104:
171 nvidia,pad-autocal-pull-up-offset-hs400:
233 description: pull-up/down configuration for 3.3 V
235 description: pull-up/down configuration for 1.8 V
238 description: pull-up/down configuration for 3.3 V
240 description: pull-up/down configuration for 1.8 V
[all …]
|