| /linux-3.4.99/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-3.4.99/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-3.4.99/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,
|
| /linux-3.4.99/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.
|
| /linux-3.4.99/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-3.4.99/Documentation/devicetree/bindings/usb/ |
| D | usb-ehci.txt | 4 - compatible : should be "usb-ehci".
5 - reg : should contain at least address and length of the standard EHCI
9 - interrupts : one EHCI interrupt should be described here.
11 node should have "big-endian-regs" property.
13 "big-endian-desc" property should be specified.
|
| /linux-3.4.99/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 …]
|
| /linux-3.4.99/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 …]
|
| /linux-3.4.99/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.
|
| /linux-3.4.99/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-3.4.99/Documentation/serial/ |
| D | driver | 7 driver. It is not complete, any questions you have should be directed to
75 this function should return TIOCSER_TEMT, otherwise return 0.
76 If the port does not support this operation, then it should
92 If the appropriate bit is set, the signal should be driven
93 active. If the bit is clear, the signal should be driven
102 of the outputs should not be returned, since the core keeps
103 track of their state. The state information should include:
109 the port does not support CTS, DCD or DSR, the driver should
111 not available, the signal should not be indicated as active.
122 The driver should stop transmitting characters as soon as
[all …]
|
| /linux-3.4.99/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 | 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.
|
| /linux-3.4.99/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.
28 - #address-cells: should be 1.
29 - #size-cells: should be 1.
|
| /linux-3.4.99/Documentation/devicetree/bindings/serial/ |
| 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
|
| /linux-3.4.99/Documentation/devicetree/bindings/arm/ |
| D | l2cc.txt | 5 The ARM L2 cache representation in the device tree should be done as follows:
9 - compatible : should be one of:
22 without setup latency control should use a value of 0.
25 should use 0. Controllers without separate read and write Tag RAM latency
26 values should only use the first cell.
|
| /linux-3.4.99/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 …]
|
| /linux-3.4.99/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 …]
|
| /linux-3.4.99/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-3.4.99/drivers/staging/omapdrm/ |
| D | TODO | 5 . still some rough edges with flipping.. event back to userspace should
7 . where should we do eviction (detatch_pages())? We aren't necessarily
21 There should be some way to do this with less wheel-reinvention.
27 CRTC's should be disabled, and on resume the LUT should be reprogrammed
|
| /linux-3.4.99/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
|