| /linux-4.1.27/arch/ia64/scripts/ |
| D | pvcheck.sed | 4 s/ssm.*psr\.ic.*/.warning \"ssm psr.ic should not be used directly\"/g
5 s/rsm.*psr\.ic.*/.warning \"rsm psr.ic should not be used directly\"/g
6 s/ssm.*psr\.i.*/.warning \"ssm psr.i should not be used directly\"/g
7 s/rsm.*psr\.i.*/.warning \"rsm psr.i should not be used directly\"/g
8 s/ssm.*psr\.dt.*/.warning \"ssm psr.dt should not be used directly\"/g
9 s/rsm.*psr\.dt.*/.warning \"rsm psr.dt should not be used directly\"/g
10 s/mov.*=.*cr\.ifa/.warning \"cr.ifa should not used directly\"/g
11 s/mov.*=.*cr\.itir/.warning \"cr.itir should not used directly\"/g
12 s/mov.*=.*cr\.isr/.warning \"cr.isr should not used directly\"/g
13 s/mov.*=.*cr\.iha/.warning \"cr.iha should not used directly\"/g
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | wii.txt | 30 - compatible : should be "nintendo,hollywood-vi","nintendo,flipper-vi"
31 - reg : should contain the VI registers location and length
32 - interrupts : should contain the VI interrupt
41 - compatible : should be "nintendo,hollywood-pi","nintendo,flipper-pi"
42 - reg : should contain the PI registers location and length
53 - compatible : should be "nintendo,flipper-pic"
63 - compatible : should be "nintendo,hollywood-dsp","nintendo,flipper-dsp"
64 - reg : should contain the DSP registers location and length
65 - interrupts : should contain the DSP interrupt
75 - compatible : should be "nintendo,hollywood-si","nintendo,flipper-si"
[all …]
|
| D | gamecube.txt | 21 - compatible : should be "nintendo,flipper-vi"
22 - reg : should contain the VI registers location and length
23 - interrupts : should contain the VI interrupt
32 - compatible : should be "nintendo,flipper-pi"
33 - reg : should contain the PI registers location and length
43 - compatible : should be "nintendo,flipper-pic"
52 - compatible : should be "nintendo,flipper-dsp"
53 - reg : should contain the DSP registers location and length
54 - interrupts : should contain the DSP interrupt
64 - compatible : should be "nintendo,flipper-aram"
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | akebono.txt | 20 - compatible : should be "ibm,476gtr-sdhci","generic-sdhci".
21 - reg : should contain the SDHCI registers location and length.
23 - interrupts : should contain the SDHCI interrupt.
31 - compatible : should be "ibm,476gtr-ahci".
32 - reg : should contain the AHCI registers location and length.
34 - interrupts : should contain the AHCI interrupt.
43 - compatible : should be "ibm,akebono-fpga".
44 - reg : should contain the FPGA registers location and length.
53 - compatible : should be "ibm,akebono-avr".
54 - reg : should contain the I2C bus address for the AVR.
|
| /linux-4.1.27/drivers/staging/iio/Documentation/ |
| D | sysfs-bus-iio-light | 33 This should return the calculated lux from the light sensor. If
34 it comes back in SI units, it should also include _input else it
35 should include _raw to signify it is not in SI units.
42 in proximity mode. When this is enabled, then the device should
52 This property is supported by proximity sensors and should be
54 value is returned in SI units, it should also include _input
55 but if it is not, then it should include _raw.
62 sensing mode. This value should be the output from a reading
63 and if expressed in SI units, should include _input. If this
64 value is not in SI units, then it should include _raw.
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/ |
| D | par_io.txt | 4 The node should reside in the "soc" node of the tree. For each
5 device that using parallel I/O ports, a child node should be created.
10 - device_type : should be "par_io".
25 Note that "par_io" nodes are obsolete, and should not be used for
26 the new device trees. Instead, each Par I/O bank should be represented
30 - #gpio-cells : should be "2".
31 - compatible : should be "fsl,<chip>-qe-pario-bank",
|
| D | usb.txt | 4 - compatible : should be "fsl,<chip>-qe-usb", "fsl,mpc8323-qe-usb".
5 - reg : the first two cells should contain usb registers location and
6 length, the next two two cells should contain PRAM location and
8 - interrupts : should contain USB interrupt.
19 - gpios : should specify GPIOs in this order: USBOE, USBTP, USBTN, USBRP,
|
| D | ucc.txt | 4 - device_type : should be "network", "hldc", "uart", "transparent"
11 information for the interrupt. This should be encoded based on
22 driver should use "Soft-UART" mode, which is needed on some SOCs that have
34 Drivers that currently use the deprecated properties should continue to
35 do so, in order to support older device trees, but they should be updated
|
| /linux-4.1.27/Documentation/devicetree/bindings/media/ |
| D | exynos-fimc-lite.txt | 5 - compatible : should be one of:
11 - interrupts : should contain FIMC-LITE interrupt;
12 - clocks : FIMC LITE gate clock should be specified in this property.
13 - clock-names : should contain "flite" entry.
15 Each FIMC device should have an alias in the aliases node, in the form of
|
| D | exynos5-gsc.txt | 6 - compatible: should be "samsung,exynos5-gsc"
7 - reg: should contain G-Scaler physical address location and length.
8 - interrupts: should contain G-Scaler interrupt number
19 Each G-Scaler node should have a numbered alias in the aliases node,
|
| D | samsung-s5k6a3.txt | 15 - clocks : should contain list of phandle and clock specifier pairs
18 - clock-names : should contain "extclk" entry for the sensor's EXTCLK clock;
22 - clock-frequency : the frequency at which the "extclk" clock should be
26 The common video interfaces bindings (see video-interfaces.txt) should be
28 node should contain one 'port' child node with an 'endpoint' subnode.
|
| D | samsung-s5c73m3.txt | 8 and should be placed under respective bus controller nodes.
25 - clocks : should contain list of phandle and clock specifier pairs
28 - clock-names : should contain "cis_extclk" entry for the CIS_EXTCLK clock;
32 - clock-frequency : the frequency at which the "cis_extclk" clock should be
36 The common video interfaces bindings (see video-interfaces.txt) should be used
38 device node should contain one 'port' child node with an 'endpoint' subnode for
50 and physical lane indexes in subsequent elements of the array should
|
| D | exynos-jpeg-codec.txt | 5 - compatible : should be one of:
10 - clock-names : should contain:
13 - clocks : should contain the clock specifier and clock ID list
|
| D | sunxi-ir.txt | 7 - clock-names : should contain "apb" and "ir" entries;
8 - interrupts : should contain IR IRQ number;
9 - reg : should contain IO map address for IR.
|
| D | samsung-s5k5baf.txt | 18 - clock-names : should include "mclk" for the sensor's master clock;
22 - clock-frequency : the frequency at which the "mclk" clock should be
26 The device node should contain one 'port' child node with one child 'endpoint'
35 video-interfaces.txt. If present it should be <1> - the device
|
| D | samsung-fimc.txt | 25 must be 1. A clock provider is associated with the 'camera' node and it should
30 - clock-output-names: from the common clock bindings, should contain names of
37 camera port pinmux at runtime. The "idle" state should configure both the camera
39 should be inactive. For the "active-a" state the camera port A must be activated
40 and the port B deactivated and for the state "active-b" it should be the other
54 - interrupts: should contain FIMC interrupt;
67 Each FIMC device should have an alias in the aliases node, in the form of
83 respectively. If a rotator is present its corresponding bit should be set.
96 This node should contain child 'port' nodes specifying active parallel video
108 The sensor device nodes should be added to their control bus controller (e.g.
|
| D | st-rc.txt | 11 protocol used for receiving remote control signals. rx-mode should
13 - tx-mode: should be "infrared". This property specifies the L1
14 protocol used for transmitting remote control signals. tx-mode should
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | nspire.txt | 4 - compatible: Compatible property value should contain "ti,nspire".
5 CX models should have "ti,nspire-cx"
6 Touchpad models should have "ti,nspire-tp"
7 Clickpad models should have "ti,nspire-clp"
|
| D | pmu.txt | 5 representation in the device tree should be done as under:-
9 - compatible : should be one of
25 interrupt (PPI) then 1 interrupt should be specified.
33 This property should be present when there is more than
|
| D | l2cc.txt | 9 The ARM L2 cache representation in the device tree should be done as follows:
13 - compatible : should be one of:
38 without setup latency control should use a value of 0.
41 should use 0. Controllers without separate read and write Tag RAM latency
42 values should only use the first cell.
|
| /linux-4.1.27/Documentation/devicetree/bindings/misc/ |
| D | sram.txt | 15 child node should use a 'reg' property to specify a specific range of
18 Following the generic-names recommended practice, node names should
19 reflect the purpose of the node. Unit address (@<address>) should be
24 - #address-cells, #size-cells : should use the same values as the root node
25 - ranges : standard definition, should translate from local addresses
34 - compatible : standard definition, should contain a vendor specific string
|
| /linux-4.1.27/Documentation/devicetree/bindings/sound/ |
| D | rockchip-i2s.txt | 8 - compatible: should be one of the followings
14 - interrupts: should contain the I2S interrupt.
15 - #address-cells: should be 1.
16 - #size-cells: should be 0.
19 - dma-names: should include "tx" and "rx".
21 - clock-names: should contain followings:
|
| D | brcm,bcm2835-i2s.txt | 6 * The first entry should cover the PCM registers
7 * The second entry should cover the PCM clock registers
12 One of the DMA channels will be responsible for transmission (should be
13 named "tx") and one for reception (should be named "rx").
|
| D | sirf-audio-port.txt | 10 One of the DMA channels will be responsible for transmission (should be
11 named "tx") and one for reception (should be named "rx").
|
| /linux-4.1.27/Documentation/devicetree/bindings/rtc/ |
| D | atmel,at91sam9-rtc.txt | 4 - compatible: should be: "atmel,at91sam9260-rtt"
5 - reg: should encode the memory region of the RTT controller
7 - clocks: should contain the 32 KHz slow clk that will drive the RTT block.
8 - atmel,rtt-rtc-time-reg: should encode the GPBR register used to store
10 The first cell should point to the GPBR node and the second one
|
| D | abracon,abx80x.txt | 9 - "compatible": should one of:
28 - "abracon,tc-diode": should be "standard" (0.6V) or "schottky" (0.3V)
29 - "abracon,tc-resistor": should be <0>, <3>, <6> or <11>. 0 disables the output
|
| D | nxp,rtc-2123.txt | 4 - compatible: should be: "nxp,rtc-pcf2123"
5 - reg: should be the SPI slave chipselect address
|
| D | haoyu,hym8563.txt | 7 - compatible: should be: "haoyu,hym8563"
10 - #clock-cells: the value should be 0
|
| D | dallas,ds1339.txt | 10 Should be given if trickle charger should be enabled
12 Should be given if internal trickle charger diode should be disabled
|
| D | rtc-cmos.txt | 6 - reg : should contain registers location and length.
9 - interrupts : should contain interrupt.
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | review-checklist.txt | 7 2. Patches should be against kvm.git master branch.
15 5. New features must default to off (userspace should explicitly request them).
16 Performance improvements can and should default to on.
18 6. New cpu features should be exposed via KVM_GET_SUPPORTED_CPUID2
20 7. Emulator changes should be accompanied by unit tests for qemu-kvm.git
23 8. Changes should be vendor neutral when possible. Changes to common code
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | backend-api.txt | 20 The cache definition (struct fscache_cache) should be initialised by calling:
38 The cache should then be registered with FS-Cache by passing a pointer to the
45 Two extra arguments should also be supplied:
47 (*) "fsdef" which should point to the object representation for the FS-Cache
52 (*) "tagname" which, if given, should be a text string naming this cache. If
138 Structures of this type should be allocated by the cache backend and
144 that refer to a particular object. In such a case it should be printed
148 is backing. An object should retired when put_object() is called if it is
149 in state FSCACHE_OBJECT_RECYCLING. The fscache_object struct should be
173 an operation needs more processing time, it should be enqueued again.
[all …]
|
| D | operations.txt | 33 To make use of this facility, <linux/fscache-cache.h> should be #included.
52 Someone wanting to issue an operation should allocate something with this
53 struct embedded in it. They should initialise it by calling:
60 The op->flags parameter should be set to indicate the CPU time provision and
63 The op->fast_work, op->slow_work and op->processor flags should be set as
154 The first function should be used to submit non-exclusive ops and the
167 it, so the caller should put their reference to it by passing it to:
172 operation with FSCACHE_OP_MYTHREAD, then it should monitor
176 When it has finished doing its processing, it should call
200 processor method with a pointer to the operation. This should then get at the
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/ |
| D | brcm,bcmgenet.txt | 4 - compatible: should contain one of "brcm,genet-v1", "brcm,genet-v2",
11 - #address-cells: should be 1
12 - #size-cells: should be 1
19 name should be "enet" and second should be "enet-wol".
26 voluntarily disabled, this property should be used to describe the "fixed link".
32 - mdio bus node: this node should always be present regarless of the PHY
37 - compatible: should contain one of "brcm,genet-mdio-v1", "brcm,genet-mdio-v2"
42 - #address-cells: address cell for MDIO bus addressing, should be 1
43 - #size-cells: size of the cells for MDIO bus addressing, should be 0
|
| D | meson-dwmac.txt | 8 - compatible: should be "amlogic,meson6-dwmac" along with "snps,dwmac"
12 - reg: should contain a register range for the dwmac controller and
|
| /linux-4.1.27/Documentation/devicetree/bindings/usb/ |
| D | exynos-usb.txt | 8 - compatible: should be "samsung,exynos4210-ehci" for USB 2.0
15 - port: if in the SoC there are EHCI phys, they should be listed here.
16 One phy per port. Each port should have following entries:
49 - compatible: should be "samsung,exynos4210-ohci" for USB 2.0
56 - port: if in the SoC there are OHCI phys, they should be listed here.
57 One phy per port. Each port should have following entries:
85 - compatible: should be one of the following -
89 - #address-cells, #size-cells : should be '1' if the device has sub-nodes
97 The dwc3 core should be added as subnode to Exynos dwc3 glue.
|
| D | samsung-usbphy.txt | 14 - compatible : should be "samsung,exynos4210-usb2phy"
22 - compatible : should be "samsung,exynos5250-usb2phy"
27 - #address-cells: should be '1' when usbphy node has a child node with 'reg'
29 - #size-cells: should be '1' when usbphy node has a child node with 'reg'
35 interface for usb-phy. It should provide the following information required by
75 - compatible : should be "samsung,exynos5250-usb3phy"
83 - #address-cells: should be '1' when usbphy node has a child node with 'reg'
85 - #size-cells: should be '1' when usbphy node has a child node with 'reg'
91 interface for usb-phy. It should provide the following information required by
|
| D | ohci-st.txt | 8 - interrupts : one OHCI controller interrupt should be described here
10 - clock-names : should be "ic" for interconnect clock and "clk48"
14 - phy-names : should be "usb"
17 - reset-names : should be "power" and "softreset".
|
| D | dwc3-st.txt | 10 - reg-names : should be "reg-glue" and "syscfg-reg"
11 - st,syscon : should be phandle to system configuration node which
13 - resets : list of phandle and reset specifier pairs. There should be two entries, one
15 - reset-names : list of reset signal names. Names should be "powerdown" and "softreset"
19 - #address-cells, #size-cells : should be '1' if the device has sub-nodes
32 The dwc3 core should be added as subnode to ST DWC3 glue as shown in the
|
| D | ehci-st.txt | 7 - interrupts : one EHCI interrupt should be described here
12 - clock-names : should be "ic" for interconnect clock and "clk48"
16 - phy-names : should be "usb"
19 - reset-names : should be "power" and "softreset"
|
| D | usb-xhci.txt | 4 - compatible: should be one of "generic-xhci",
8 - reg: should contain address and length of the standard XHCI
10 - interrupts: one XHCI interrupt should be described here.
|
| D | twlxxxx-usb.txt | 5 - interrupts : Two interrupt numbers to the cpu should be specified. First
10 - usb-supply : phandle to the regulator device tree node. It should be vusb
25 - interrupts : The interrupt numbers to the cpu should be specified. First
29 <supply-name> should be vusb1v5, vusb1v8 and vusb3v1
|
| D | keystone-usb.txt | 6 - compatible: should be "ti,keystone-dwc3".
7 - #address-cells, #size-cells : should be '1' if the device has sub-nodes
19 The dwc3 core should be added as subnode to Keystone DWC3 glue.
|
| D | usb-ehci.txt | 4 - compatible : should be "generic-ehci".
5 - reg : should contain at least address and length of the standard EHCI
9 - interrupts : one EHCI interrupt should be described here.
|
| D | ohci-omap3.txt | 5 - compatible: should be "ti,ohci-omap3"
6 - reg: should contain one register range i.e. start and length
|
| D | usb-nop-xceiv.txt | 4 - compatible: should be usb-nop-xceiv
20 - vbus-detect-gpio: should specify the GPIO detecting a VBus insertion
22 - vbus-regulator : should specifiy the regulator supplying current drawn from
|
| D | ci-hdrc-usb2.txt | 4 - compatible: should be "chipidea,usb2"
11 - phy-names: should be "usb-phy"
|
| D | fsl-usb.txt | 12 Wherever applicable, the IP version of the USB controller should
14 - phy_type : For multi port host USB controllers, should be one of
15 "ulpi", or "serial". For dual role USB controllers, should be
33 information for the interrupt. This should be encoded based on
|
| D | ehci-omap.txt | 8 - compatible: should be "ti,ehci-omap"
9 - reg: should contain one register range i.e. start and length
|
| D | keystone-phy.txt | 4 - compatible: should be "ti,keystone-usbphy".
5 - #address-cells, #size-cells : should be '1' if the device has sub-nodes
|
| /linux-4.1.27/Documentation/devicetree/bindings/phy/ |
| D | berlin-sata-phy.txt | 5 - compatible: should be one of
8 - address-cells: should be 1
9 - size-cells: should be 0
15 Each PHY should be represented as a sub-node.
|
| D | rockchip-usb-phy.txt | 7 - #address-cells: should be 1
8 - #size-cells: should be 0
11 Each PHY should be represented as a sub-node.
15 - #phy-cells: should be 0
|
| D | phy-stih41x-usb.txt | 8 - compatible : should be "st,stih416-usb-phy" or "st,stih415-usb-phy"
9 - st,syscfg : should be a phandle of the syscfg node
|
| /linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
| D | omap-usb-tll.txt | 5 - compatible : should be "ti,usbhs-tll"
6 - reg : should contain one register range i.e. start and length
7 - interrupts : should contain the TLL module's interrupt
15 - clock-names: should include:
|
| D | atmel-hlcdc.txt | 4 - compatible: value should be one of the following:
9 - clocks: should contain the 3 clocks requested by the HLCDC device.
10 - interrupts: should contain the description of the HLCDC interrupt line
|
| /linux-4.1.27/Documentation/devicetree/bindings/drm/imx/ |
| D | ldb.txt | 10 - #address-cells : should be <1>
11 - #size-cells : should be <0>
12 - compatible : should be "fsl,imx53-ldb" or "fsl,imx6q-ldb".
16 - gpr : should be <&gpr> on i.MX53 and i.MX6q.
37 - pinctrl-names : should be "default" on i.MX53, not used on i.MX6q
40 - fsl,dual-channel : boolean. if it exists, only LVDS channel 0 should
52 - reg : should be <0> or <1>
58 On i.MX6, there should be four input ports (port@[0-3]) that correspond
67 - fsl,data-mapping : should be "spwg" or "jeida"
70 - fsl,data-width : should be <18> or <24>
|
| D | hdmi.txt | 10 - #address-cells : should be <1>
11 - #size-cells : should be <0>
12 - compatible : should be "fsl,imx6q-hdmi" or "fsl,imx6dl-hdmi".
13 - gpr : should be <&gpr>.
|
| /linux-4.1.27/Documentation/networking/ |
| D | netdev-features.txt | 23 request. This set should be initialized in ndo_init callback and not
27 for a device. This should be changed only by network core or in
38 networking core and should not be referenced in drivers.
62 netdev_update_features() while holding rtnl_lock. This should not be done
63 from ndo_*_features callbacks. netdev->features should not be modified by
73 All dependencies between features should be resolved here. The resulting
78 This callback should not modify hardware nor driver state (should be
88 Hardware should be reconfigured to match passed feature set. The set
89 should not be altered unless some error condition happens that can't
91 should update netdev->features to match resulting hardware state.
[all …]
|
| D | x25-iface.txt | 26 over the LAPB link. The LAPB link should already exist before any data is
32 confirmation message should be returned as soon as possible.
37 confirmation message should be returned as soon as possible.
89 Thus, driver authors should make netif_rx() as reliable as possible:
94 - Driver authors should use irq affinity for the interrupt handler.
99 (1) Drivers for kernel versions 2.4.x and above should always check the
107 data_indication() method should now transparently pass the
109 (2) Drivers for kernel versions 2.2.x should always check the global
111 should only call netif_rx() if netdev_dropping is zero. Otherwise
112 the driver should not confirm delivery of the frame and drop it.
[all …]
|
| D | regulatory.txt | 17 core regulatory domain all wireless devices should adhere to.
38 # Example file, should be put in /etc/udev/rules.d/regulatory.rules
86 roaming should use this callback. More on world roaming will be
143 structure and pass it to the wireless core. To do this you should
145 structure and you should then fill it with your data. Finally you simply
205 The file net/wireless/db.txt should be kept up-to-date with the db.txt
210 Again, most users in most situations should be using the CRDA package
212 should be building and using CRDA on their own rather than using
213 this option. If you are not absolutely sure that you should be using
|
| D | dm9000.txt | 16 maintained and tested by Ben Dooks, who should be CC: to any patches for this
29 These resources should be specified in that order, as the ordering of the
97 The IO should be done with 8bit operations.
101 The IO should be done with 16bit operations.
105 The IO should be done with 32bit operations.
114 EEPROM, or that the EEPROM should be hidden from the user.
|
| D | ppp_generic.txt | 50 flow-control reasons. In this case, start_xmit() should return 0
51 and the channel should call the ppp_output_wakeup() function at a
54 is accepted, the start_xmit() function should return 1.
85 generic layer to this channel. The channel should provide some way
125 however it wishes. The channel should initialize the `mtu' and
133 start of the PPP frame), it should set the `hdrlen' field of the
136 should still check if there is sufficient headroom and copy the skbuff
139 On the input side, channels should ideally provide at least 2 bytes of
287 instance the "owner" of the interface. The argument should point to
294 The argument should point to an int containing the unit number.
[all …]
|
| /linux-4.1.27/Documentation/arm/ |
| D | Setup | 11 should not be referenced outside of arch/arm/kernel/setup.c:setup_arch().
24 the memory is banked, then this should contain the total number
27 If the system contains separate VRAM, this value should not
32 This is now obsolete, and should not be used.
50 or VGA console character size. They should not be used for any other
61 is otherwise unused. (should not be used for other console types, and
62 should not be used for other purposes).
82 These are now obsolete, and should not be used.
125 These are now obsolete, and should not be used.
|
| D | Booting | 14 Essentially, the boot loader should provide (as a minimum) the
45 The boot loader should initialise and enable one serial port on the
47 which serial port it should use for the kernel console (generally
63 The boot loader should detect the machine type its running on by some
68 should be passed to the kernel in register r1.
100 minimum tagged list should look:
110 The tagged list should be stored in system RAM.
161 kernel should be placed in the first 128MiB of RAM. It is recommended
208 should be such that a kernel which does not include support for the
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | qe.txt | 4 NOTE: This is an interim binding; it should be updated to fit
8 as a complete entity (UCC, USB etc ). All of them should be siblings on
16 - compatible : should be "fsl,qe";
29 that contains the firmware that should be uploaded for this QE.
30 The compatible property for the firmware node should say,
52 - compatible : should be "fsl,qe-muram", "fsl,cpm-muram".
79 property, and any firmware-specific properties. The node should be placed
82 should define an fsl,firmware-phandle property that points to the firmware node
93 kind of firmware it is. For QE, this should be "fsl,qe-firmware".
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mcu-mpc8349emitx.txt | 5 - reg : should specify I2C address (0x0a).
6 - #gpio-cells : should be 2.
7 - gpio-controller : should be present.
|
| D | cpus.txt | 31 these registers should be set if the coresponding CPU should be
33 that should be set if this cpu should be snooped.
|
| D | pmc.txt | 6 "fsl,mpc8349-pmc" should be listed for any chip whose PMC is
7 compatible. "fsl,mpc8313-pmc" should also be listed for any chip
10 "fsl,mpc8548-pmc" should be listed for any chip whose PMC is
11 compatible. "fsl,mpc8536-pmc" should also be listed for any chip
14 "fsl,mpc8641d-pmc" should be listed for any chip whose PMC is
51 DEVDISR2, if present -- this cell should be zero or absent if the
|
| D | gtm.txt | 4 - compatible : should be
8 - reg : should contain gtm registers location and length (0x40).
9 - interrupts : should contain four interrupts.
|
| D | diu.txt | 7 - compatible : should be "fsl,diu" or "fsl,mpc5121-diu".
8 - reg : should contain at least address and length of the DIU register
10 - interrupts : one DIU interrupt should be described here.
|
| D | board.txt | 25 - compatible: should be a board-specific string followed by a string
28 - reg: should contain the address and the length of the FPGA register set.
29 - interrupt-parent: should specify phandle for the interrupt controller.
30 - interrupts: should specify event (wakeup) IRQ.
96 - reg: should describe CPLD registers
|
| D | pamu.txt | 15 I/O space utilized by the controller. The size should
42 functions. Certain bits from these registers should be
43 set if PAMUs should be snooped. This property defines
44 a bitmask which selects the bits that should be set if
45 PAMUs should be snooped.
50 connected to a specific PAMU device should have a "fsl,pamu-phandle" property
56 PAMU controller's configuration registers. The size should
|
| D | srio.txt | 13 compatible is provided it should be ordered before "fsl,srio".
19 length of the SRIO configuration registers. The size should
39 Port Child Nodes: There should a port child node for each port that exists in
40 the controller. The ports are numbered starting at one (1) and should have
60 correctly configured for SRIO accesses. The property should
|
| D | mpc5200.txt | 10 <chip>-<device>[-<mode>]. The OS should be able to match a device driver
12 match on the compatible list; the 'most compatible' driver should be
16 conundrum. How should the compatible property be set up to provide
28 should have two items in the compatible list:
71 tree should use the "fsl,mpc5200b-<device>","fsl,mpc5200-<device>" form.
105 design supports the internal wdt, then the device node for GPT0 should
140 The PSCs should include a cell-index which is the index of the PSC in
153 Each GPIO controller node should have the empty property gpio-controller and
164 - current-speed - Specifies that the MII should be configured for a fixed
165 speed. This property should contain two cells. The
[all …]
|
| D | cache_sram.txt | 6 tree should be done as under:-
10 - compatible : should be "fsl,p2020-cache-sram"
|
| /linux-4.1.27/Documentation/serial/ |
| D | driver | 7 driver. It is not complete, any questions you have should be directed to
77 this function should return TIOCSER_TEMT, otherwise return 0.
78 If the port does not support this operation, then it should
94 If the appropriate bit is set, the signal should be driven
95 active. If the bit is clear, the signal should be driven
104 of the outputs should not be returned, since the core keeps
105 track of their state. The state information should include:
111 the port does not support CTS, DCD or DSR, the driver should
113 not available, the signal should not be indicated as active.
124 The driver should stop transmitting characters as soon as
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/nios2/ |
| D | nios2.txt | 11 - compatible: Compatible property value should be "altr,nios2-1.0".
15 interrupt source, should be 1.
26 - altr,has-mul: Specifies CPU hardware multipy support, should be 1.
27 - altr,has-mmu: Specifies CPU support MMU support, should be 1.
28 - altr,has-initda: Specifies CPU support initda instruction, should be 1.
35 - altr,implementation: Nios II core implementation, this should be "fast";
|
| /linux-4.1.27/tools/testing/selftests/powerpc/primitives/ |
| D | load_unaligned_zeropad.c | 104 unsigned long should; in do_one_test() local
108 should = *(unsigned long *)p; in do_one_test()
113 if (should != got) in do_one_test()
114 …tf("offset %u load_unaligned_zeropad returned 0x%lx, should be 0x%lx\n", page_offset, got, should); in do_one_test()
|
| /linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
| D | gpio-samsung.txt | 4 - compatible: Compatible property value should be "samsung,exynos4-gpio>".
10 should be the following with values derived from the SoC user manual.
29 - #address-cells: should be 1.
30 - #size-cells: should be 1.
|
| D | gpio-tz1090.txt | 4 - compatible: Compatible property value should be "img,tz1090-gpio".
13 - Each bank of GPIOs should have a subnode to represent it.
21 nodes should have the following values.
42 client nodes should have the following values.
|
| D | gpio-stmpe.txt | 8 - st,norequest-mask: bitmask specifying which GPIOs should _not_ be requestable
11 Node name must be stmpe_gpio and should be child node of stmpe node to which it
|
| D | gpio-mvebu.txt | 6 or "marvell,armadaxp-gpio". "marvell,orion-gpio" should be used for
8 370. "marvell,mv78200-gpio" should be used for the Discovery
9 MV78200. "marvel,armadaxp-gpio" should be used for all Armada XP
|
| D | gpio-clps711x.txt | 6 There should be two registers, first is DATA register, the second
14 Note: Each GPIO port should have an alias correctly numbered in "aliases"
|
| /linux-4.1.27/Documentation/devicetree/bindings/iio/accel/ |
| D | bma180.txt | 7 - compatible : should be "bosch,bma180"
12 - interrupt-parent : should be the phandle for the interrupt controller
14 - interrupts : interrupt mapping for GPIO IRQ, it should by configured with
|
| /linux-4.1.27/drivers/staging/media/davinci_vpfe/ |
| D | TODO | 5 - Controls should be used when possible rather than private ioctl
6 - No enums should be used
14 - The driver should have no knowledge of possible external subdevs; see
16 - Some of the hardware control should be refactorede
18 - Names that are visible in kernel global namespace should have a common
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 5.Posting | 19 feedback from the community before the work is complete. So you should
32 There are a number of things which should be done before you consider
43 - Does your change have performance implications? If so, you should run
45 summary of the results should be included with the patch.
62 general rule, a patch should be based on the current mainline as found in
73 Only the most simple changes should be formatted as a single patch;
74 everything else should be made as a logical series of changes. Splitting
86 - Each logically independent change should be formatted as a separate
88 large (adding a significant new driver, for example), but they should be
90 should make a specific change which can be reviewed on its own and
[all …]
|
| D | 4.Coding | 48 on it for other reasons, but coding style changes should not be made for
51 The coding style document also should not be read as an absolute law which
64 just as harmful as premature optimization. Abstraction should be used to
75 patches to remove unused arguments; they should, in general, not be added
102 should be confined to header files whenever possible.
124 slow execution dramatically. Inline functions, as a rule, should be quite
135 a given function should actually be inlined or not. So the liberal
165 New code should be written with this requirement in mind; retrofitting
167 should take the time to understand the available locking primitives well
214 tools should be used whenever possible.
[all …]
|
| /linux-4.1.27/Documentation/input/ |
| D | event-codes.txt | 90 Client should ignore all events up to and including next SYN_REPORT
109 code should be set to a value of 1. When the tool is no longer interacting
110 with the input device, the BTN_TOOL_<name> code should be reset to 0. All
111 trackpads, tablets, and touchscreens should use at least one BTN_TOOL_<name>
138 BTN_TOOL_DOUBLETAP should be set to value 1 for the duration of the motion.
140 purpose. A trackpad event generated by finger touches should generate events
142 codes should have a value of 1 during any synchronization frame.
147 Note: In multitouch drivers, the input_mt_report_finger_count() function should
154 space is unknown. If the absolute position is known, EV_ABS codes should be used
172 event should only be emitted while the tool is hovering, meaning in close
[all …]
|
| D | multi-touch-protocol.txt | 52 For type A devices, the kernel driver should generate an arbitrary
57 For type B devices, the kernel driver should associate a slot with each
69 driver. A driver for such a device should associate one type B slot with each
71 contact associated with a slot changes, the driver should invalidate that
73 tracking more contacts than it is currently reporting, the driver should use
75 being tracked by the hardware at that moment. The driver should do this by
78 The driver should only advertise as many slots as the hardware can report.
218 implicitly handled by input core; drivers should instead call
227 The length of the major axis of the contact. The length should be given in
239 tool. This should be understood as the size of the tool itself. The
[all …]
|
| D | gameport-programming.txt | 139 If the gameport supports cooked mode, this should be set to a value that
144 Trigger. This function should trigger the ns558 oneshots. If set to NULL,
154 If the gameport supports cooked mode, it should point this to its cooked
155 read function. It should fill axes[0..3] with four values of the joystick axes
160 Function for calibrating the ADC hardware. When called, axes[0..3] should be
161 pre-filled by cooked data by the caller, max[0..3] should be pre-filled with
162 expected maximums for each axis. The calibrate() function should set the
177 Close() should free the resources allocated by open, possibly disabling the
|
| /linux-4.1.27/Documentation/devicetree/bindings/pci/ |
| D | v3-v360epc-pci.txt | 7 - syscon: should contain a link to the syscon device node (since
13 - reg: should contain the base address of the V3 adapter.
14 - interrupts: should contain a reference to the V3 error interrupt
|
| /linux-4.1.27/Documentation/devicetree/bindings/drm/atmel/ |
| D | hlcdc-dc.txt | 7 - compatible: value should be "atmel,hlcdc-display-controller"
9 - pinctrl-0: should contain the default pinctrl states.
10 - #address-cells: should be set to 1.
11 - #size-cells: should be set to 0.
|
| /linux-4.1.27/Documentation/devicetree/bindings/video/ |
| D | dw_hdmi-rockchip.txt | 8 - clock-names: should be "iahb" "isfr"
9 - rockchip,grf: this soc should set GRF regs to mux vopl/vopb.
14 - reg-io-width: the width of the reg:1,4, the value should be 4 on
19 - clocks, clock-names: phandle to the HDMI CEC clock, name should be "cec"
|
| D | exynos_dsim.txt | 4 - compatible: value should be one of the following
10 - interrupts: should contain DSI interrupt
13 - clock-names: should include "bus_clk"and "pll_clk" entries
16 - phy-names: should include "dsim" entry
20 - #address-cells, #size-cells: should be set respectively to <1> and <0>
|
| D | exynos7-decon.txt | 8 - compatible: value should be "samsung,exynos7-decon";
12 - interrupt-parent: should be the phandle of the decon controller's
15 - interrupts: should contain a list of all DECON IP block interrupts in the
19 - interrupt-names: should contain the interrupt names: "fifo", "vsync",
|
| /linux-4.1.27/Documentation/devicetree/bindings/i2c/ |
| D | i2c-designware.txt | 5 - compatible : should be "snps,designware-i2c"
14 - i2c-sda-hold-time-ns : should contain the SDA hold time in nanoseconds.
17 - i2c-scl-falling-time-ns : should contain the SCL falling time in nanoseconds.
20 - i2c-sda-falling-time-ns : should contain the SDA falling time in nanoseconds.
|
| D | ti,bq32k.txt | 10 Should be given if trickle charger should be enabled
12 Should be given if internal trickle charger diode should be disabled
|
| D | i2c-meson.txt | 8 - #address-cells: should be <1>
9 - #size-cells: should be <0>
|
| D | i2c-digicolor.txt | 8 - #address-cells: should be <1>
9 - #size-cells: should be <0>
|
| D | i2c-riic.txt | 8 - #address-cells : should be <1>
9 - #size-cells : should be <0>
|
| D | i2c-jz4780.txt | 4 - compatible: should be "ingenic,jz4780-i2c"
11 - pinctrl-names: should be "default";
|
| /linux-4.1.27/Documentation/sound/oss/ |
| D | ALS | 18 Since the ALS-007/100/200 are PnP cards, ISAPnP support should probably be
22 When using kernel level ISAPnP, the kernel should correctly identify and
26 section. This should all be correctly configured by the kernel; if problems
33 of the card's resources should be passed to the kernel modules ("sb", "opl3"
36 requires they be different. For "sb", "io", "irq" and "dma" should be set
38 isapnp. "dma16" should be explicitly set to "-1" for an ALS-007 since this
41 "mpu_io" should be set to 0. The "io" parameter of the "opl3" module should
|
| /linux-4.1.27/Documentation/devicetree/bindings/spi/ |
| D | spi-meson.txt | 10 - compatible: should be "amlogic,meson6-spifc"
13 - #address-cells: should be 1
14 - #size-cells: should be 0
|
| D | spi-samsung.txt | 8 - compatible: should be one of the following.
28 - #address-cells: should be 1.
29 - #size-cells: should be 0.
41 - cs-gpios: should specify GPIOs used for chipselects (see spi-bus.txt)
45 - The spi slave nodes should provide the following information which is required
59 - All the SPI controller nodes should be represented in the aliases node using
|
| D | spi-rockchip.txt | 8 - compatible: should be one of the following.
19 - #address-cells: should be 1.
20 - #size-cells: should be 0.
26 - dma-names: DMA request names should include "tx" and "rx" if present.
|
| D | spi_altera.txt | 4 - compatible : should be "ALTR,spi-1.0". <DEPRECATED>
5 - compatible : should be "altr,spi-1.0".
|
| D | fsl-spi.txt | 7 - compatible : should be "fsl,spi" or "aeroflexgaisler,spictrl".
12 information for the interrupt. This should be encoded based on
40 - compatible : should be "fsl,mpc8536-espi".
42 - interrupts : should contain eSPI interrupt, the device has one interrupt.
|
| D | spi_oc_tiny.txt | 4 - compatible : should be "opencores,tiny-spi-rtlsvn2".
5 - gpios : should specify GPIOs used for chipselect.
|
| D | spi-dw.txt | 4 - compatible: should be "snps,designware-spi"
8 - interrupts: should contain one interrupt
|
| D | spi-gpio.txt | 5 - compatible: should be set to "spi-gpio"
6 - #address-cells: should be set to <0x1>
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/msm/ |
| D | ssbi.txt | 12 indicates the SSBI bus variant the controller should use to talk
13 with the slave device. This should be one of "ssbi", "ssbi2", or
17 The slave device should be the single child node of the ssbi device
|
| /linux-4.1.27/Documentation/usb/ |
| D | chipidea.txt | 23 The A-device(with micro A plug inserted) should enumrate B-device.
33 B-device should take host role and enumrate A-device.
39 A-device should switch back to host and enumrate B-device.
42 A-device should enumrate B-device again.
45 A-device should NOT enumrate B-device.
60 A-device should disconnect with B-device and power down the bus.
66 A-device should resume usb bus and enumrate B-device.
|
| D | gadget_serial.txt | 19 You should have received a copy of the GNU General Public
45 no longer statically defined. Your Linux based system should mount
96 serial driver running, you should be able to communicate between
128 Your system should use mdev (from busybox) or udev to make the
129 device nodes. After this gadget driver has been set up you should
142 The /dev/ttyGS0 line should work like most any other serial port.
159 to the Windows host with a USB cable, Windows should recognize the
174 should see "Gadget Serial" listed as the driver for one of the COM
189 to the Linux host with a USB cable, the host system should recognize
194 should show something like this:
[all …]
|
| /linux-4.1.27/Documentation/i2c/ |
| D | slave-interface | 39 Each backend should come with separate documentation to describe its specific
67 Another I2C master wants to write data to us. This event should be sent once
77 Another I2C master wants to read data from us. This event should be sent once
79 should transmit the first byte.
84 'ret': 0 if the byte should be acked, some errno if the byte should be nacked
87 is zero, the bus driver should ack this byte. If 'ret' is an errno, then the byte
88 should be nacked.
109 A stop condition was received. This can happen anytime and the backend should
134 should use pm_runtime_forbid() because your device usually needs to be powered
156 arises. However, cases should be extremely rare because the master is expected
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
| D | samsung-pinctrl.txt | 9 - compatible: should be one of the following.
47 as child nodes of the pin-controller node. There should be atleast one
54 The child node should contain a list of pin(s) on which a particular pin
57 should be atleast one pin specfied for this property and there is no upper
61 as "gpa0-0", "gpa0-1", "gpa0-2" and so on. The names should be in lower case.
62 The format of the pin names should be (as per the hardware manual)
65 The pin function selection that should be applied on the pins listed in the
67 of this property that should be applied to each of the pins listed in the
68 "samsung,pins" property should be picked from the hardware manual of the SoC
75 configuration that should be applied on all the pins listed in the
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/clock/ |
| D | marvell,mmp2.txt | 8 - compatible: should be one of the following.
15 - #clock-cells: should be 1.
16 - #reset-cells: should be 1.
|
| D | marvell,pxa168.txt | 8 - compatible: should be one of the following.
15 - #clock-cells: should be 1.
16 - #reset-cells: should be 1.
|
| D | marvell,pxa910.txt | 8 - compatible: should be one of the following.
15 - #clock-cells: should be 1.
16 - #reset-cells: should be 1.
|
| D | hi3620-clock.txt | 8 - compatible: should be one of the following.
15 - #clock-cells: should be 1.
|
| D | imx6sx-clock.txt | 9 - clock-names: should include entries "ckil", "osc", "ipp_di0" and "ipp_di1"
11 The clock consumer should specify the desired clock by having the clock
|
| D | clk-s5pv210-audss.txt | 8 - compatible: should be "samsung,s5pv210-audss-clock".
11 - #clock-cells: should be 1.
23 - clock-names: Aliases for the above clocks. They should be "hclk",
|
| D | rockchip,rk3288-cru.txt | 9 - compatible: should be "rockchip,rk3288-cru"
12 - #clock-cells: should be 1.
13 - #reset-cells: should be 1.
|
| D | exynos5440-clock.txt | 8 - compatible: should be "samsung,exynos5440-clock".
13 - #clock-cells: should be 1.
|
| /linux-4.1.27/Documentation/fb/ |
| D | aty128fb.txt | 18 * graphic mode is slower than text mode... but you should not notice
32 You should compile in both vgacon (to boot if you remove your Rage128 from
33 box) and aty128fb (for graphics mode). You should not compile-in vesafb
41 XF68_FBDev should generally work fine, but it is non-accelerated. As of
51 `video=aty128fb:option1,option2:value2,option3' (multiple options should
|
| D | sa1100fb.txt | 16 on the kernel command line should be enough to configure the
17 controller. The bits per pixel (bpp) value should be 4, 8, 12, or
18 16. LCCR values are display-specific and should be computed as
|
| /linux-4.1.27/Documentation/devicetree/bindings/mmc/ |
| D | atmel-hsmci.txt | 12 - compatible: should be "atmel,hsmci"
13 - #address-cells: should be one. The cell is the slot id.
14 - #size-cells: should be zero.
39 - reg: should contain the slot id.
|
| D | synopsys-dw-mshc.txt | 10 * compatible: should be
12 * #address-cells: should be 1.
13 * #size-cells: should be 0.
16 each child-node representing a supported slot. There should be atleast one
51 * clock-frequency: should be the frequency (in Hz) of the ciu clock. If this
80 - All the MSHC controller nodes should be represented in the aliases node using
|
| /linux-4.1.27/Documentation/devicetree/bindings/input/ |
| D | e3x0-button.txt | 8 - compatible: should be one of the following
12 - interrupts: should be one of the following
14 - interrupt-names: should be one of the following
|
| D | tps65218-pwrbutton.txt | 6 - compatible: should be "ti,tps65218-pwrbutton"
7 - interrupts: should be one of the following
|
| D | ti,palmas-pwrbutton.txt | 10 - compatible: should be one of the following
18 button should be kept pressed for Palmas to power off automatically.
22 which the power button should be kept pressed for Palmas to register
|
| D | twl4030-pwrbutton.txt | 9 - compatible: should be one of the following
11 - interrupts: should be one of the following
|
| /linux-4.1.27/Documentation/devicetree/bindings/pwm/ |
| D | atmel-hlcdc-pwm.txt | 7 - compatible: value should be one of the following:
10 - pinctrl-0: should contain the pinctrl states described by pinctrl
12 - #pwm-cells: should be set to 3. This PWM chip use the default 3 cells
|
| D | imx-pwm.txt | 4 - compatible : should be "fsl,<soc>-pwm" and one of the following
9 - #pwm-cells: should be 2. See pwm.txt in this directory for a description of
12 - clock-names : Clock names should include both "ipg" and "per"
|
| D | spear-pwm.txt | 4 - compatible: should be one of:
8 - #pwm-cells: should be 2. See pwm.txt in this directory for a description of
|
| D | pwm-samsung.txt | 11 - compatible : should be one of following:
22 - clock-names: should contain all following required clock names:
30 - clocks: should contain clock specifiers of all clocks, which input names
32 - #pwm-cells: should be 3. See pwm.txt in this directory for a description of
|
| D | atmel-tcb-pwm.txt | 4 - compatible: should be "atmel,tcb-pwm"
5 - #pwm-cells: should be 3. See pwm.txt in this directory for a description of
|
| D | mxs-pwm.txt | 4 - compatible: should be "fsl,imx23-pwm"
6 - #pwm-cells: should be 2. See pwm.txt in this directory for a description of
|
| D | pwm-sun4i.txt | 4 - compatible: should be one of:
8 - #pwm-cells: should be 3. See pwm.txt in this directory for a description of
|
| D | vt8500-pwm.txt | 4 - compatible: should be "via,vt8500-pwm"
6 - #pwm-cells: should be 3. See pwm.txt in this directory for a description of
|
| /linux-4.1.27/Documentation/ |
| D | remoteproc.txt | 36 Note: to use this function you should already have a valid rproc
90 This function should be used by rproc implementations during
93 implementations should then call rproc_add() to complete
122 This function should be called when the platform specific rproc
123 implementation decides to remove the rproc device. it should
128 last refcount should be decremented by calling rproc_put().
135 platform specific rproc implementation. This should not be called from a
141 These callbacks should be provided by platform-specific remoteproc
156 Every remoteproc implementation should at least provide the ->start and ->stop
158 should be provided as well.
[all …]
|
| D | email-clients.txt | 19 attachments, but then the attachments should have content-type
24 Email clients that are used for Linux kernel patches should send the
25 patch text untouched. For example, they should not modify or delete tabs
34 Email clients should not modify the character set encoding of the text.
35 Emailed patches should be in ASCII or UTF-8 encoding only.
39 Email clients should generate and maintain References: or In-Reply-To:
49 (This should be fixable.)
75 When composing the message, the cursor should be placed where the patch
76 should appear, and then pressing CTRL-R let you specify the patch file
87 "Auto wrapping" in Configuration->Preferences->Compose->Wrapping should be
[all …]
|
| D | phy.txt | 30 should provide its own implementation of of_xlate. of_xlate is used only for
41 arguments. For the dt boot case, all PHY providers should use one of the above
53 The PHY driver should create the PHY in order for other peripheral controllers
82 should contain the phy name as given in the dt data and in the case of
83 non-dt boot, it should contain the label of the PHY. The two
87 devm_phy_optional_get should be used when the phy is optional. These
91 It should be noted that NULL is a valid phy reference. All phy
111 When the driver that created the PHY is unloaded, it should destroy the PHY it
130 It should also be noted that phy_power_on and phy_power_off performs
|
| D | SubmittingPatches | 62 Patches should be based in the root kernel source directory,
76 To create a patch for multiple files, you should unpack a "vanilla",
88 the build process, and should be ignored in any diff(1)-generated
151 I.e., the patch (series) and its description should be self-contained.
181 You should also be sure to use at least the first twelve characters of the
215 The point to remember is that each patch should make an easily understood
216 change that can be verified by reviewers. Each patch should be justifiable
243 another -- in this case you should not modify the moved code at all in
250 (scripts/checkpatch.pl). Note, though, that the style checker should be
259 You should be able to justify all violations that remain in your
[all …]
|
| D | highuid.txt | 7 - kernel code should use uid_t and gid_t in kernel-private structures and
18 architectures, this should not be a problem.
21 accounting file, or if we should break it as the comments suggest
70 (it should be safe because it's always used a 32-bit integer to
|
| /linux-4.1.27/Documentation/devicetree/bindings/serial/ |
| D | altera_jtaguart.txt | 4 - compatible : should be "ALTR,juart-1.0" <DEPRECATED>
5 - compatible : should be "altr,juart-1.0"
|
| D | omap_serial.txt | 4 - compatible : should be "ti,omap2-uart" for OMAP2 controllers
5 - compatible : should be "ti,omap3-uart" for OMAP3 controllers
6 - compatible : should be "ti,omap4-uart" for OMAP4 controllers
|
| D | altera_uart.txt | 4 - compatible : should be "ALTR,uart-1.0" <DEPRECATED>
5 - compatible : should be "altr,uart-1.0"
|
| D | vt8500-uart.txt | 4 - compatible: should be "via,vt8500-uart" (for VIA/WonderMedia chips up to and
12 - clocks: shall be the input parent clock phandle for the clock. This should
|
| D | digicolor-usart.txt | 8 - compatible : should be "cnxt,cx92755-usart".
14 Note: Each UART port should have an alias correctly numbered
|
| /linux-4.1.27/Documentation/devicetree/bindings/serio/ |
| D | altera_ps2.txt | 4 - compatible : should be "ALTR,ps2-1.0". <DEPRECATED>
5 - compatible : should be "altr,ps2-1.0".
|
| /linux-4.1.27/drivers/block/paride/ |
| D | Kconfig | 18 parallel port IDE driver, otherwise you should answer M to build
32 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
37 you have such a CD-ROM drive, you should also say Y or M to "ISO
48 parallel port ATAPI disk driver, otherwise you should answer M
62 parallel port ATAPI disk driver, otherwise you should answer M
79 otherwise you should answer M to build it as a loadable module. The
103 protocol driver, otherwise you should answer M to build it as a
121 answer Y here to build in the protocol driver, otherwise you should
140 answer Y here to build in the protocol driver, otherwise you should
152 driver, otherwise you should answer M to build it as a loadable
[all …]
|
| /linux-4.1.27/Documentation/power/ |
| D | drivers-testing.txt | 8 functional system with this driver loaded. Moreover, that should be done
15 resume without the driver being tested. Thus, if possible, you should first
38 2). [As far as the STR tests are concerned, it should not matter whether or
44 Each of the above tests should be repeated several times and the STD tests
45 should be mixed with the STR tests. If any of them fails, the driver cannot be
|
| /linux-4.1.27/tools/perf/scripts/perl/Perf-Trace-Util/ |
| D | README | 7 that the core perf support for Perl calls on and should always be
11 executable; scripts wishing to do that should 'use Context.pm'.
32 You should then be able to run the normal perf make as usual.
36 Building perf with perf script Perl scripting should install this
39 You should make sure libperl and ExtUtils/Embed.pm are installed first
|
| /linux-4.1.27/Documentation/filesystems/nfs/ |
| D | rpc-cache.txt | 57 in the cache_head. cache_put should release any
60 It should then release the memory allocated by
73 contents of a cache. This should show one item,
79 bpp should be moved forward over the encoded message,
80 and *blen should be reduced to show how much free
86 cache_parse should parse this, find the item in the
121 passed which should hold the content. If the item found by _lookup
146 should be create or updated to have the given content, and the
147 expiry time should be set on that item.
170 Each cache should define a "cache_parse" method which takes a message
[all …]
|
| /linux-4.1.27/Documentation/networking/caif/ |
| D | spi_porting.txt | 43 variable indicates whether the GPIO should be asserted (HIGH) or
55 not to introduce latency). The ifc parameter should be the pointer
61 report that a transfer is completed. This function should only be
64 not to introduce latency). The ifc parameter should be the pointer
120 * SS signal. Once a edge is detected, the ss_cb() function should be
139 /* Store transfer info. For a normal implementation you should
152 /* If xfer is true then you should assert the SPI_INT to indicate to
154 * SPI. If xfer is false then you should de-assert SPI_INT to indicate
164 * Here you should release your SPI device resources.
170 /* Here you should initialize your SPI device by providing the
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/ |
| D | submitting-patches.txt | 9 1) The Documentation/ portion of the patch should be a separate patch.
18 3) The Documentation/ portion of the patch should come in the series before
35 As in the above example, the known values of "<chip>" should be
39 driver, the documentation should also include a compatible
57 3) For a series going though multiple trees, the binding patch should be
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,bcm63138.txt | 4 Boards compatible with the BCM63138 DSL System-on-a-Chip should have the
9 compatible: should be "brcm,bcm63138"
|
| /linux-4.1.27/Documentation/devicetree/bindings/power/reset/ |
| D | st-reset.txt | 4 - compatible: should be "st,<chip>-restart".
5 - st,syscfg: should be a phandle of the syscfg node.
|
| /linux-4.1.27/Documentation/devicetree/bindings/dma/ |
| D | shdma.txt | 15 - compatible: should be "renesas,shdma-mux"
16 - #dma-cells: should be <1>, see "dmas" property below
25 - compatible: should be of the form "renesas,shdma-<soc>", where <soc> should
|
| /linux-4.1.27/Documentation/devicetree/bindings/iio/magnetometer/ |
| D | ak8975.txt | 5 - compatible : should be "asahi-kasei,ak8975"
10 - gpios : should be device tree identifier of the magnetometer DRDY pin
|
| D | hmc5843.txt | 5 - compatible : should be "honeywell,hmc5843"
14 - gpios : should be device tree identifier of the magnetometer DRDY pin
|
| /linux-4.1.27/Documentation/dmaengine/ |
| D | provider.txt | 70 destination addresses, whether it should increment these addresses or
113 * channels: should be initialized as a list using the
117 - should contain a bitmask of the supported source transfer width
120 - should contain a bitmask of the supported destination transfer
124 - should contain a bitmask of the supported slave directions
141 * dev: should hold the pointer to the struct device associated
260 for the transfer being prepared, and should create a hardware
263 - Any allocation you might do should be using the GFP_NOWAIT
266 - Drivers should try to pre-allocate any memory they might need
270 - It should return a unique instance of the
[all …]
|
| /linux-4.1.27/arch/x86/realmode/rm/ |
| D | trampoline_32.S | 32 wbinvd # Needed for NUMA-Q should be harmless for others
39 cli # We should be safe anyway
|
| /linux-4.1.27/Documentation/devicetree/bindings/iio/light/ |
| D | apds9300.txt | 7 - compatible : should be "avago,apds9300"
12 - interrupt-parent : should be the phandle for the interrupt controller
|
| /linux-4.1.27/drivers/staging/media/bcm2048/ |
| D | TODO | 10 The sysfs stuff should be replaced by controls as well. A lot of the RDS
14 properties/controls should be there at all.
20 Finally this driver should probably be split up into two parts: one
|
| /linux-4.1.27/Documentation/scsi/ |
| D | dc395x.txt | 6 The driver has been tested with CD-R and CD-R/W drives. These should
8 great degree and caution should be exercised if you want to attempt
15 Problems, questions and patches should be submitted to the mailing
87 For the built in driver the parameters should be prefixed with
94 License (GPL). Please read it, before using this driver. It should be
|
| /linux-4.1.27/Documentation/ABI/obsolete/ |
| D | sysfs-bus-usb | 16 During normal use, devices should be left in the "auto"
19 free to wake up in response to I/O requests, you should
22 Device not capable of proper suspend and resume should be
|
| /linux-4.1.27/net/decnet/ |
| D | TODO | 20 [maybe this should be done at socket level... the control data in the
21 send/recvmsg() calls should simply be a vector of set/getsockopt()
24 o check MSG_CTRUNC is set where it should be.
|
| /linux-4.1.27/arch/x86/crypto/ |
| D | crc32c-pcl-intel-asm_64.S | 271 LABEL less_than_ %j # less_than_j: Length should be in
286 less_than_8: # Length should be stored in
294 less_than_4: # Length should be stored in
301 less_than_2: # Length should be stored in the MSB
306 less_than_1: # Length should be zero
|
| /linux-4.1.27/arch/avr32/boards/favr-32/ |
| D | Kconfig | 10 Specify the target rate the internal DAC should try to match. This
14 Must be within the range 32000 to 50000, which should be suitable to
|
| /linux-4.1.27/Documentation/devicetree/bindings/power/ |
| D | renesas,sysc-rmobile.txt | 23 - pm-domains: This node contains a hierarchy of PM domain nodes, which should
34 The nodes should be named by the real power area names, and thus their names
35 should be unique.
89 Hardware blocks belonging to a PM domain should contain a "power-domains"
|
| /linux-4.1.27/net/mac80211/ |
| D | Kconfig | 142 many debugging messages. It should not be selected
154 should not be selected on production systems as some
175 It should not be selected on production systems as some
185 very verbose OCB debugging messages. It should not
196 very verbose IBSS debugging messages. It should not
209 It should not be selected on production systems as those
222 It should not be selected on production systems as those
235 It should not be selected on production systems as those
248 It should not be selected on production systems as those
293 It should not be selected on production systems as those
|
| /linux-4.1.27/arch/mips/kvm/ |
| D | 00README.txt | 4 (1) KVM/MIPS should support MIPS32R2 and beyond. It has been tested on the following platforms:
16 (2) 16K Page Sizes: Both Host Kernel and Guest Kernel should have the same page size, currently at …
20 Both the host kernel and Guest kernel should have the page size set to 16K.
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | ide-cd | 9 The ide-cd driver should work with all ATAPI ver 1.2 to ATAPI 2.6 compliant
26 around should work; I usually use Workman.
69 2. You should also ensure that the iso9660 filesystem is either
74 3. The CDROM drive should be connected to the host on an IDE
90 driver, you should make sure your IDE interface uses either the
92 the CDROM drive is the only device on the IDE interface, it should
99 4. Boot the system. If the drive is recognized, you should see a
111 where X should be replaced by the letter indicating where your
114 6. You should be able to see any error messages from the driver with
128 an empty directory. You should now be able to see the contents of the
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/keystone/ |
| D | keystone.txt | 8 - compatible: All TI specific devices present in Keystone SOC should be in
10 type UART should use the specified compatible for those devices.
|
| /linux-4.1.27/drivers/memstick/ |
| D | Kconfig | 10 If you want MemoryStick support, you should say Y here and also
18 This is an option for use by developers; most people should
|
| /linux-4.1.27/Documentation/pcmcia/ |
| D | driver-changes.txt | 85 should be initialized in struct pcmcia_driver, and handle
92 * pcmcia/version.h should not be used (as of 2.6.13)
105 ioaddr_t should be replaced by unsigned int in PCMCIA card drivers.
108 The irq_mask and irq_list parameters should no longer be used in
110 determine which IRQ should be used. Therefore, link->irq.IRQInfo2
139 other drivers in Linux. You should use request_region() to mark
141 memory regions in-use. The name argument should be a pointer to
142 your driver name. Eg, for pcnet_cs, name should point to the
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | videobuf | 52 Depending on which type of buffers are being used, the driver should
59 The driver's data structure describing a V4L2 device should include a
82 parameter will be a suggested number of buffers to use; the driver should
86 device. The size parameter should be set to the expected (maximum) size
90 passed to buf_prepare(), which should set the buffer's size, width, height,
92 VIDEOBUF_NEEDS_INIT, the driver should pass it to:
98 Finally, the buf_prepare() function should set the buffer's state to
101 When a buffer is queued for I/O, it is passed to buf_queue(), which should
110 used. The driver should ensure that there is no I/O active on the buffer,
130 should be used (it should be zero in the buf_release() case), and intr
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/regulator/ |
| D | regulator.txt | 10 - regulator-always-on: boolean, regulator should never be disabled
15 For hardware which supports disabling ramp rate, it should be explicitly
29 - regulator-on-in-suspend: regulator should be on in suspend state.
30 - regulator-off-in-suspend: regulator should be off in suspend state.
31 - regulator-suspend-microvolt: regulator should be set to this voltage
|
| D | max8997-regulator.txt | 11 - reg: Specifies the i2c slave address of the pmic block. It should be 0x66.
27 property should specify atleast one voltage level (which would be a
32 'max8997,pmic-buck[1/2/5]-dvs-voltage' should be specified.
52 property should be between 0 and 7. If not specified or if out of range, the
58 Regulators: The regulators of max8997 that have to be instantiated should be
60 sub-node should be of the format as listed below.
|
| /linux-4.1.27/Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-exynos5440.txt | 10 in the decreasing order. Frequency should be in KHz units and voltage
11 should be in microvolts.
|
| /linux-4.1.27/drivers/staging/media/cxd2099/ |
| D | TODO | 10 While there's no proper fix for it, the driver should be kept in staging.
12 Patches should be submitted to: linux-media@vger.kernel.org.
|
| /linux-4.1.27/Documentation/arm/OMAP/ |
| D | omap_pm | 57 The intention is that eventually the Linux PM QoS layer should support
72 not support these functions should leave these function pointers set
73 to NULL. Drivers should use the following idiom:
80 becomes accessible. To accomplish this, driver writers should use the
99 set_max_bus_tput(), which should be called with an r argument of 0).
133 Defining CONFIG_PM should enable OPP layer for the silicon
134 and the registration of OPP table should take place automatically.
|
| /linux-4.1.27/Documentation/devicetree/bindings/mtd/ |
| D | denali-nand.txt | 4 - compatible : should be "denali,denali-nand-dt"
5 - reg : should contain registers location and length for data and reg.
|
| /linux-4.1.27/drivers/staging/media/lirc/ |
| D | TODO | 1 - All drivers should either be ported to ir-core, or dropped entirely
7 simply be converted to a normal PCI driver, but ideally it should be
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | porting.txt | 46 This should be done in the initialization function for the bus type,
107 should be created to convert from the generic object type.
126 bus driver should initialize the generic device. The most important
148 belongs to. This should be set to the bus_type that was declared
174 This should happen on buses that support hotpluggable devices.
175 If a bus driver unregisters a device, it should not immediately free
176 it. It should instead wait for the driver model core to call the
288 bus driver should define single instances of the generic methods that
306 The generic driver should be initialized with these methods before it
321 Ideally, the bus should only initialize the fields if they are not
[all …]
|
| /linux-4.1.27/Documentation/crypto/ |
| D | asymmetric-keys.txt | 50 should be given from the content of the key.
191 The owner and name fields should be set to the owning module and the name of
205 Mandatory. This should free the memory associated with the key. The
253 The owner and name fields should be set to the owning module and the name of
285 If the parser is happy with the blob, it should propose a description for
286 the key and attach it to ->description, ->type_data[0] should be set to
287 point to the subtype to be used, ->payload should be set to point to the
288 initialised data for that subtype, ->type_data[1] should point to a hex
289 fingerprint and quotalen should be updated to indicate how much quota this
290 key should account for.
[all …]
|
| /linux-4.1.27/Documentation/timers/ |
| D | timers-howto.txt | 16 code in an atomic context?" This should be followed closely by "Does
34 In general, use of mdelay is discouraged and code should
38 You should use the *sleep[_range] family of functions.
54 quirks you should be aware of.
90 that you will not trigger an interrupt; this should
|
| /linux-4.1.27/drivers/mmc/ |
| D | Kconfig | 12 If you want MMC/SD/SDIO support, you should say Y here and
19 This is an option for use by developers; most people should
|
| /linux-4.1.27/net/wireless/ |
| D | Kconfig | 43 users should better be implemented with debugfs.
82 You should disable this option unless you are both capable
91 This option should only be enabled by system integrators
107 drivers that support this feature. You should only enable this
128 a channel due to this relaxation should not allow connection from
142 If this causes your applications to misbehave you should fix your
190 Drivers should select this option if they require cfg80211's
200 Drivers should select this themselves if needed.
|
| /linux-4.1.27/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 93 consequently, this function should be called before the driver calls
114 the driver should not attempt to request any more MSI interrupts for
117 This function should be called before the driver calls request_irq(),
191 the driver should not attempt to request any more MSI interrupts for
202 This function should be used to undo the effect of pci_enable_msi_range().
205 to another device, so drivers should not cache the value of dev->irq.
243 should assign interrupts; it is invalid to fill in two entries with the
254 which should be at least 'maxvec' entries in size.
260 the driver should then call request_irq() for each 'vector' that it
267 the driver should not attempt to allocate any more MSI-X interrupts for
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/can/ |
| D | sja1000.txt | 5 - compatible : should be "nxp,sja1000".
7 - reg : should specify the chip select, address offset and size required
16 should be performed on the device. Valid value is 1, 2 or 4.
|
| /linux-4.1.27/Documentation/devicetree/bindings/leds/ |
| D | leds-gpio.txt | 4 - compatible : should be "gpio-leds".
11 Documentation/devicetree/bindings/gpio/gpio.txt. Active low LEDs should be
20 glitch should be produced where the LED momentarily turns off (or
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | vfs.txt | 133 filesystem should be mounted
136 should be shut down
138 owner: for internal VFS use: you should initialize this to THIS_MODULE in
141 next: for internal VFS use: you should initialize this to NULL
159 superblock must be locked. On failure it should return ERR_PTR(error).
255 should be synchronous or not, not all filesystems check this flag.
260 This method should be either NULL (normal UNIX filesystem
277 should wait until the write out has been completed. Optional.
375 get should not have an inode (i.e. it should be a negative
382 dentry. The "i_count" field in the inode structure should be
[all …]
|
| /linux-4.1.27/Documentation/x86/ |
| D | boot.txt | 103 memory. The boot loader should use the "INT 12h" BIOS call to verify
108 error to the user. The boot loader should therefore be designed to
111 0x90000 segment, the boot loader should make sure not to use memory
150 The first step in loading a Linux kernel should be to load the
212 following parameters should be assumed:
231 All general purpose boot loaders should write the fields marked
233 nonstandard address should fill in the fields marked (reloc); other
342 should be less than (0x200*setup_sects).
587 If a boot loader makes use of this field, it should update the
593 misaligned kernel. Therefore, a loader should typically try each
[all …]
|
| /linux-4.1.27/Documentation/hid/ |
| D | hidraw.txt | 9 Hidraw should be used if the userspace application knows exactly how to
28 Hidraw uses a dynamic major number, meaning that udev should be relied on to
31 and udev rule-dependent, applications should use libudev to locate hidraw
60 The first byte of the buffer passed to write() should be set to the report
61 number. If the device does not use numbered reports, the first byte should
62 be set to 0. The report data itself should begin at the second byte.
106 endpoint. The first byte of the supplied buffer should be set to the report
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/ieee802154/ |
| D | at86rf230.txt | 4 - compatible: should be "atmel,at86rf230", "atmel,at86rf231",
6 - spi-max-frequency: maximal bus speed, should be set to 7500000 depends
|
| /linux-4.1.27/Documentation/devicetree/bindings/crypto/ |
| D | qcom-qce.txt | 5 - compatible : should be "qcom,crypto-v5.1"
13 - dma-names : DMA request names should be "rx" and "tx"
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/rockchip/ |
| D | smp-sram.txt | 12 - compatible : should be "rockchip,rk3066-smp-sram"
14 The rest of the properties should follow the generic mmio-sram discription
|
| /linux-4.1.27/Documentation/fmc/ |
| D | carrier.txt | 8 do exactly the same for the VME carrier (actually, it should do it
26 change in layout of some fmc data structures). Device writers should
91 Please note that the carrier should read its own EEPROM memory before
94 The following fields should not be assigned, because they are filled
160 and efficient should use fmc_readl and fmc_writel. For Etherbone,
181 name argument is NULL, the carrier should reprogram the golden
186 Clients should call rhe new helper, fmc_reprogram, which both
208 called before reprogramming and the carrier should refuse them
216 same address space is carrier-specific and should only be used
284 In theory, some form of autodetection should be possible: a driver like
[all …]
|