| /kernel/linux/linux-6.6/tools/testing/selftests/drivers/net/mlxsw/ |
| D | devlink_trap_control.sh | 222 $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
230 "igmp_v1_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
238 "igmp_v2_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
246 "igmp_v3_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
254 "igmp_v2_leave" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:02 \
310 $MZ $h1 -c 1 -a own -b bcast -A 0.0.0.0 -B 255.255.255.255 \
314 $MZ $h1 -c 1 -a own -b $(mac_get $rp1) -A 192.0.2.1 \
332 $MZ $h1 -c 1 -a own -b bcast -t arp request -p 100 -q
338 $MZ $h1 -c 1 -a own -b $(mac_get $rp1) -t arp reply -p 100 -q
366 "ipv6_neigh_advert" $MZ $h1 -6 -c 1 -a own -b $(mac_get $rp1) \
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/drivers/net/mlxsw/ |
| D | devlink_trap_control.sh | 220 $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
228 "igmp_v1_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
236 "igmp_v2_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
244 "igmp_v3_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
252 "igmp_v2_leave" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:02 \
308 $MZ $h1 -c 1 -a own -b bcast -A 0.0.0.0 -B 255.255.255.255 \
312 $MZ $h1 -c 1 -a own -b $(mac_get $rp1) -A 192.0.2.1 \
330 $MZ $h1 -c 1 -a own -b bcast -t arp request -p 100 -q
336 $MZ $h1 -c 1 -a own -b $(mac_get $rp1) -t arp reply -p 100 -q
364 "ipv6_neigh_advert" $MZ $h1 -6 -c 1 -a own -b $(mac_get $rp1) \
[all …]
|
| D | devlink_trap_l2_drops.sh | 130 $MZ $h1 "$opt" -c 0 -p 100 -a own -b $dmac -t ip -d 1msec -q &
190 $MZ $h1 -Q $vid -c 0 -p 100 -a own -b $dmac -t ip -d 1msec -q &
233 $MZ $h1 -Q $vid -c 0 -p 100 -a own -b $dmac -t ip -d 1msec -q &
303 $MZ $h1 -c 0 -p 100 -a own -b $dmac -t ip -d 1msec -q &
348 $MZ $h1 -c 0 -p 100 -a own -b $dmac -t ip -B $dip -d 1msec -q &
394 $MZ $h1 -c 0 -p 100 -a own -b $dmac -t ip -d 1msec -q &
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/knightslanding/ |
| D | cache.json | 165 …and prefetch code read requests that accounts for responses which hit its own tile's L2 with data…
174 …and prefetch code read requests that accounts for responses which hit its own tile's L2 with data…
183 …and prefetch code read requests that accounts for responses which hit its own tile's L2 with data…
192 …and prefetch code read requests that accounts for responses which hit its own tile's L2 with data…
273 … L1 prefetch data read requests that accounts for responses which hit its own tile's L2 with data…
282 … L1 prefetch data read requests that accounts for responses which hit its own tile's L2 with data…
291 … L1 prefetch data read requests that accounts for responses which hit its own tile's L2 with data…
300 … L1 prefetch data read requests that accounts for responses which hit its own tile's L2 with data…
381 …": "Counts any Prefetch requests that accounts for responses which hit its own tile's L2 with data…
390 …": "Counts any Prefetch requests that accounts for responses which hit its own tile's L2 with data…
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/knightslanding/ |
| D | cache.json | 1268 … data and L1 prefetch data reads that accounts for responses which hit its own tile's L2 with data…
1279 …nts Demand cacheable data writes that accounts for responses which hit its own tile's L2 with data…
1290 …de reads and prefetch code reads that accounts for responses which hit its own tile's L2 with data…
1301 …(includes PREFETCHW instruction) that accounts for responses which hit its own tile's L2 with data…
1312 …for Outstanding response type). that accounts for responses which hit its own tile's L2 with data…
1323 …nd should be programmed on PMC1) that accounts for responses which hit its own tile's L2 with data…
1334 … for Outstanding response type) that accounts for responses which hit its own tile's L2 with data…
1345 …us locks and split lock requests that accounts for responses which hit its own tile's L2 with data…
1356 …on": "Counts Software Prefetches that accounts for responses which hit its own tile's L2 with data…
1367 …": "Counts L1 data HW prefetches that accounts for responses which hit its own tile's L2 with data…
[all …]
|
| /kernel/linux/linux-6.6/drivers/video/fbdev/core/ |
| D | Kconfig | 50 filling. This is used by drivers that don't provide their own
58 This is used by drivers that don't provide their own (accelerated)
66 blitting. This is used by drivers that don't provide their own
82 filling. This is used by drivers that don't provide their own
90 This is used by drivers that don't provide their own (accelerated)
98 blitting. This is used by drivers that don't provide their own
|
| /kernel/linux/linux-5.10/drivers/media/pci/ttpci/ |
| D | Kconfig | 38 Say Y if you own such a card and want to use it.
85 Say Y if you own such a card and want to use it.
112 Say Y if you own such a card and want to use it.
135 Say Y if you own such a card and want to use it.
157 Say Y if you own such a card and want to use it.
|
| /kernel/linux/linux-6.6/drivers/net/fddi/ |
| D | defza.c | 449 u32 own, rmc; in fza_do_xmit() local
461 own = FZA_RING_TX_OWN_HOST; in fza_do_xmit()
485 writel_o(own, &fp->ring_rmc_tx[i].own); in fza_do_xmit()
492 own = FZA_RING_TX_OWN_RMC; in fza_do_xmit()
503 writel_o(FZA_RING_TX_OWN_RMC, &fp->ring_rmc_tx[first].own); in fza_do_xmit()
516 u32 own; in fza_do_recv_smt() local
520 own = readl_o(&fp->ring_smt_rx[i].own); in fza_do_recv_smt()
521 if ((own & FZA_RING_OWN_MASK) == FZA_RING_OWN_FZA) in fza_do_recv_smt()
530 writel_o(FZA_RING_OWN_FZA, &fp->ring_smt_rx[i].own); in fza_do_recv_smt()
544 u32 own, rmc; in fza_tx() local
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/fddi/ |
| D | defza.c | 449 u32 own, rmc; in fza_do_xmit() local
461 own = FZA_RING_TX_OWN_HOST; in fza_do_xmit()
485 writel_o(own, &fp->ring_rmc_tx[i].own); in fza_do_xmit()
492 own = FZA_RING_TX_OWN_RMC; in fza_do_xmit()
503 writel_o(FZA_RING_TX_OWN_RMC, &fp->ring_rmc_tx[first].own); in fza_do_xmit()
516 u32 own; in fza_do_recv_smt() local
520 own = readl_o(&fp->ring_smt_rx[i].own); in fza_do_recv_smt()
521 if ((own & FZA_RING_OWN_MASK) == FZA_RING_OWN_FZA) in fza_do_recv_smt()
530 writel_o(FZA_RING_OWN_FZA, &fp->ring_smt_rx[i].own); in fza_do_recv_smt()
544 u32 own, rmc; in fza_tx() local
[all …]
|
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | adm1031.rst | 33 They sense their own temperature as well as the temperature of up to one
39 Each temperature channel has its own high and low limits, plus a critical
43 two. Each fan channel has its own low speed limit.
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | adm1031.rst | 33 They sense their own temperature as well as the temperature of up to one
39 Each temperature channel has its own high and low limits, plus a critical
43 two. Each fan channel has its own low speed limit.
|
| /kernel/linux/linux-6.6/Documentation/arch/mips/ |
| D | ingenic-tcu.rst | 18 - Each one of the TCU channels has its own clock, which can be reparented to three
45 own interrupt line; channels 2-7 share the last interrupt line.
46 - On JZ4725B, channel 0 has its own interrupt; channels 1-5 share one
48 - on newer SoCs (JZ4750 and above), channel 5 has its own interrupt;
|
| /kernel/linux/linux-5.10/Documentation/mips/ |
| D | ingenic-tcu.rst | 18 - Each one of the TCU channels has its own clock, which can be reparented to three
45 own interrupt line; channels 2-7 share the last interrupt line.
46 - On JZ4725B, channel 0 has its own interrupt; channels 1-5 share one
48 - on newer SoCs (JZ4750 and above), channel 5 has its own interrupt;
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | typec.rst | 30 Every port will be presented as its own device under /sys/class/typec/. The
33 When connected, the partner will be presented also as its own device under
39 The cable and the two plugs on it may also be optionally presented as their own
47 Alternate Mode SVID will have their own device describing them. Note that the
51 Every mode that is supported will have its own group under the Alternate Mode
110 The plugs are represented as their own devices. The cable is registered first,
172 own functions, but the registration will always return a handle to struct
201 own logical components: "mux" for the mode and "switch" for the orientation.
|
| /kernel/linux/linux-6.6/Documentation/driver-api/usb/ |
| D | typec.rst | 30 Every port will be presented as its own device under /sys/class/typec/. The
33 When connected, the partner will be presented also as its own device under
39 The cable and the two plugs on it may also be optionally presented as their own
47 Alternate Mode SVID will have their own device describing them. Note that the
51 Every mode that is supported will have its own group under the Alternate Mode
110 The plugs are represented as their own devices. The cable is registered first,
172 own functions, but the registration will always return a handle to struct
201 own logical components: "mux" for the mode and "switch" for the orientation.
|
| /kernel/linux/linux-5.10/Documentation/riscv/ |
| D | patch-acceptance.rst | 24 course, maintain their own Linux kernel trees that contain code for
28 their own custom extensions. These custom extensions aren't required
34 (Implementors, may, of course, maintain their own Linux kernel trees
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-detect.rst | 37 - The image is divided into a grid, each cell with its own motion
41 - The image is divided into a grid, each cell with its own region
43 should be used. Each region has its own thresholds. How these
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-detect.rst | 37 - The image is divided into a grid, each cell with its own motion
41 - The image is divided into a grid, each cell with its own region
43 should be used. Each region has its own thresholds. How these
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | edid.rst | 19 - A KVM sends its own EDID data instead of querying the connected monitor.
39 If you want to create your own EDID file, copy the file 1024x768.S,
40 replace the settings with your own data and add a new target to the
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | edid.rst | 19 - A KVM sends its own EDID data instead of querying the connected monitor.
39 If you want to create your own EDID file, copy the file 1024x768.S,
40 replace the settings with your own data and add a new target to the
|
| /kernel/linux/linux-6.6/drivers/media/pci/ttpci/ |
| D | Kconfig | 33 Say Y if you own such a card and want to use it.
60 Say Y if you own such a card and want to use it.
83 Say Y if you own such a card and want to use it.
|
| /kernel/linux/linux-6.6/tools/testing/selftests/drivers/net/dsa/ |
| D | bridge_mdb.sh | 839 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
846 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
852 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
859 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
887 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
894 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
900 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
907 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
967 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $valid_src -B $grp -t udp -q
971 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $invalid_src -B $grp -t udp -q
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/net/forwarding/ |
| D | bridge_mdb.sh | 839 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
846 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
852 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
859 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
887 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
894 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
900 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
907 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
967 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $valid_src -B $grp -t udp -q
971 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $invalid_src -B $grp -t udp -q
[all …]
|
| D | tc_flower_l2_miss.sh | 89 $MZ $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
100 $MZ $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
111 $MZ $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
146 $MZ $mode $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
157 $MZ $mode $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
168 $MZ $mode $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
258 $MZ $mode $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | 6.Followthrough.rst | 7 addition of your own engineering skills, have posted a perfect series of
48 agendas at the expense of your own. Kernel developers often expect to
56 making. Do not let their form of expression or your own pride keep that
69 be easy to become blinded by your own solution to a problem to the point
110 subsystem to the next; each maintainer has his or her own way of doing
142 Merging into the mainline brings its own challenges.
193 your own), or send an Acked-by: response back and let the original poster
|