Searched full:determine (Results 1 – 25 of 379) sorted by relevance
12345678910>>...16
| /Documentation/pcmcia/ |
| D | devicetable.rst | 26 You can determine the hash of the product ID strings by catting the file
35 to determine the crc32 hash. Simply pass the string you want to evaluate
|
| /Documentation/ABI/testing/ |
| D | dell-smbios-wmi | 13 first determine the minimum size of the calling interface
19 To determine the size of the buffer read() a u64 dword from
|
| D | sysfs-class-thermal | 174 to determine a hotspot temperature based off the sensor's
175 raw readings. It is up to the device driver to determine
183 to determine a hotspot temperature based off the sensor's
184 raw readings. It is up to the device driver to determine
|
| D | sysfs-class-regulator | 23 'unknown' means software cannot determine the state, or
27 or microamps to determine configured regulator output levels.
101 NOTE: This value should not be used to determine the regulator
116 NOTE: This value should not be used to determine the regulator
140 NOTE: This value should not be used to determine the regulator
143 attribute may be available to determine the actual mode.
371 'unknown' means software cannot determine the state, or
|
| /Documentation/devicetree/bindings/sound/ |
| D | cs35l36.txt | 32 - cirrus,multi-amp-mode : Boolean to determine if there are more than
43 - cirrus,amp-pcm-inv : Boolean to determine Amplifier will invert incoming
46 - cirrus,imon-pol-inv : Boolean to determine Amplifier will invert the
49 - cirrus,vmon-pol-inv : Boolean to determine Amplifier will invert the
|
| D | cs35l35.txt | 23 - cirrus,stereo-config : Boolean to determine if there are 2 AMPs for a
51 - cirrus,bst-pdn-fet-on : Boolean to determine if the Boost PDN control
66 - cirrus,amp-gain-zc : Boolean to determine if to use Amplifier gain-change
|
| /Documentation/process/ |
| D | cve.rst | 74 assess the validity and scope of a reported vulnerability and determine
101 determine, it is not up to the CVE assignment team. Please do not
102 contact us to attempt to determine the applicability of any specific
110 of the kernel that you use, so there is no way for us to determine if a
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | microchip,wilc1000.yaml | 35 description: Used by wilc1000-spi to determine the GPIO line
44 description: Used by wilc1000-spi to determine the GPIO line
|
| /Documentation/trace/ |
| D | sys-t.rst | 34 configfs gets a few additional attributes, which determine per-source
55 ts_interval and clocksync_interval determine how much time in milliseconds
|
| /Documentation/driver-api/pldmfw/ |
| D | index.rst | 30 operations to determine if the firmware file is a match for the device. If
61 2. Scan through the records and determine if the device matches any record
|
| /Documentation/bpf/ |
| D | map_bloom_filter.rst | 73 The ``bpf_map_peek_elem()`` helper is used to determine whether
100 A userspace program can determine the presence of ``value`` in a bloom
123 This snippet shows how to determine presence of a value in a bloom
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | firmware.txt | 11 Device drivers can search this string to determine if the
|
| /Documentation/power/regulator/ |
| D | consumer.rst | 48 A consumer can determine if a regulator is enabled by calling::
98 regulator is enabled or disabled and should NOT be used to determine regulator
100 determine the regulator physical output voltage.
130 is enabled or disabled and should not be used to determine regulator current
|
| D | design.rst | 13 - It is not possible to automatically determine the power configuration
|
| /Documentation/devicetree/bindings/clock/ |
| D | armada3700-xtal-clock.txt | 3 Marvell Armada 37xx SoCs allow to determine the xtal clock frequencies by
|
| D | moxa,moxart-clock.txt | 7 MOXA ART SoCs allow to determine PLL output and APB frequencies
|
| /Documentation/misc-devices/ |
| D | xilinx_sdfec.rst | 105 performed to configure and activate the SD-FEC core and determine the
109 - Determine Configuration
125 Determine Configuration
128 Determine the configuration of the SD-FEC core by using the ioctl
152 … calculate the size of shared LPDC code tables. This allows the user to determine the shared table…
|
| /Documentation/core-api/ |
| D | union_find.rst | 20 Find: Determine which set a particular element belongs to, usually by
84 This operation is mainly used to determine whether two nodes belong to the same
|
| /Documentation/filesystems/xfs/ |
| D | xfs-self-describing-metadata.rst | 26 determine the root cause of a corruption problem, but it is still mainly a
58 quickly determine if the metadata is intact and can be ignored for the purpose
108 determine the scope of the corruption. For example, if we have a extent btree
114 determine the scope of the problem.
131 For example, we can determine whether a metadata object is supposed to be free
245 whether the magic number can be used to determine the format of the block. In
|
| /Documentation/devicetree/bindings/hwinfo/ |
| D | samsung,exynos-chipid.yaml | 36 to determine the ASV bin of an SoC if respective information
|
| /Documentation/admin-guide/perf/ |
| D | arm_dsu_pmu.rst | 15 registers. There is no way for the driver to determine if the other events
|
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api-intro.rst | 15 cropping target determine the area actually sampled. The sink is an
|
| D | streaming-par.rst | 22 Finally these ioctls can be used to determine the number of buffers used
|
| /Documentation/driver-api/mmc/ |
| D | mmc-tools.rst | 16 - Determine the eMMC writeprotect status.
|
| /Documentation/devicetree/bindings/gnss/ |
| D | mediatek.yaml | 38 description: GPIO used to determine device position fix state, pin names
|
12345678910>>...16