| /linux-6.15/Documentation/devicetree/bindings/dma/ |
| H A D | mv-xor.txt | 20 - dmacap,memcpy to indicate that the XOR channel is capable of memcpy operations
21 - dmacap,memset to indicate that the XOR channel is capable of memset operations
22 - dmacap,xor to indicate that the XOR channel is capable of xor operations
23 - dmacap,interrupt to indicate that the XOR channel is capable of
|
| /linux-6.15/Documentation/networking/device_drivers/cellular/qualcomm/ |
| H A D | rmnet.rst | 42 Command (1)/ Data (0) bit value is to indicate if the packet is a MAP command
51 Multiplexer ID is to indicate the PDN on which data has to be sent.
68 Command (1)/ Data (0) bit value is to indicate if the packet is a MAP command
77 Multiplexer ID is to indicate the PDN on which data has to be sent.
121 Command (1)/ Data (0) bit value is to indicate if the packet is a MAP command
125 Next header is used to indicate the presence of another header, currently is
131 Multiplexer ID is to indicate the PDN on which data has to be sent.
143 Header Type is to indicate the type of header, this usually is set to CHECKSUM
151 Checksum Valid is to indicate whether the header checksum is valid. Value of 1
|
| /linux-6.15/Documentation/leds/ |
| H A D | well-known-leds.txt | 21 Game controllers may feature LEDs to indicate a player number. This is commonly
23 The "player LEDs" are then programmed with a pattern to indicate a particular
25 to indicate player 1, "-x--" to indicate player 2 etcetera where "x" means on.
101 multiple LEDs, use left/right, or top/bottom to indicate their
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-light-si1133 | 6 dark photodiode. "small" indicate the surface area capturing
14 dark photodiodes. "large" indicate the surface area capturing
|
| H A D | sysfs-devices-mmc | 8 is enabled, this attribute will indicate the start address of
19 is enabled, this attribute will indicate the size of enhanced
|
| H A D | sysfs-class-spi-eeprom | 7 name to indicate that it employs ferroelectric process.
|
| H A D | sysfs-platform-intel-pmc | 8 manufacturing process to indicate that consequent reset
|
| /linux-6.15/Documentation/trace/ |
| H A D | events-kmem.rst | 25 Heavy activity for these events may indicate that a specific cache is
65 is triggered. Significant amounts of activity here could indicate that the
71 indicate that the system is under memory pressure and can also indicate
97 is being concentrated in one place. It could also indicate that the per-CPU
|
| /linux-6.15/Documentation/userspace-api/gpio/ |
| H A D | gpio-v2-line-set-values-ioctl.rst | 30 to indicate the subset of requested lines to set and ``bits`` set to
31 indicate the new value.
|
| /linux-6.15/Documentation/hwmon/ |
| H A D | occ.rst | 57 Temperature sensor fault boolean; 1 to indicate
58 that a fault is present or 0 to indicate that
64 VRM temperature alarm boolean; 1 to indicate
65 alarm, 0 to indicate no alarm
|
| H A D | sht15.rst | 67 flag to indicate not to reload from OTP (default to false).
69 flag to indicate the temp/humidity resolution to use (default to false).
|
| H A D | adt7410.rst | 53 INT pin to indicate that a minimum or maximum temperature set point has been
54 exceeded, as well as a critical temperature (CT) pin to indicate that the
|
| H A D | scpi-hwmon.rst | 33 The driver relies on device tree node to indicate the presence of SCPI
|
| /linux-6.15/Documentation/admin-guide/device-mapper/ |
| H A D | kcopyd.rst | 9 Users of kcopyd must first create a client and indicate how many memory pages
40 passing back the user's context pointer. It will also indicate if a read or
|
| /linux-6.15/Documentation/devicetree/bindings/iio/resolver/ |
| H A D | adi,ad2s1210.yaml | 112 GPIO lines connected to the LOT and DOS pins. These pins combined indicate
113 the type of fault present, if any. As these pins a pulled low to indicate
120 This is used to indicate the selected mode if A0 and A1 are hard-wired
|
| /linux-6.15/Documentation/devicetree/bindings/sound/ |
| H A D | nvidia,tegra30-ahub.txt | 59 For RX CIFs, the numbers indicate the register number within AHUB routing
61 For TX CIFs, the numbers indicate the bit position within the AHUB routing
|
| /linux-6.15/drivers/net/hyperv/ |
| H A D | netvsc_drv.c | 667 struct rndis_indicate_status *indicate = &resp->msg.indicate_status; in netvsc_linkstatus_callback() local
680 memcpy(indicate, data + RNDIS_HEADER_SIZE, sizeof(*indicate)); in netvsc_linkstatus_callback()
683 if (indicate->status == RNDIS_STATUS_LINK_SPEED_CHANGE) { in netvsc_linkstatus_callback()
692 if (indicate->status_buflen < sizeof(speed) || in netvsc_linkstatus_callback()
693 indicate->status_buf_offset < sizeof(*indicate) || in netvsc_linkstatus_callback()
695 data_buflen - RNDIS_HEADER_SIZE - indicate->status_buf_offset in netvsc_linkstatus_callback()
696 < indicate->status_buflen) { in netvsc_linkstatus_callback()
707 if (indicate->status != RNDIS_STATUS_NETWORK_CHANGE && in netvsc_linkstatus_callback()
708 indicate->status != RNDIS_STATUS_MEDIA_CONNECT && in netvsc_linkstatus_callback()
709 indicate->status != RNDIS_STATUS_MEDIA_DISCONNECT) in netvsc_linkstatus_callback()
[all …]
|
| /linux-6.15/Documentation/arch/arm64/ |
| H A D | elf_hwcaps.rst | 45 The majority of hwcaps are intended to indicate the presence of features
55 Such hwcaps indicate the availability of functionality that the ARM ARM
57 indicate that idreg.field is precisely equal to val, nor do they
58 indicate the absence of functionality implied by other values of
61 Other hwcaps may indicate the presence of features which cannot be
|
| /linux-6.15/Documentation/networking/ |
| H A D | rxrpc.rst | 245 to indicate the terminal message for that call.
366 RXRPC_USER_CALL_ID to indicate the call that's now complete.
378 This is delivered to a client application to indicate that a call was
380 associated with an RXRPC_USER_CALL_ID to indicate the rejected call.
384 This is delivered to an application to indicate that a local error was
400 to indicate the user ID to be assigned. If there is no call to be
407 This is used to indicate that a client call should be made on a one-off
487 This is used to indicate that a service socket with two bindings may
633 the service - otherwise it will be altered to indicate the service ID the
714 RXRPC_ACCEPT indicate connection acceptance
[all …]
|
| H A D | secid.rst | 9 The secid member in the flow structure is used in LSMs (e.g. SELinux) to indicate
|
| /linux-6.15/Documentation/PCI/endpoint/ |
| H A D | pci-ntb-function.rst | 66 (ATU) and to indicate the link status. Endpoint can indicate the status of
67 commands issued by host in this region. Endpoint can also indicate the
131 CMD_LINK_UP (0x3): Command to indicate an NTB application is
134 raise a LINK_UP event to both the hosts to indicate the host
|
| /linux-6.15/Documentation/devicetree/bindings/spi/ |
| H A D | cdns,qspi-nor.yaml | 126 Flag to indicate whether decoder is used to select different chip select
132 Flag to indicate that QSPI return clock is used to latch the read
|
| /linux-6.15/Documentation/devicetree/bindings/powerpc/opal/ |
| H A D | sensor-groups.txt | 13 - type : String to indicate the type of sensor-group
|
| /linux-6.15/arch/arm64/boot/dts/qcom/ |
| H A D | qcs8550.dtsi | 20 * indicate the firmware related reserved information. Bootloader
29 * that indicate fimware-related shared information. A label name
|
| /linux-6.15/Documentation/devicetree/bindings/misc/ |
| H A D | nvidia,tegra186-misc.yaml | 29 indicate strapping options
|