Home
last modified time | relevance | path

Searched full:representation (Results 1 – 25 of 153) sorted by relevance

1234567

/Documentation/ABI/testing/
Dsysfs-kernel-boot_params12 "data" file is the binary representation of struct boot_params.
14 "version" file is the string representation of boot
23 representation of setup_data type. "data" file is the binary
24 representation of setup_data payload.
Dsysfs-fs-fuse26 Contents is ASCII decimal representation of bpf_prog_type_fuse
Dsysfs-secvar34 representation. The data and size can be determined by reading
40 Description: An integer representation of the size of the content of the
/Documentation/ABI/stable/
Dsysfs-bus-firewire17 Hexadecimal string representation of an u64.
69 Decimal string representation.
87 Hexadecimal string representation of an u24.
93 Hexadecimal string representation of an u24.
99 Hexadecimal string representation of an u24.
103 Hexadecimal string representation of an u24.
110 Hexadecimal string representation of an u24.
Dsysfs-kernel-notes4 Description: The /sys/kernel/notes file contains the binary representation
Dsysfs-firmware-opal-elog42 id: An ASCII representation of the ID of the
45 type: An ASCII representation of the type id and
Dsysfs-firmware-opal-dump28 id: An ASCII representation of the dump ID
30 type: An ASCII representation of the type of
/Documentation/trace/rv/
Ddeterministic_automata.rst32 in multiple formats. For example, using a *graphical representation*, using
57 /* enum representation of X (set of states) to be used as index */
66 /* enum representation of E (set of events) to be used as index */
109 The Graphviz open-source tool can produce the graphical representation
143 in the example above and automatically convert it to the C representation
148 representation (previously shown) in the 'wip.h' file::
179 For the C representation in kernel, see::
Dda_monitor_synthesis.rst8 The formal representation needs to be then *synthesized* into a *monitor*
50 the DOT format into the C representation [1] and creating the skeleton of
90 the 'type' argument is the data type used by dot2k on the representation of
141 from one representation to another, see::
/Documentation/devicetree/bindings/crypto/
Dmv_cesa.txt10 but this representation is deprecated and marvell,crypto-srams should
12 - reg-names: "regs". Can contain an "sram" entry, but this representation
Dmarvell-cesa.txt14 but this representation is deprecated and marvell,crypto-srams should
16 - reg-names: "regs". Can contain an "sram" entry, but this representation
/Documentation/devicetree/bindings/usb/
Dusb-device.yaml34 The textual representation of VID and PID shall be in lower case
58 representation of an interface-node unit address for configuration 1.
66 number. The textual representation of VID, PID, CN and IN shall be
/Documentation/devicetree/bindings/pci/
Dmobiveil-pcie.txt7 - #address-cells: Address representation for root ports, set to <3>
8 - #size-cells: Size representation for root ports, set to <2>
/Documentation/userspace-api/media/v4l/
Dhsv-formats.rst10 in a geometrical representation. The colors are mapped into a
Dpixfmt-y12i.rst26 **Bit-packed representation.**
Dpixfmt-cnf4.rst23 **Bit-packed representation.**
/Documentation/devicetree/bindings/reserved-memory/
Dnvidia,tegra210-emc-table.yaml13 description: On Tegra210, firmware passes a binary representation of the
/Documentation/devicetree/bindings/virtio/
Dvirtio-device.yaml22 representation of ID shall be in lower case hexadecimal with leading
/Documentation/arch/powerpc/
Dassociativity.rst102 "ibm,lookup-index-table" helps in having a compact representation of distance matrix.
104 With "ibm,lookup-index-table" we can achieve a compact representation of
/Documentation/devicetree/bindings/net/
Dmarvell,mvusb.yaml18 having a device tree representation of the device. But in order to use it with
/Documentation/userspace-api/media/mediactl/
Dmedia-controller-model.rst20 - An **interface** is a graph representation of a Linux Kernel
/Documentation/devicetree/bindings/mtd/
Dnand-controller.yaml16 children nodes of the NAND controller. This representation should be
/Documentation/networking/
Dphy-link-topology.rst11 The PHY link topology representation in the networking stack aims at representing
103 The whole point of having a topology representation is to assign the phyindex
/Documentation/admin-guide/device-mapper/
Dswitch.rst12 that would allow for a compact representation of the mapping such as
65 large for us). This is a much denser representation than the dm table
/Documentation/devicetree/bindings/memory-controllers/ddr/
Djedec,lpddr-props.yaml25 formatted in lower case hexadecimal representation with leading zeroes.

1234567