Searched refs:indicate (Results 1 – 25 of 377) sorted by relevance
12345678910>>...16
| /linux-5.19.10/Documentation/devicetree/bindings/dma/ |
| 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-5.19.10/Documentation/networking/device_drivers/cellular/qualcomm/ |
| 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-5.19.10/Documentation/devicetree/bindings/pinctrl/ |
| D | atmel,at91-pinctrl.txt | 89 PULL_UP (1 << 0): indicate this pin needs a pull up.
90 MULTIDRIVE (1 << 1): indicate this pin needs to be configured as multi-drive.
92 DEGLITCH (1 << 2): indicate this pin needs deglitch.
93 PULL_DOWN (1 << 3): indicate this pin needs a pull down.
94 DIS_SCHMIT (1 << 4): indicate this pin needs to the disable schmitt trigger.
95 DRIVE_STRENGTH (3 << 5): indicate the drive strength of the pin using the
101 OUTPUT (1 << 7): indicate this pin need to be configured as an output.
104 DEBOUNCE (1 << 16): indicate this pin needs debounce.
|
| /linux-5.19.10/Documentation/leds/ |
| 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.
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-light-si1133 | 6 dark photodiode. "small" indicate the surface area capturing
14 dark photodiodes. "large" indicate the surface area capturing
|
| 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
|
| D | sysfs-class-spi-eeprom | 7 name to indicate that it employs ferroelectric process.
|
| /linux-5.19.10/Documentation/trace/ |
| 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-5.19.10/Documentation/arm64/ |
| 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-5.19.10/Documentation/devicetree/bindings/input/rmi4/ |
| D | rmi_spi.txt | 12 - #address-cells: Set to 1 to indicate that the function child nodes
14 - #size-cells: Set to 0 to indicate that the function child nodes do not
|
| D | rmi_i2c.txt | 12 - #address-cells: Set to 1 to indicate that the function child nodes
14 - #size-cells: Set to 0 to indicate that the function child nodes do not
|
| /linux-5.19.10/Documentation/hwmon/ |
| 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
|
| 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).
|
| 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
|
| /linux-5.19.10/Documentation/admin-guide/device-mapper/ |
| 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-5.19.10/Documentation/devicetree/bindings/spi/ |
| D | cdns,qspi-nor.yaml | 68 Flag to indicate whether decoder is used to select different chip select
74 Flag to indicate that QSPI return clock is used to latch the read
|
| /linux-5.19.10/Documentation/devicetree/bindings/sound/ |
| 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-5.19.10/Documentation/devicetree/bindings/soundwire/ |
| D | qcom,sdw.txt | 103 Definition: should be 0 or 1 to indicate the block packing mode.
104 0 to indicate Blocks are per Channel
105 1 to indicate Blocks are per Port.
114 Definition: should be in range 1 to 4 to indicate how many sample
|
| /linux-5.19.10/drivers/net/hyperv/ |
| D | netvsc_drv.c | 696 struct rndis_indicate_status *indicate = &resp->msg.indicate_status; in netvsc_linkstatus_callback() local
709 memcpy(indicate, data + RNDIS_HEADER_SIZE, sizeof(*indicate)); in netvsc_linkstatus_callback()
712 if (indicate->status == RNDIS_STATUS_LINK_SPEED_CHANGE) { in netvsc_linkstatus_callback()
721 if (indicate->status_buflen < sizeof(speed) || in netvsc_linkstatus_callback()
722 indicate->status_buf_offset < sizeof(*indicate) || in netvsc_linkstatus_callback()
723 data_buflen - RNDIS_HEADER_SIZE < indicate->status_buf_offset || in netvsc_linkstatus_callback()
724 data_buflen - RNDIS_HEADER_SIZE - indicate->status_buf_offset in netvsc_linkstatus_callback()
725 < indicate->status_buflen) { in netvsc_linkstatus_callback()
730 speed = *(u32 *)(data + RNDIS_HEADER_SIZE + indicate->status_buf_offset) / 10000; in netvsc_linkstatus_callback()
736 if (indicate->status != RNDIS_STATUS_NETWORK_CHANGE && in netvsc_linkstatus_callback()
[all …]
|
| /linux-5.19.10/Documentation/devicetree/bindings/cpufreq/ |
| D | ti-cpufreq.txt | 31 2. Which eFuse bits indicate this OPP is available
59 * 0x2 and 0x4 have eFuse bits that indicate if they are available or not
|
| /linux-5.19.10/Documentation/devicetree/bindings/mmc/ |
| D | mmc-card.yaml | 26 Use this to indicate that the mmc-card has a broken hpi
|
| /linux-5.19.10/Documentation/networking/ |
| D | rxrpc.rst | 245 to indicate the terminal message for that call.
252 and control data messages will be set to indicate the context. Receiving
348 This is used to indicate the application's call ID. It's an unsigned long
357 sendmsg, or it can be delivered by recvmsg to indicate a remote abort was
364 This is delivered to a server application to indicate that the final ACK
366 RXRPC_USER_CALL_ID to indicate the call that's now complete.
370 This is delivered to an application to indicate that an ICMP error message
373 indicating the problem, and an RXRPC_USER_CALL_ID will indicate the call
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.
[all …]
|
| D | secid.rst | 9 The secid member in the flow structure is used in LSMs (e.g. SELinux) to indicate
|
| /linux-5.19.10/Documentation/PCI/endpoint/ |
| 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-5.19.10/Documentation/i2c/ |
| D | fault-codes.rst | 18 result for an operation ... it doesn't indicate that anything is wrong
89 Returned by I2C adapters to indicate that the address phase
94 Returned by driver probe() methods to indicate that they
|
12345678910>>...16