| /linux-4.4.14/crypto/ |
| D | ansi_cprng.c | 48 unsigned char DT[DEFAULT_BLK_SZ]; member
96 hexdump("Input DT: ", ctx->DT, DEFAULT_BLK_SZ); in _get_more_prng_bytes()
111 memcpy(tmp, ctx->DT, DEFAULT_BLK_SZ); in _get_more_prng_bytes()
169 ctx->DT[i] += 1; in _get_more_prng_bytes()
170 if (ctx->DT[i] != 0) in _get_more_prng_bytes()
177 hexdump("Output DT: ", ctx->DT, DEFAULT_BLK_SZ); in _get_more_prng_bytes()
283 const unsigned char *V, const unsigned char *DT) in reset_prng_context() argument
301 if (DT) in reset_prng_context()
302 memcpy(ctx->DT, DT, DEFAULT_BLK_SZ); in reset_prng_context()
304 memset(ctx->DT, 0, DEFAULT_BLK_SZ); in reset_prng_context()
|
| /linux-4.4.14/Documentation/devicetree/bindings/cpufreq/ |
| D | arm_big_little_dt.txt | 1 Generic ARM big LITTLE cpufreq driver's DT glue
4 This is DT specific glue layer for generic cpufreq driver for big LITTLE
10 FIXME: Cpus should boot in the order specified in DT and all cpus for a cluster
11 must be present contiguously. Generic DT driver will check only node 'x' for
|
| D | cpufreq-dt.txt | 3 It is a generic DT based cpufreq driver for frequency management. It supports
15 details. OPPs *must* be supplied either via DT, i.e. this property, or
|
| /linux-4.4.14/drivers/staging/board/ |
| D | TODO | 1 * replace platform device code with DT nodes once the driver supports DT
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | submitting-patches.txt | 2 Submitting devicetree (DT) binding patches
15 and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
16 all of the DT maintainers.
22 previously documented in the corresponding DT binding text file
27 ("checkpatch: add DT compatible string documentation checks"). ]
|
| D | ABI.txt | 2 Devicetree (DT) ABI
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | usage-model.txt | 13 The "Open Firmware Device Tree", or simply Device Tree (DT), is a data
19 Structurally, the DT is a tree, or acyclic graph with named nodes, and
41 The DT was originally created by Open Firmware as part of the
53 and 64-bit support, the decision was made to require DT support on all
55 Firmware. To do this, a DT representation called the Flattened Device
59 Device Tree Binary (dtb) and to modify a dtb at boot time. DT was
62 existing non-DT aware firmware.
67 out of mainline (nios) have some level of DT support.
76 The most important thing to understand is that the DT is simply a data
90 Linux uses DT data for three major purposes:
[all …]
|
| D | 00-INDEX | 12 - How Linux uses DT and what DT aims to solve.
|
| D | changesets.txt | 1 A DT changeset is a method which allows one to apply changes
17 2. A number of DT tree change calls, of_changeset_attach_node(),
|
| D | of_unittest.txt | 40 is used to compile the DT source file (testcases.dts) into a binary blob
41 (testcases.dtb), also referred as flattened DT.
|
| D | booting-without-of.txt | 20 II - The DT block format
71 May 24, 2005: Rev 0.3 - Precise that DT block has to be in RAM
74 for the DT block (version 16 needs kernel
300 Similar to the arch/arm case (b), a DT-aware bootloader is expected to
313 DT block. In this case, Linux will look for a builtin DTB, selected via
319 II - The DT block format
348 u32 totalsize; /* total size of DT block */
363 u32 size_dt_struct; /* size of the DT structure block */
391 This is the total size of the DT block including the header. The
392 "DT" block should enclose all data structures defined in this
[all …]
|
| D | overlay-notes.txt | 130 Using the non-phandle based target method allows one to use a base DT which does
|
| /linux-4.4.14/Documentation/arm64/ |
| D | arm-acpi.txt | 38 while DT explicitly does not support this. For hardware vendors, being
47 as for RAS) which are currently used in production systems. DT does not.
48 Such bindings could be defined in DT at some point, but doing so means ARM
54 both DT and ACPI if they want to support multiple operating systems. And,
78 in place. DT does exactly what Linux needs it to when working with vertically
80 server vendors need. Linux could potentially get there with DT, but doing so
82 the hardware vendors need, Microsoft won’t collaborate on DT, and hardware
110 exclusive with DT support at compile time.
115 Regardless of whether DT or ACPI is used, the kernel must always be capable
126 When an ARMv8 system boots, it can either have DT information, ACPI tables,
[all …]
|
| D | booting.txt | 188 - The DT or ACPI tables must describe a GICv3 interrupt controller.
196 - The DT or ACPI tables must describe a GICv2 interrupt controller.
|
| /linux-4.4.14/drivers/staging/comedi/drivers/ |
| D | dt3000.c | 730 { PCI_VDEVICE(DT, 0x0022), BOARD_DT3001 },
731 { PCI_VDEVICE(DT, 0x0023), BOARD_DT3002 },
732 { PCI_VDEVICE(DT, 0x0024), BOARD_DT3003 },
733 { PCI_VDEVICE(DT, 0x0025), BOARD_DT3004 },
734 { PCI_VDEVICE(DT, 0x0026), BOARD_DT3005 },
735 { PCI_VDEVICE(DT, 0x0027), BOARD_DT3001_PGL },
736 { PCI_VDEVICE(DT, 0x0028), BOARD_DT3003_PGL },
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/xilinx/ |
| D | xlnx,video.txt | 9 and IP core specific documentation, xlnx,v-*.txt, in this directory. The DT
22 - ports: Video port, using the DT bindings defined in ../video-interfaces.txt.
|
| D | xlnx,v-tpg.txt | 21 - port: Video port, using the DT bindings defined in ../video-interfaces.txt.
|
| D | video.txt | 1 DT bindings for Xilinx video IP cores
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | ibmpowernv | 20 All the nodes in the DT appear under "/ibm,opal/sensors" and each valid node in
21 the DT maps to an attribute file in 'sysfs'. The node exports unique 'sensor-id'
|
| D | vexpress | 33 Tree passed to the kernel. Details of the DT binding for them can be found
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | cs4271.txt | 1 Cirrus Logic CS4271 DT bindings
30 in the MODE2 register. This workaround can be enabled with this DT
|
| D | pcm1792a.txt | 1 Texas Instruments pcm1792a DT bindings
|
| D | mrvl,pxa2xx-pcm.txt | 1 DT bindings for ARM PXA2xx PCM platform driver
|
| D | widgets.txt | 5 Each entry is a pair of strings in DT:
|
| D | imx-audio-spdif.txt | 25 * Note: At least one of these two properties should be set in the DT binding.
|
| /linux-4.4.14/Documentation/devicetree/bindings/pci/ |
| D | samsung,exynos5440-pcie.txt | 15 SoC specific DT Entry:
57 Board specific DT Entry:
|
| D | pci-keystone.txt | 9 for the details of Designware DT bindings. Additional properties are
60 Designware DT Properties not applicable for Keystone PCI
|
| D | xilinx-pcie.txt | 1 * Xilinx AXI PCIe Root Port Bridge DT description
34 created a interrupt controller node to support 'interrupt-map' DT
|
| D | xgene-pci.txt | 28 SoC specific DT Entry:
54 Board specific DT Entry:
|
| D | spear13xx-pcie.txt | 1 SPEAr13XX PCIe DT detail:
|
| D | hisilicon-pcie.txt | 1 HiSilicon PCIe host bridge DT description
|
| D | rcar-pci.txt | 25 SoC specific DT Entry:
|
| D | mvebu-pci.txt | 43 * t is the type of the MBus window (as defined by the standard PCI DT
|
| D | nvidia,tegra20-pcie.txt | 220 enumeration and therefore don't need corresponding device nodes in DT. However
|
| /linux-4.4.14/Documentation/devicetree/bindings/usb/ |
| D | generic.txt | 7 via DT, USB controllers should default to their maximum
12 passed via DT, USB DRD controllers should default to
|
| D | dwc3-st.txt | 33 example below. The DT binding details of dwc3 can be found in:
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/ |
| D | s5p-mfc.txt | 35 SoC specific DT entry:
46 Board specific DT entry:
|
| D | stih407-c8sectpfe.txt | 37 - i2c-bus : phandle to the I2C bus DT node which the demodulators & tuners on this tsin channel are…
51 /* stih410 SoC b2120 + b2004a + stv0367-pll(NIMB) + stv0367-tda18212 (NIMA) DT example) */
|
| D | ti,omap3isp.txt | 4 The DT definitions can be found in include/dt-bindings/media/omap3-isp.h.
|
| D | video-interfaces.txt | 10 SoC internal blocks are described by DT nodes, placed similarly to other SoC
|
| /linux-4.4.14/Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 15 specifier - a list of DT cells that represents the reset signal within the
23 the DT node of each affected HW block, since if activated, an unrelated block
24 may be reset. Instead, reset signals should be represented in the DT node
|
| /linux-4.4.14/drivers/staging/emxx_udc/ |
| D | TODO | 3 * DT bindings
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/exynos/ |
| D | exynos5433-decon.txt | 34 SoC specific DT entry:
61 Board specific DT entry:
|
| D | exynos7-decon.txt | 45 SoC specific DT entry:
62 Board specific DT entry:
|
| D | samsung-fimd.txt | 90 SoC specific DT entry:
104 Board specific DT entry:
|
| D | exynos-mic.txt | 24 SoC specific DT entry:
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | shdma.txt | 6 SHDMA DT nodes to be placed under a DMA multiplexer node. All such compatible
8 descriptors. Therefore respective DMA DT bindings can also all be placed in the
|
| D | mv-xor.txt | 10 The DT node must also contains sub-nodes for each XOR channel that the
|
| /linux-4.4.14/drivers/staging/wilc1000/ |
| D | TODO | 10 into run-time options that are read from DT
|
| /linux-4.4.14/Documentation/devicetree/bindings/phy/ |
| D | st-spear-miphy.txt | 1 ST SPEAr miphy DT details
|
| D | ti-phy.txt | 1 TI PHY: DT DOCUMENTATION FOR PHYs in TI PLATFORMs
|
| D | samsung-phy.txt | 84 Refer to DT bindings documentation of particular PHY consumer devices for more
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
| D | dra7-atl.txt | 14 To be able to integrate the ATL clocks with DT clock tree.
17 for the DT clock tree, the IP driver is needed to handle the actual configuration
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ux500/ |
| D | power_domain.txt | 7 and use the corresponding DT bindings.
|
| /linux-4.4.14/Documentation/arm/keystone/ |
| D | knav-qmss.txt | 26 DT documentation is available at
34 accumulator channels defined in DTS (example in DT documentation) to monitor
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | renesas,irqc.txt | 1 DT bindings for the R-Mobile/R-Car interrupt controller
|
| D | renesas,intc-irqpin.txt | 1 DT bindings for the R-/SH-Mobile irqpin controller
|
| /linux-4.4.14/Documentation/devicetree/bindings/pwm/ |
| D | pwm-tipwmss.txt | 16 Also child nodes should also populated under PWMSS DT node.
|
| /linux-4.4.14/drivers/cpufreq/ |
| D | Kconfig.arm | 14 tristate "Generic probing via DT for ARM big LITTLE CPUfreq driver"
17 This enables probing via DT for Generic CPUfreq driver for ARM
18 big.LITTLE platform. This gets frequency tables from DT.
|
| D | Kconfig | 189 tristate "Generic DT based cpufreq driver"
195 This adds a generic DT based cpufreq driver for frequency management.
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | hisi504-nand.txt | 1 Hisilicon Hip04 Soc NAND controller DT binding
|
| D | pxa3xx-nand.txt | 1 PXA3xx NAND DT bindings
|
| D | jedec,spi-nor.txt | 7 manufacturer and name of the chip. Bear in mind the DT binding
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/omap/ |
| D | prcm.txt | 4 a DT hierarchy. Each TI SoC can have multiple PRCM entities listed for it,
|
| /linux-4.4.14/drivers/mtd/nand/ |
| D | denali_dt.c | 63 denali->platform = DT; in denali_dt_probe()
|
| D | denali.h | 450 #define DT 3 macro
|
| D | Kconfig | 56 tristate "Support Denali NAND controller as a DT device"
61 controller as a DT device.
|
| /linux-4.4.14/Documentation/devicetree/bindings/misc/ |
| D | ifm-csi.txt | 10 - ifm,csi-clk-handle: the phandle to a node in the DT describing the sensor
|
| /linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
| D | tmio_mmc.txt | 7 their own platform data or from their DT information. In the latter case all
|
| /linux-4.4.14/drivers/gpu/drm/msm/ |
| D | NOTES | 70 (ie. like DT super-node.. but I don't have any snapdragon hw yet that
71 is using DT).
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/ |
| D | edt-ft5x06.txt | 13 that a distinction can be added if necessary without changing the DT
|
| /linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/ |
| D | renesas-memory-controllers.txt | 1 DT bindings for Renesas R-Mobile and SH-Mobile memory controllers
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/ |
| D | rotary-encoder.txt | 1 Rotary encoder DT bindings
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/rockchip/ |
| D | rockchip-vop.txt | 36 SoC specific DT entry:
|
| /linux-4.4.14/Documentation/acpi/ |
| D | enumeration.txt | 376 identification string in the Device Tree (DT) namespace, especially if that ID
383 Section 6.1.2 of ACPI 6.0 for details) and the DT namespace is not one of them.
389 The special DT namespace link device ID, PRP0001, provides a means to use the
390 existing DT-compatible device identification in ACPI and to satisfy the above
394 property to identify the corresponding device in analogy with the original DT
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | at91-foxg20.dts | 4 * Based on DT files for at91sam9g20ek evaluation board (AT91SAM9G20 SoC)
|
| D | exynos4210-origen.dts | 253 * DT-based regulator lookup yet.
|
| D | armada-370-rd.dts | 50 * DT-capable, U-Boot bootloaders provided by Marvell. Some earlier
|
| D | armada-xp-db.dts | 52 * DT-capable, U-Boot bootloaders provided by Marvell. Some earlier
|
| D | armada-370-db.dts | 52 * DT-capable, U-Boot bootloaders provided by Marvell. Some earlier
|
| D | armada-xp-gp.dts | 52 * DT-capable, U-Boot bootloaders provided by Marvell. Some earlier
|
| D | exynos4210-trats.dts | 418 * DT-based regulator lookup yet.
|
| D | dm816x.dtsi | 56 * it will not bring real advantage to represent that in DT
|
| D | armada-xp-synology-ds414.dts | 46 * The 0xf1000000 is the default used by the recent, DT-capable, U-Boot
|
| D | armada-370-synology-ds213j.dts | 46 * The 0xf1000000 is the default used by the recent, DT-capable, U-Boot
|
| D | tegra30-cardhu.dtsi | 5 * This file contains common DT entry for all fab version of Cardhu.
|
| D | am57xx-beagle-x15.dts | 718 * board's DT.
|
| D | omap3.dtsi | 77 * Since it will not bring real advantage to represent that in DT for
|
| D | am33xx.dtsi | 89 * it will not bring real advantage to represent that in DT
|
| D | exynos5250.dtsi | 162 * value from DT.
|
| D | omap4.dtsi | 111 * Since it will not bring real advantage to represent that in DT for
|
| D | omap5.dtsi | 126 * Since it will not bring real advantage to represent that in DT for
|
| D | dra7.dtsi | 90 * Since it will not bring real advantage to represent that in DT for
|
| /linux-4.4.14/Documentation/devicetree/bindings/opp/ |
| D | opp.txt | 45 phandle to a OPP table in their DT node. The OPP core will use this phandle to
101 regulators are specified in device's DT node.
111 regulators are specified in device's DT node. If this property isn't required
|
| /linux-4.4.14/Documentation/arm/ |
| D | README | 188 For platforms that support device tree (DT), the machine selection is
200 Note: Please do not register a machine type for DT-only platforms. If your
201 platform is DT-only, you do not need a registered machine type.
|
| D | uefi.txt | 40 When booting in UEFI mode, the stub deletes any memory nodes from a provided DT.
|
| D | Booting | 61 New boot loaders: MANDATORY except for DT-only platforms
70 For DT-only platforms, the machine type will be determined by device
|
| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | pwm-regulator.txt | 8 provided via DT. Limitations are that the regulator can
|
| /linux-4.4.14/arch/arc/boot/dts/ |
| D | axc003.dtsi | 76 * DT "invisible" DW APB GPIO block, configured to simply pass thru
|
| /linux-4.4.14/Documentation/gpio/ |
| D | board.txt | 66 ACPI also supports function names for GPIOs in a similar fashion to DT.
67 The above DT example can be converted to an equivalent ACPI description
|
| D | gpio-legacy.txt | 474 subsystem. There are two ways of doing it currently: with or without DT.
476 For with DT support refer to Documentation/devicetree/bindings/gpio/gpio.txt.
478 For non-DT support, user can call gpiochip_add_pin_range() with appropriate
|
| /linux-4.4.14/drivers/cpuidle/ |
| D | Kconfig.arm | 10 at run-time through DT nodes. The CPUidle suspend backend is
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/ |
| D | renesas,sysc-rmobile.txt | 1 DT bindings for the Renesas R-Mobile System Controller
|
| /linux-4.4.14/Documentation/w1/masters/ |
| D | omap-hdq | 50 setting "ti,mode" property to "1w" in DT (see
|
| /linux-4.4.14/Documentation/devicetree/bindings/edac/ |
| D | apm-xgene-edac.txt | 11 The following section describes the EDAC DT node binding.
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | marvell,berlin.txt | 60 chip control registers, so there should be a single DT node only providing the
|
| D | coresight.txt | 36 layout using the generic DT graph presentation found in
|
| D | cci.txt | 28 root node (ie from CPUs perspective as per DT standard).
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio.txt | 106 a1) (Preferred) Dictated by a binding-specific DT property.
110 a2) Defined statically by the DT binding itself.
113 that would prevent the DT from separately representing the two orthogonal
|
| /linux-4.4.14/drivers/hwtracing/coresight/ |
| D | Kconfig | 10 a topological view of the CoreSight components based on a DT
|
| /linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
| D | samsung,sysmmu.txt | 31 The current DT binding for the Exynos System MMU is incomplete.
|
| /linux-4.4.14/Documentation/devicetree/bindings/soc/fsl/ |
| D | bman.txt | 88 etc.). The size configured in the DT must reflect the hardware capabilities and
|
| D | qman.txt | 105 FMan ports, etc.). The size configured in the DT must reflect the hardware
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 107 ... /* Standard DT properties for the device itself elided */
166 structure of the DT nodes that contain these properties.
|
| /linux-4.4.14/drivers/isdn/hardware/eicon/ |
| D | pc.h | 286 #define DT 0x29 /* ETSI date/time */ macro
|
| D | message.c | 4864 {MAXPARMSIDS, CPN, 0xff, DSA, OSA, BC, LLC, HLC, ESC_CAUSE, DSP, DT, CHA, in sig_ind()
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | fscache.txt | 351 …17e4b 2 ACTV 0 0 0 0 0 0 7b 4 0 0 | NFS.fh DT 0 ffff88001dd82820…
352 …1693a 2 ACTV 0 0 0 0 0 0 7b 4 0 0 | NFS.fh DT 0 ffff88002db23380…
377 TY Cookie type (IX - index, DT - data, hex - special)
|
| /linux-4.4.14/Documentation/nvmem/ |
| D | nvmem.txt | 22 This framework aims at solve these problems. It also introduces DT
|
| /linux-4.4.14/Documentation/fpga/ |
| D | fpga-mgr.txt | 44 Given a DT node, get an exclusive reference to a FPGA manager or release
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 22 driver and is not defined in the DT. The SPM state machine should be
|
| /linux-4.4.14/Documentation/arm/Marvell/ |
| D | README | 149 Directory: arch/arm/mach-mvebu (DT enabled platforms)
150 arch/arm/mach-dove (non-DT enabled platforms)
|
| /linux-4.4.14/Documentation/devicetree/bindings/bus/ |
| D | ti-gpmc.txt | 17 - ti,hwmods: Should be set to "ti,gpmc" until the DT transition is
|
| /linux-4.4.14/Documentation/scsi/ |
| D | ChangeLog.sym53c8xx_2 | 76 - Add DT/ST (double/simple transition) in the transfer
|
| D | ChangeLog.sym53c8xx | 53 The C1010 supports offset 62 in DT mode but only 31 in
59 not requires extra cycles in DT DATA OUT phase.
72 pass PPR options (for now only DT clocking).
188 62 in DT mode.
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,brcmstb.txt | 4 SoC shall have the following DT organization:
|
| /linux-4.4.14/sound/isa/ |
| D | Kconfig | 68 tristate "Diamond Tech. DT-019x and Avance Logic ALSxxx"
76 Diamond Technologies DT-019X or Avance Logic chips: ALS007,
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | as3722.txt | 116 Missing this property on DT will be assume as no
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | clock-bindings.txt | 124 This DT fragment defines three devices: an external oscillator to provide a
|
| /linux-4.4.14/arch/arm/plat-samsung/ |
| D | Kconfig | 49 Platforms that support only DT based boot need not to select
|
| /linux-4.4.14/Documentation/thermal/ |
| D | cpu-cooling-api.txt | 33 order to bind it via the thermal DT code. This api can support multiple
|
| /linux-4.4.14/Documentation/ |
| D | hwspinlock.txt | 53 This function provides a means for DT users of a hwspinlock module
|
| /linux-4.4.14/drivers/power/ |
| D | Kconfig | 398 is an integrated, single-cell lithium-ion battery charger. DT
|
| /linux-4.4.14/drivers/staging/comedi/ |
| D | Kconfig | 383 tristate "Data Translation DT2821 series and DT-EZ ISA card support"
386 Enable support for Data Translation DT2821 series including DT-EZ
|
| /linux-4.4.14/drivers/media/dvb-frontends/ |
| D | Kconfig | 812 * Panasonic ENV57H12D5 (ET-50DT)
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic7xxx.reg | 185 field SINGLE_EDGE 0x10 /* Disable DT Transfers */
|
| D | aic7xxx.seq | 1040 * We enable the auto-ack feature on DT capable
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | v4l2-framework.txt | 345 in DT as I2C device nodes. The API used in this second case is described further
|
| /linux-4.4.14/arch/mips/ |
| D | Kconfig | 174 Build a generic DT-based kernel image that boots on select
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | ALSA-Configuration.txt | 588 Module for Diamond Technologies DT-019X / Avance Logic ALS-007 (PnP
|