Searched full:describing (Results 1 – 25 of 239) sorted by relevance
12345678910
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-mt6797.txt | 10 - reg-names: An array of strings describing the "reg" entries. Must
52 - mediatek,tdsel: An integer describing the steps for output level shifter
55 - mediatek,rdsel: An integer describing the steps for input level shifter
58 - mediatek,pull-up-adv: An integer describing the code R1R0 as 0, 1, 2
60 - mediatek,pull-down-adv: An integer describing the code R1R0 as 0, 1, 2,
|
| D | berlin,pinctrl.txt | 30 - groups: a list of strings describing the group names.
31 - function: a string describing the function used to mux the groups.
|
| /Documentation/devicetree/bindings/media/ |
| D | renesas,vin.txt | 48 - port - sub-node describing a single endpoint connected to the VIN
74 - port@0 - sub-node describing a single endpoint connected to the VIN
76 Describing more than one endpoint in port@0 is invalid. Only VIN
82 - port@1 - sub-nodes describing one or more endpoints connected to
86 - endpoint@0 - sub-node describing the endpoint connected to CSI20
87 - endpoint@1 - sub-node describing the endpoint connected to CSI21
88 - endpoint@2 - sub-node describing the endpoint connected to CSI40
89 - endpoint@3 - sub-node describing the endpoint connected to CSI41
|
| /Documentation/hwmon/ |
| D | sch5636.rst | 35 An application note describing the Theseus' registers, as well as an
36 application note describing the protocol for communicating with the
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-mm-lantiq.txt | 7 The node describing the memory mapped GPIOs needs to be a child of the node
8 describing the "lantiq,localbus".
|
| /Documentation/devicetree/bindings/net/can/ |
| D | mpc5xxx-mscan.txt | 12 - fsl,mscan-clock-source : a string describing the clock source. Valid values
23 - fsl,mscan-clock-source : a string describing the clock source. Valid values
|
| /Documentation/devicetree/bindings/pci/ |
| D | aardvark-pci.txt | 5 The Device Tree node describing an Aardvark PCIe controller must
23 In addition, the Device Tree describing an Aardvark PCIe controller
|
| D | pci-msi.txt | 1 This document describes the generic device tree binding for describing the
36 * rid-base is a single cell describing the first RID matched by the entry.
40 * msi-base is an msi-specifier describing the msi-specifier produced for the
43 * length is a single cell describing how many consecutive RIDs are matched
|
| /Documentation/devicetree/bindings/timer/ |
| D | ezchip,nps400-timer1.txt | 8 - clocks : Must contain a single entry describing the clock input
|
| D | ezchip,nps400-timer0.txt | 9 - clocks : Must contain a single entry describing the clock input
|
| D | mrvl,mmp-timer.txt | 9 - clocks : Should contain a single entry describing the clock input.
|
| /Documentation/devicetree/bindings/display/ |
| D | arm,malidp.txt | 27 - arm,malidp-output-port-lines: Array of u8 values describing the number
36 - memory-region: phandle to a node describing memory (see
|
| /Documentation/devicetree/bindings/arm/ |
| D | vexpress.txt | 87 The nodes describing configuration controllers must define
93 and children describing available functions.
102 property, describing physical location of the children nodes:
110 - when describing tiles consisting more than one DCC, its number
149 The tile description should define a "smb" node, describing the
|
| D | spe-pmu.txt | 13 the arm,gic-v3 binding for details on describing a PPI partition.
|
| /Documentation/virt/kvm/devices/ |
| D | vcpu.txt | 23 A value describing the PMUv3 (Performance Monitor Unit v3) overflow interrupt
50 A value describing the architected timer interrupt number when connected to an
|
| D | s390_flic.txt | 63 describing the adapter to register:
115 AIS capability is enabled. Takes a kvm_s390_ais_req describing:
142 a kvm_s390_ais_all describing:
|
| /Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu-v3.txt | 18 - interrupts : Non-secure interrupt list describing the wired
39 describing a single stream ID. All possible stream
|
| /Documentation/ABI/testing/ |
| D | sysfs-class | 6 subdirectories describing individual classes of devices
|
| /Documentation/devicetree/bindings/mtd/ |
| D | atmel-dataflash.txt | 6 The device tree may optionally contain sub-nodes describing partitions of the
|
| /Documentation/filesystems/ |
| D | xfs-self-describing-metadata.txt | 1 XFS Self Describing Metadata
36 Self Describing Metadata
57 self describing metadata.
59 The first, fundamental requirement of self describing metadata is that the
75 As a primary concern, self describing metadata needs some form of overall
92 Self describing metadata needs to contain enough information so that the
119 Self describing metadata also needs to contain some indication of when it was
147 Validation of self-describing metadata takes place at runtime in two places:
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | srio-rmu.txt | 62 binding document describing the node's interrupt parent.
92 binding document describing the node's interrupt parent.
122 binding document describing the node's interrupt parent.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | digicolor-ic.txt | 11 - syscon: A phandle to the syscon node describing UC registers
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | exynos-srom.txt | 10 extra properties, describing the bus behind it, should be specified as below:
24 properties, describing configuration of the relevant SROM bank:
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | vexpress.txt | 16 - label : string describing the monitored value
|
| /Documentation/devicetree/bindings/i3c/ |
| D | i3c.txt | 16 The node describing an I3C bus should be named i3c-master.
78 Another use case for describing an I3C device in the device tree is when this
84 where device-type is describing the type of device connected on the bus
|
12345678910