Searched full:identify (Results 1 – 25 of 294) sorted by relevance
12345678910>>...12
| /Documentation/devicetree/bindings/leds/ |
| D | leds-powernv.txt | 12 - led-types : Supported LED types (attention/identify/fault) provided
22 led-types = "identify", "fault";
|
| /Documentation/filesystems/xfs/ |
| D | xfs-maintainer-entry-profile.rst | 60 Reviewers should identify themselves with an ``R:`` entry in the kernel
68 The testing lead should identify themselves with an ``M:`` entry in
72 enough detail to identify the person to whom the report should be
75 The bug triagers should identify themselves with a ``B:`` entry in
86 The release manager should identify themselves with an ``M:`` entry in
99 The maintainer for a given LTS release should identify themselves with an
|
| /Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 16 to identify which functions are live is to use a stacktrace.
116 trace, it is strongly recommended that architectures positively identify code
124 There are several ways an architecture may identify kernel code which is deemed
145 and it may not be possible to identify whether such unwinding will be reliable.
148 Architectures which cannot identify when it is reliable to unwind such cases
154 Architectures which can identify when it is reliable to unwind such cases (or
308 reliably identify when the LR or stack value should be used (e.g. using
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-kernel-fadump_enabled | 7 Primarily used to identify whether the FADump is enabled in
|
| /Documentation/networking/devlink/ |
| D | devlink-flash.rst | 73 The ``driver`` attribute and ``fixed`` group identify the specific device
76 is fixed) - ``fixed`` versions should identify the design, not a single
79 ``running`` and ``stored`` firmware versions identify the firmware running
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-sun | 13 So reading the sysfs file, we can identify a physical position
|
| D | sysfs-class-fc | 14 tag to identify traffic sources.
|
| D | sysfs-firmware-sgi_uv | 41 This value can be used to identify the UV system version::
72 This value is used to physically identify a hub within a system.
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | rockchip-mailbox.txt | 17 - #mbox-cells: Common mailbox binding property to identify the number
|
| D | altera-mailbox.txt | 8 - #mbox-cells: Common mailbox binding property to identify the number
|
| /Documentation/devicetree/bindings/thermal/ |
| D | dlg,da9062-thermal.yaml | 16 Junction temperature thermal module uses an interrupt signal to identify
|
| D | imx8mm-thermal.yaml | 48 Number of cells required to uniquely identify the thermal
|
| /Documentation/devicetree/bindings/arm/ |
| D | primecell.yaml | 14 identify the peripheral type, vendor, and revision. This value can be used for
|
| /Documentation/devicetree/bindings/misc/ |
| D | nvidia,tegra186-misc.yaml | 14 registers that can be used to identify a given chip and various strapping
|
| /Documentation/devicetree/bindings/iio/dac/ |
| D | dac.yaml | 25 description: Unique name to identify which channel this is.
|
| /Documentation/devicetree/bindings/iio/temperature/ |
| D | ti,tmp117.yaml | 31 description: Unique name to identify which device this is.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,keystone-irq.txt | 5 The IRQ handler running on HOST OS can identify DSP signal source by
|
| /Documentation/userspace-api/media/v4l/ |
| D | querycap.rst | 31 specific applications to reliably identify the driver.
|
| D | vidioc-dbg-g-chip-info.rst | 13 VIDIOC_DBG_G_CHIP_INFO - Identify the chips on a TV card
61 the PCI or USB bus. Non-zero numbers identify specific parts of the
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-opal.txt | 12 - ibm,opal-id: Refers to a specific bus and used to identify it when calling
|
| /Documentation/devicetree/bindings/fsi/ |
| D | fsi-controller.yaml | 45 Processor index, a global unique chip ID which is used to identify
|
| /Documentation/sound/designs/ |
| D | compress-accel.rst | 36 A new direction SND_COMPRESS_ACCEL is introduced to identify
106 must identify the task to be reused. In both cases, a new seqno value
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | par_io.txt | 34 - gpio-controller : node to identify gpio controllers.
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-get-info.rst | 36 used to identify kernel devices compatible with this specification and to
|
| /Documentation/hwmon/ |
| D | ltc4151.rst | 29 which can be safely used to identify the chip. You will have to instantiate
|
12345678910>>...12