| /linux-3.3/Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | wii.txt | 11 - model : Should be "nintendo,wii"
12 - compatible : Should be "nintendo,wii"
21 - compatible : Should be "nintendo,hollywood"
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"
[all …]
|
| D | gamecube.txt | 12 - compatible : Should be "nintendo,flipper"
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
[all …]
|
| /linux-3.3/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.3/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.3/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-3.3/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.3/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.3/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.
194 implicitly handled by input core; drivers should instead call
203 The length of the major axis of the contact. The length should be given in
215 tool. This should be understood as the size of the tool itself. The
[all …]
|
| /linux-3.3/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-3.3/arch/mips/cavium-octeon/executive/ |
| D | cvmx-helper-fpa.c | 19 * You should have received a copy of the GNU General Public License
93 * @pip_pool: Should always be CVMX_FPA_PACKET_POOL
94 * @pip_size: Should always be CVMX_FPA_PACKET_POOL_SIZE
97 * @wqe_pool: Should always be CVMX_FPA_WQE_POOL
98 * @wqe_size: Should always be CVMX_FPA_WQE_POOL_SIZE
101 * @pko_pool: Should always be CVMX_FPA_OUTPUT_BUFFER_POOL
102 * @pko_size: Should always be CVMX_FPA_OUTPUT_BUFFER_POOL_SIZE
104 * PKO Command buffers. You should at minimum have two per
106 * @tim_pool: Should always be CVMX_FPA_TIMER_POOL
107 * @tim_size: Should always be CVMX_FPA_TIMER_POOL_SIZE
[all …]
|
| /linux-3.3/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.3/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | board.txt | 10 - compatible : Should be "fsl,<board>-bcsr"
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.
47 - compatible : Should be "fsl,<board>-bcsr-gpio".
48 - reg : Should contain the address and the length of the GPIO bank
50 - #gpio-cells : Should be two. The first cell is the pin number and the
|
| /linux-3.3/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".
54 - ranges : Should be defined as specified in 1) to describe the
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.3/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-3.3/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.3/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",
|
| /linux-3.3/fs/debugfs/ |
| D | file.c | 79 * @mode: the permission that the file should have
80 * @parent: a pointer to the parent dentry for this file. This should be a
83 * @value: a pointer to the variable that the file should read to and write
131 * @mode: the permission that the file should have
132 * @parent: a pointer to the parent dentry for this file. This should be a
135 * @value: a pointer to the variable that the file should read to and write
183 * @mode: the permission that the file should have
184 * @parent: a pointer to the parent dentry for this file. This should be a
187 * @value: a pointer to the variable that the file should read to and write
236 * @mode: the permission that the file should have
[all …]
|
| /linux-3.3/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.3/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).
256 should be synchronous or not, not all filesystems check this flag.
261 This method should be either NULL (normal UNIX filesystem
281 should wait until the write out has been completed. Optional.
374 get should not have an inode (i.e. it should be a negative
381 dentry. The "i_count" field in the inode structure should be
[all …]
|
| /linux-3.3/include/linux/ |
| D | exportfs.h | 121 * @encode_fh should store in the file handle fragment @fh (using at most
124 * set, the encode_fh() should store sufficient information so that a good
127 * the filehandle fragment. encode_fh() should return the fileid_type on
134 * fragment (@fh, @fh_len). It should return a &struct dentry which refers
136 * it should return a %NULL pointer if the file was found but no acceptable
148 * @get_name should find a name for the given @child in the given @parent
149 * directory. The name should be stored in the @name (with the
151 * buffer. get_name() should return %0 on success, a negative error code
155 * @get_parent should find the parent directory for the given @child which
157 * space cannot be allocated, a %ERR_PTR should be returned.
[all …]
|
| /linux-3.3/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-3.3/drivers/staging/iio/ |
| D | events.h | 45 * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
47 * @modifier: Modifier for the channel. Should be one of enum iio_modifier.
49 * @type: Type of the event. Should be one enum iio_event_type.
69 * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
71 * @modifier: Modifier for the channel. Should be one of enum iio_modifier.
72 * @type: Type of the event. Should be one enum iio_event_type.
82 * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
84 * @type: Type of the event. Should be one enum iio_event_type.
|