Searched full:typical (Results 1 – 25 of 231) sorted by relevance
12345678910
| /Documentation/devicetree/bindings/display/panel/ |
| D | panel-timing.yaml | 56 Timing can be specified either as a typical value or as a tuple
78 description: typical number of pixels
90 description: typical number of pixels
102 description: typical number of pixels
114 description: typical number of lines
126 description: typical number of lines
138 description: typical number of lines
|
| /Documentation/userspace-api/media/ |
| D | intro.rst | 12 A typical media device hardware is shown at :ref:`typical_media_device`.
20 Typical Media Device
|
| /Documentation/i2c/ |
| D | functionality.rst | 69 function callback ``functionality``. Typical implementations are given
72 A typical SMBus-only adapter would list all the SMBus transactions it
82 A typical full-I2C adapter would use the following (from the i2c-pxa
104 check whether the needed functionality is present. The typical way to do
|
| /Documentation/mm/ |
| D | overcommit-accounting.rst | 9 space are refused. Used for a typical system. It ensures a
45 largest size you think you will need. For typical stack usage this does
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | sophgo,cv1800-pinctrl.yaml | 71 description: typical current when output high level.
74 description: typical threshold for schmitt trigger.
|
| /Documentation/ABI/testing/ |
| D | debugfs-iio-backend | 11 Directly access the registers of backend Y. Typical usage is:
|
| D | sysfs-bus-iio-mpu6050 | 8 is a 3x3 unitary matrix. A typical mounting matrix would look like
|
| D | sysfs-class-power-wilco | 11 typical battery usage pattern.
|
| D | procfs-smaps_rollup | 17 Typical output looks like this::
|
| D | sysfs-devices-platform-docg3 | 35 Typical values are:
|
| /Documentation/virt/gunyah/ |
| D | message-queue.rst | 18 The diagram below shows how message queue works. A typical configuration
31 a. gunyah_msgq_send() has PUSH flag. This is a typical case when the message
|
| /Documentation/devicetree/bindings/iio/light/ |
| D | rohm,bu27034anuc.yaml | 14 capable of detecting a very wide range of illuminance. Typical application
|
| D | rohm,bu27008.yaml | 16 selected to be simultaneously measured. Typical application is adjusting
|
| D | rohm,bu27010.yaml | 17 Typical application is adjusting LCD/OLED backlight of TVs, mobile phones
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | restart-handler.yaml | 23 128:: Typical, default restart handler; use if no other restart handler
|
| /Documentation/litmus-tests/rcu/ |
| D | RCU+sync+free.litmus | 10 * This is a typical pattern of RCU usage, where the write before the grace
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | mediatek,mt7921s-bluetooth.yaml | 33 An active-low reset line for the Bluetooth core; on typical M.2
|
| /Documentation/devicetree/bindings/rtc/ |
| D | faraday,ftrtc010.yaml | 37 clocks here, like Cortina who chose 32768 Hz (a typical low-power clock).
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | amd,sbrmi.yaml | 17 Mailbox Service Request and resembles a typical 8-pin remote power
|
| D | amd,sbtsi.yaml | 18 and resembles a typical 8-pin remote temperature sensor's I2C interface
|
| D | adi,ltc4282.yaml | 58 10% and 15% settings with the actual min, typical and max tolerances.
70 10% and 15% settings with the actual min, typical and max tolerances.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | fsl,imx8qxp-csr.yaml | 16 to a mix of standalone hardware devices within that subsystem. One typical
18 by phandle, and the other typical use-case is that the operating system
|
| D | syscon-common.yaml | 12 represent as any specific type of device. The typical use-case is
|
| /Documentation/driver-api/iio/ |
| D | hw-consumer.rst | 22 A typical IIO HW consumer setup looks like this::
|
| /Documentation/hwmon/ |
| D | sbtsi_temp.rst | 38 and physical interface of a typical 8-pin remote temperature sensor (RTS) on
|
12345678910