| /Documentation/devicetree/bindings/display/panel/ |
| D | urt,umsh-8596md.txt | 3 Supported are LVDS versions (-11T, -19T) and parallel ones
4 (-T, -1T, -7T, -20T).
8 "urt,umsh-8596md-t",
9 "urt,umsh-8596md-1t",
10 "urt,umsh-8596md-7t",
11 "urt,umsh-8596md-11t",
12 "urt,umsh-8596md-19t",
13 "urt,umsh-8596md-20t".
|
| /Documentation/devicetree/bindings/mips/cavium/ |
| D | bootbus.txt | 32 - cavium,t-adr: A cell specifying the ADR timing (in nS).
34 - cavium,t-ce: A cell specifying the CE timing (in nS).
36 - cavium,t-oe: A cell specifying the OE timing (in nS).
38 - cavium,t-we: A cell specifying the WE timing (in nS).
40 - cavium,t-rd-hld: A cell specifying the RD_HLD timing (in nS).
42 - cavium,t-wr-hld: A cell specifying the WR_HLD timing (in nS).
44 - cavium,t-pause: A cell specifying the PAUSE timing (in nS).
46 - cavium,t-wait: A cell specifying the WAIT timing (in nS).
48 - cavium,t-page: A cell specifying the PAGE timing (in nS).
50 - cavium,t-rd-dly: A cell specifying the RD_DLY timing (in nS).
[all …]
|
| /Documentation/media/dvb-drivers/ |
| D | cards.rst | 19 DVB-S/DVB-C/DVB-T. Thus the frontend drivers are listed separately.
49 DVB-T:
58 DVB-S/C/T:
89 - Avermedia DVB-T
92 - DViCO FusionHDTV DVB-T Lite
98 - DEC 2000-T, 3000-S, 2540-T
100 - DiBcom DVB-T USB based devices:
102 - Twinhan VisionPlus VisionDTV USB-Ter DVB-T Device
103 - HAMA DVB-T USB device
105 - KWorld V-Stream XPERT DTV DVB-T USB
[all …]
|
| D | avermedia.rst | 3 HOWTO: Get An Avermedia DVB-T working under Linux
26 although the component structure of budget DVB-T cards are
61 The purpose of a simple budget digital TV card (DVB-T,C or S)
79 The Avermedia DVB-T
82 The Avermedia DVB-T is a budget PCI DVB card. It has 3 inputs:
90 Frontend of the Avermedia DVB-T is a Microtune 7202D. A timely
95 The DVB-T card is based around the BT878 chip which is a very
124 stage) for the Avermedia DVB-T are:
159 Receiving DVB-T in Australia
162 I have no experience of DVB-T in other countries other than
[all …]
|
| /Documentation/trace/ |
| D | sys-t.rst | 4 MIPI SyS-T over STP
7 The MIPI SyS-T protocol driver can be used with STM class devices to
11 In order to use the MIPI SyS-T protocol driver with your STM device,
17 # mkdir /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/
23 With Intel TH, therefore it can look like "0-sth:p_sys-t.my-policy".
30 # cat /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/protocol
31 p_sys-t
33 Now, with the MIPI SyS-T protocol driver, each policy node in the
37 # mkdir /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/default
38 # ls /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/default
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | ABI.txt | 9 break on an older device tree, but that doesn't mean the binding is
11 don't result in breakage. For instance, if a new property is added,
15 new. These guidelines aren't new, but they desperately need to be
20 1) Maintainers, don't let perfect be the enemy of good. Don't hold up a
21 binding because it isn't perfect.
26 3) Bindings can be augmented, but the driver shouldn't break when given
27 the old binding. ie. add additional properties, but don't change the
31 4) Don't submit bindings for staging or unstable. That will be decided by
|
| D | writing-bindings.txt | 12 - DO attempt to make bindings complete even if a driver doesn't support some
16 - DON'T refer to Linux or "device driver" in bindings. Bindings should be
20 defined in the DT Spec. If there isn't one, consider adding it.
25 - DON'T create nodes just for the sake of instantiating drivers. Multi-function
29 - DON'T use 'syscon' alone without a specific compatible string. A 'syscon'
36 - DO make 'compatible' properties specific. DON'T use wildcards in compatible
45 - DON'T redefine common properties. Just reference the definition and define
60 platforms don't need all devices to have 64-bit address and size.
|
| /Documentation/PCI/endpoint/function/binding/ |
| D | pci-test.txt | 8 revid : don't care
9 progif_code : don't care
10 subclass_code : don't care
12 cache_line_size : don't care
13 subsys_vendor_id : don't care
14 subsys_id : don't care
|
| /Documentation/ABI/testing/ |
| D | configfs-stp-policy-p_sys-t | 1 What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/uuid
8 tagged with this UUID in the MIPI SyS-T packet stream, to
13 What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/do_len
17 Include payload length in the MIPI SyS-T header, boolean.
18 If enabled, the SyS-T protocol encoder will include payload
23 What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/ts_interval
28 MIPI SyS-T packet metadata, if this many milliseconds have
32 What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/clocksync_interval
|
| D | sysfs-bus-siox | 3 Contact: Thorsten Scherer <t.scherer@eckelmann.de>, Uwe Kleine-König <u.kleine-koenig@pengutronix.d…
15 Contact: Thorsten Scherer <t.scherer@eckelmann.de>, Uwe Kleine-König <u.kleine-koenig@pengutronix.d…
30 Contact: Thorsten Scherer <t.scherer@eckelmann.de>, Uwe Kleine-König <u.kleine-koenig@pengutronix.d…
36 Contact: Thorsten Scherer <t.scherer@eckelmann.de>, Uwe Kleine-König <u.kleine-koenig@pengutronix.d…
44 Contact: Thorsten Scherer <t.scherer@eckelmann.de>, Uwe Kleine-König <u.kleine-koenig@pengutronix.d…
46 Read-only value. "0" means the Yth device on siox bus X isn't "connected" i.e.
51 Contact: Thorsten Scherer <t.scherer@eckelmann.de>, Uwe Kleine-König <u.kleine-koenig@pengutronix.d…
57 Contact: Thorsten Scherer <t.scherer@eckelmann.de>, Uwe Kleine-König <u.kleine-koenig@pengutronix.d…
59 Counts the number of time intervals when the read status byte doesn't yield the
64 Contact: Thorsten Scherer <t.scherer@eckelmann.de>, Uwe Kleine-König <u.kleine-koenig@pengutronix.d…
[all …]
|
| /Documentation/media/v4l-drivers/ |
| D | cx88-cardlist.rst | 74 - KWorld/VStream XPert DVB-T
90 - Hauppauge Nova-T DVB-T
94 - Conexant DVB-T reference design
102 - DViCO FusionHDTV DVB-T Plus
110 - digitalnow DNTV Live! DVB-T
130 - DViCO FusionHDTV 3 Gold-T
134 - ADS Tech Instant TV DVB-T PCI
138 - TerraTec Cinergy 1400 DVB-T
158 - WinFast DTV1000-T
178 - Hauppauge WinTV-HVR1100 DVB-T/Hybrid
[all …]
|
| /Documentation/x86/x86_64/ |
| D | boot-options.rst | 25 Don't make logs for corrected errors. All events reported
45 If your BIOS doesn't do that it's a good idea to enable though
62 Don't overwrite the bios-set CMCI threshold. This boot option
83 Don't use the IO-APIC.
86 Don't use the local APIC
89 Don't use the local APIC (alias for i386 compatibility)
95 Don't set up the APIC timer
98 Don't check the IO-APIC timer. This can work around
112 Don't use the HPET timer.
118 Don't do power saving in the idle loop using HLT, but poll for rescheduling
[all …]
|
| /Documentation/filesystems/ |
| D | hpfs.txt | 34 danger. I tried to write it so that it won't crash if check=normal on
57 also won't be able to compile linux kernel (and maybe other things) on HPFS
85 that if somebody (I don't know who?) has set "UID", "GID", "MODE" or "DEV"
86 attributes with different sizes, they won't be rewritten and changing these
87 values doesn't work.
94 chgrp symlinks but I don't know what is it good for. chmoding symlink results
99 extended attributes and partly in OS2SYS.INI. I don't want (and don't know how)
107 America where people don't care much about codepages and so multiple codepages
127 this codepage - if you don't try to do what I described above :-)
133 should work. If you have OS/2 server, use only read-only mode. I don't know how
[all …]
|
| D | efivarfs.txt | 9 than a single page, sysfs isn't the best interface for this.
16 mount -t efivarfs none /sys/firmware/efi/efivars
21 as immutable files. This doesn't prevent removal - "chattr -i" will work -
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 18 result for an operation ... it doesn't indicate that anything is wrong
19 at all, just that the outcome wasn't on the "golden path".
36 cases (unless the hardware doesn't provide unique fault reports).
78 specific than ENXIO, implying the problem isn't with the
85 Returned by any component that can't allocate memory when
90 of a transfer didn't get an ACK. While it might just mean
99 that it doesn't, or can't, support.
102 doesn't support SMBus block transfers is asked to execute
107 Similarly, if an I2C adapter can't execute all legal I2C
109 transaction it can't. (These limitations can't be seen in
|
| D | ten-bit-addresses.rst | 20 * Not all bus drivers support 10-bit addresses. Some don't because the
21 hardware doesn't support them (SMBus doesn't require 10-bit address
22 support for example), some don't because nobody bothered adding the
|
| /Documentation/process/ |
| D | management-style.rst | 14 to do with reality. It started as a lark, but that doesn't mean that it
27 making it painfully obvious to the questioner that we don't have a clue
49 (Corollary:if the people you manage don't know the details better than
71 things that can't be undone. Don't get ushered into a corner from which
83 you made a year ago wasn't a big decision after all, since it could be
93 wasn't worthwhile after all can be hard on the poor lowly engineers
101 admitting up-front that you don't have a friggin' clue, and telling
105 to admit that you are stupid when you haven't **yet** done the really
113 not. After all, if **they** aren't certain whether it's a good idea, you
114 sure as hell shouldn't encourage them by promising them that what they
[all …]
|
| /Documentation/i2c/busses/ |
| D | i2c-ali15x3.rst | 26 The force_addr parameter is useful for boards that don't set the address in
28 lspci. Don't use this unless the driver complains that the base address is
61 - Gigabyte GA-5AX (Generally doesn't work because the BIOS doesn't
85 "ali15x3: Error: Can't detect ali15x3!"
92 The driver won't work if it can't find the M7101 device.
97 The whole M7101 device has to be enabled for the SMB to work. You can't
113 registers. It doesn't use the ACPI region.
|
| /Documentation/sphinx/ |
| D | automarkup.py | 15 # other way. Sphinx doesn't like a lot of stuff right after a
17 # bit tries to restrict matches to things that won't create trouble.
26 # just don't even try with these names.
38 t = node.astext()
41 for m in RE_function.finditer(t):
46 repl.append(nodes.Text(t[done:m.start()]))
78 if done < len(t):
79 repl.append(nodes.Text(t[done:]))
|
| /Documentation/media/uapi/mediactl/ |
| D | media-types.rst | 62 - Unknown entity. That generally indicates that a driver didn't
170 pad(s). Pixel encoding conversion includes but isn't limited
257 .. _MEDIA-INTF-T-DVB-FE:
258 .. _MEDIA-INTF-T-DVB-DEMUX:
259 .. _MEDIA-INTF-T-DVB-DVR:
260 .. _MEDIA-INTF-T-DVB-CA:
261 .. _MEDIA-INTF-T-DVB-NET:
262 .. _MEDIA-INTF-T-V4L-VIDEO:
263 .. _MEDIA-INTF-T-V4L-VBI:
264 .. _MEDIA-INTF-T-V4L-RADIO:
[all …]
|
| /Documentation/networking/ |
| D | arcnet.txt | 3 and cabling information if you're like many of us and didn't happen to get a
16 you test this and get it working. Or if you don't. Or anything.
20 didn't even have to install the patch. <sigh>
31 If you don't e-mail me about your success/failure soon, I may be forced to
32 start SINGING. And we don't want that, do we?
51 individual chipset drivers, and the source files aren't quite so packed with
53 Avery, because I didn't want to completely rewrite it.
99 oak.oakland.edu:/simtel/msdos/pktdrvr. It won't work perfectly on a 386+
100 without patches, though, and also doesn't like several cards. Fixed
101 versions are available on my WWW page, or via e-mail if you don't have WWW
[all …]
|
| /Documentation/block/ |
| D | biovecs.rst | 24 normal code doesn't have to deal with bi_bvec_done.
49 * Before, iterating over bios was very awkward when you weren't processing
52 wouldn't necessarily be the same size, the old code was tricky convoluted -
73 * Splitting bios is now much simpler. The old bio_split() didn't even work on
77 Care must be taken to ensure the biovec isn't freed while the split bio is
104 * bi_vcnt can't be trusted or relied upon by driver code - i.e. anything that
105 doesn't actually own the bio. The reason is twofold: firstly, it's not
111 So, don't use bi_vcnt anymore.
116 more importantly stacked drivers don't have to deal with both their own bio
126 shouldn't use them because the bio may have been split before it reached the
|
| /Documentation/driver-api/usb/ |
| D | persist.rst | 32 For many sorts of devices this behavior doesn't matter in the least.
46 Loss of power isn't the only mechanism to worry about. Anything that
53 entirely the BIOS's fault, but that doesn't do _you_ any good unless
64 the system can't be suspended at all. (All right, it _can_ be
65 suspended -- but it will crash as soon as it wakes up, which isn't
80 "persist" attribute is set. It doesn't try to resume the device; that
81 can't work once the power session is gone. Instead it issues a USB
113 doesn't even exist, so you only have to worry about setting it for
142 to make sure the USB device hasn't been changed; that is, the same
144 aren't guaranteed to be 100% accurate.
[all …]
|
| /Documentation/ia64/ |
| D | serial.rst | 31 and "console=" arguments. Without an HCDP, device names didn't
54 EFI knows what your console devices are, but it doesn't tell the
58 multiple simultaneous consoles and doesn't tell the kernel which
65 card) as the console. Then you don't need to tell Linux
74 NOTE: Don't assume that a serial console device will be /dev/ttyS0.
82 The kernel can't start using a serial console until it knows where
113 console device even when it isn't explicitly selected.
123 - If you don't have an HCDP, the kernel doesn't know where
134 "login:" prompt, but can't login as root:
|
| /Documentation/admin-guide/aoe/ |
| D | status.sh | 8 format="%8s\t%8s\t%8s\n"
14 # Suse 9.1 Pro doesn't put /sys in /etc/mtab
|