Searched full:treated (Results 1 – 25 of 150) sorted by relevance
123456
| /Documentation/admin-guide/perf/ |
| D | arm-cmn.rst | 31 are treated as the same type (0xa), and the common event templates are
34 * The cycle counter is treated as a synthetic event belonging to the DTC
51 traffic. Watchpoints are treated as a synthetic event type, and like PMU
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-aemif.txt | 105 Minimum value is 1 (0 treated as 1).
110 Minimum value is 1 (0 treated as 1).
117 Minimum value is 1 (0 treated as 1).
122 Minimum value is 1 (0 treated as 1).
127 Minimum value is 1 (0 treated as 1).
134 Minimum value is 1 (0 treated as 1).
|
| /Documentation/devicetree/bindings/pci/ |
| D | fsl,pci.txt | 13 property. The property itself is treated as a boolean.
|
| /Documentation/devicetree/bindings/regulator/ |
| D | vexpress.txt | 22 the device is treated as fixed (or rather "read-only") regulator.
|
| /Documentation/devicetree/bindings/sound/ |
| D | wlf,arizona.yaml | 53 are supplied the additional outputs will be treated as stereo.
85 treated as default setting.
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | kontron,sl28-vpd.yaml | 34 argument of the phandle will be treated as an offset.
|
| D | onie,tlv-layout.yaml | 44 argument of the phandle will be treated as an offset.
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm4908-partitions.yaml | 11 for regular booting, the other is treated as fallback.
|
| D | linksys,ns-partitions.yaml | 11 firmware partitions. One is used for regular booting, the other is treated as
|
| /Documentation/filesystems/ext4/ |
| D | inlinedata.rst | 33 i_block and EA space are treated as separate dirent blocks; directory
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_decoder_api.rst | 29 Practically the decoders seem to be treated differently. The application typically
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-trigger-pattern.txt | 9 the tuple with duration less than dimming interval (50ms) is treated as a step
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-intel-ifs | 48 The number written treated as the 2 digit suffix in the following file name:
|
| /Documentation/devicetree/bindings/pmem/ |
| D | pmem-region.txt | 28 each address range will be treated as though it was specified
|
| /Documentation/devicetree/bindings/thermal/ |
| D | ti_soc_thermal.txt | 24 be treated as an IRQ;
|
| /Documentation/devicetree/bindings/iio/accel/ |
| D | bosch,bma255.yaml | 55 always treated as INT2.
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | sony,imx290.yaml | 23 is treated the same as this as it was the original compatible string.
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 29 correspond to any particular physical configuration of it, but can be treated as
|
| /Documentation/arch/x86/ |
| D | tlb.rst | 55 flushes. THP is treated exactly the same as normal memory.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | omap-usb-host.txt | 16 from 1 to 3. If the port mode is not specified, that port is treated
|
| /Documentation/core-api/ |
| D | entry.rst | 206 in kernel mode (code patching). From user-space, they are treated like
207 interrupts, while from kernel mode they are treated like NMIs.
|
| /Documentation/devicetree/bindings/iio/addac/ |
| D | adi,ad74413r.yaml | 101 When not configured as a comparator, the GPO will be treated as an
|
| /Documentation/userspace-api/gpio/ |
| D | gpio-get-linehandle-ioctl.rst | 105 Bias is treated as best effort to allow userspace to apply the same
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-dust.rst | 30 configured "bad blocks" will be treated as bad, or bypassed.
188 will be treated as "bad" without having to issue I/O to the device,
|
| /Documentation/scheduler/ |
| D | sched-domains.rst | 30 is treated as one entity. The load of a group is defined as the sum of the
|
123456