| /kernel/linux/linux-5.10/drivers/gpu/drm/radeon/ |
| D | radeon_agp.c | 49 /* Intel E7505 Memory Controller Hub / RV350 AR [Radeon 9600XT] Needs AGPMode 4 (deb #515326) */
51 /* Intel 82865G/PE/P DRAM Controller/Host-Hub / Mobility 9800 Needs AGPMode 4 (deb #462590) */
53 …/* Intel 82865G/PE/P DRAM Controller/Host-Hub / RV280 [Radeon 9200 SE] Needs AGPMode 4 (lp #300304…
56 /* Intel 82855PM Processor to I/O Controller / Mobility M6 LY Needs AGPMode 1 (deb #467235) */
59 /* Intel 82855PM host bridge / Mobility 9600 M10 RV350 Needs AGPMode 1 (lp #195051) */
62 …/* Intel 82855PM host bridge / RV250/M9 GL [Mobility FireGL 9000/Radeon 9000] needs AGPMode 1 (Thi…
65 /* Intel 82855PM host bridge / Mobility M7 needs AGPMode 1 */
68 /* Intel 82855PM host bridge / FireGL Mobility T2 RV350 Needs AGPMode 2 (fdo #20647) */
71 /* Intel 82855PM host bridge / Mobility M9+ / VaioPCG-V505DX Needs AGPMode 2 (fdo #17928) */
74 /* Intel 82855PM Processor to I/O Controller / Mobility M9+ Needs AGPMode 8 (phoronix forum) */
[all …]
|
| /kernel/linux/linux-5.10/tools/usb/ |
| D | hcd-tests.sh | 7 # - out, in: out needs 'bulk sink' firmware, in needs 'bulk src'
8 # - iso-out, iso-in: out needs 'iso sink' firmware, in needs 'iso src'
9 # - halt: needs bulk sink+src, tests halt set/clear from host
10 # - unlink: needs bulk sink and/or src, test HCD unlink processing
11 # - loop: needs firmware that will buffer N transfers
260 # FIXME someone needs to write and merge a version of this
|
| /kernel/linux/linux-5.10/drivers/vhost/ |
| D | Kconfig | 6 This option is selected by any driver which needs to support
13 This option is selected by any driver which needs to access
20 This option is selected by any driver which needs to access
36 module itself which needs to be loaded in guest kernel.
|
| /kernel/linux/linux-5.10/include/linux/usb/ |
| D | quirks.h | 30 /* device needs a pause during initialization, after we read the device
61 * Device needs to be disconnected before suspend to prevent spurious
66 /* Device needs a pause after every control message. */
69 /* Hub needs extra delay after resetting its port. */
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | ti_wilink_st.h | 54 * @reserve: the number of bytes ST needs to reserve in the skb being
104 * This needs to be protected, hence the lock inside wakeup func.
114 * is received, the states, count and the skb needs to be maintained.
116 * @txq: the list of skbs which needs to be sent onto the TTY.
117 * @tx_waitq: if the chip is not in AWAKE state, the skbs needs to be queued
118 * up in here, PM(WAKEUP_IND) data needs to be sent and then the skbs
120 * Needs locking too.
124 * needs to be downloaded to initialize chip side ST.
225 * @uim_pid: KIM needs to communicate with UIM to request to install
291 * Each such action needs to be parsed by the KIM and
[all …]
|
| D | dma-buf.h | 122 * This call may sleep, e.g. when the backing storage first needs to be
186 * backing storage. The exporter also needs to ensure that cpu access is
190 * data (e.g. when the exporter needs to copy the data to temporary
208 * needs to be restarted.
226 * -ERESTARTSYS or -EINTR when the call has been interrupted and needs
236 * Note that the mapping needs to be incoherent, userspace is expected
244 * If an exporter needs to manually flush caches and hence needs to fake
245 * coherency for mmap support, it needs to be able to zap all the ptes
246 * pointing at the backing storage. Now linux mm needs a struct
457 * kernel side. For example, an exporter that needs to keep a dmabuf ptr
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | atmel,at91-pinctrl.txt | 89 PULL_UP (1 << 0): indicate this pin needs a pull up.
90 MULTIDRIVE (1 << 1): indicate this pin needs to be configured as multi-drive.
92 DEGLITCH (1 << 2): indicate this pin needs deglitch.
93 PULL_DOWN (1 << 3): indicate this pin needs a pull down.
94 DIS_SCHMIT (1 << 4): indicate this pin needs to the disable schmitt trigger.
104 DEBOUNCE (1 << 16): indicate this pin needs debounce.
|
| /kernel/linux/linux-5.10/Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.rst | 24 close preparations) can simply go. Device specific stuff needs to go to the
42 Needs the status-callback defined, otherwise returns 0
45 Needs the bootstatus member properly set. Make sure it is 0 if you
65 It needs get_timeleft() callback to be defined. Otherwise it
177 used. This needs to be converted by initializing the status variable of the
187 The module parameter itself needs to stay, everything else related to nowayout
210 The entry for the driver now needs to select WATCHDOG_CORE:
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | botching-up-ioctls.rst | 70 needs a new driver feature flags.
92 * The ioctl must check for array overflows. Also it needs to check for
165 and suiting to your needs.
172 the given GPU platforms. This means a driver needs to expose tons of handles
178 needs to be shared across processes - fd-passing over unix domain sockets
194 command submission ioctl. But then if objects are shareable userspace needs
205 Not every problem needs a new ioctl:
217 maybe only your testsuite needs this interface, and then debugfs with its
|
| /kernel/linux/linux-5.10/sound/hda/ |
| D | hdac_component.c | 28 * driver that needs the interaction with graphics driver.
61 * needs the interaction with graphics driver.
116 * driver that needs the interaction with graphics driver.
151 * driver that needs the interaction with graphics driver.
247 * driver that needs the interaction with graphics driver.
272 * driver that needs the interaction with graphics driver.
278 * binding with the DRM component. Each caller needs to sync via master_bind
327 * driver that needs the interaction with graphics driver.
|
| /kernel/linux/linux-5.10/arch/ia64/lib/ |
| D | io.c | 9 * This needs to be optimized.
24 * This needs to be optimized.
39 * This needs to be optimized.
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/ |
| D | TODO | 69 7. A single AtomISP driver needs to be implemented to support both
76 8. The file structure needs to get tidied up to resemble a normal Linux
79 9. Lots of the midlayer glue. unused code and abstraction needs removing.
86 Such IOCTL interface needs more documentation. The better would
110 particular, the user space API needs to support V4L2 controls as
|
| /kernel/linux/linux-5.10/include/soc/fsl/ |
| D | dpaa2-fd.h | 111 * @addr: the address needs to be set in frame descriptor
132 * @frc: the frame context needs to be set in frame descriptor
174 * @flc_addr: the flow context needs to be set in frame descriptor
204 * @len: the length needs to be set in frame descriptor
225 * @offset: the offset needs to be set in frame descriptor
249 * @format: the format needs to be set in frame descriptor
487 * @addr: the address needs to be set in frame list entry
509 * @frc: the frame context needs to be set in frame list entry
551 * @flc_addr: the flow context needs to be set in frame list entry
582 * @len: the length needs to be set in frame list entry
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | sync_file.rst | 47 When a driver needs to send an out-fence userspace it creates a sync_file.
54 first step, next it needs to install an fd on sync_file->file. So it gets an
65 If the creation process fail, or the sync_file needs to be released by any
71 When userspace needs to send an in-fence to the driver it passes file descriptor
|
| /kernel/linux/linux-5.10/kernel/power/ |
| D | console.c | 34 * @required: if true, caller needs VT switch at suspend/resume time
42 * the argument. If any loaded driver needs VT switching, or the
73 * pm_vt_switch_unregister - stop tracking a device's VT switching needs
100 * 3) any registered driver indicates it needs a VT switch
|
| /kernel/linux/linux-5.10/drivers/mmc/host/ |
| D | sdhci-bcm-kona.c | 83 * Back-to-Back register write needs a delay of 1ms at bootup (min 10uS) in sdhci_bcm_kona_sd_reset()
84 * Back-to-Back writes to same register needs delay when SD bus clock in sdhci_bcm_kona_sd_reset()
108 * Back-to-Back register write needs a delay of 1ms at bootup (min 10uS) in sdhci_bcm_kona_sd_init()
109 * Back-to-Back writes to same register needs delay when SD bus clock in sdhci_bcm_kona_sd_init()
120 * IP to function properly the bit 0 of CORESTAT register needs to be set/reset
130 * Back-to-Back register write needs a delay of min 10uS. in sdhci_bcm_kona_sd_card_emulate()
131 * Back-to-Back writes to same register needs delay when SD bus clock in sdhci_bcm_kona_sd_card_emulate()
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | highmem.rst | 17 at all times. This means the kernel needs to start using temporary mappings of
56 physical pages into a contiguous virtual space. It needs global
59 * kmap(). This permits a short duration mapping of a single page. It needs
131 * Linux needs a page-frame structure for each page in the system and the
136 worth of pages; the kernel, however, needs to store more than just
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | xfs-delayed-logging-design.rst | 100 but only one of those copies needs to be there - the last one "D", as it
173 running. For example, a transaction has object A locked and modified, but needs
238 region state that needs to be placed into the headers during the log write.
271 committed item tracking needs it's own locks, lists and state fields in the log
348 buffer and log vector attached to each log item needs to be attached to the
448 checkpoint sequence needs to be committed before they can continue. As a
449 result, the code that forces the log to a specific LSN now needs to ensure that
523 1MB of log space consumed (512 bytes per 32k) and the reservation needs to be
525 reservation needs to be made before the checkpoint is started, and we need to
529 A static reservation needs to manipulate the log grant counters - we can take a
[all …]
|
| D | xfs-self-describing-metadata.rst | 78 As a primary concern, self describing metadata needs some form of overall
89 could be used, it is more than sufficient for our needs and has relatively
95 Self describing metadata needs to contain enough information so that the
97 look at any other metadata. This means it needs to contain location information.
122 Self describing metadata also needs to contain some indication of when it was
165 For read verification, the caller needs to specify the expected type of metadata
168 marks the object being read as EFSCORRUPTED. The caller needs to catch this
169 error (same as for IO errors), and if it needs to take special action due to a
191 A typical on-disk structure needs to contain the following information::
352 repair will probably complain about it - but it needs to be fixed.
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 10 # Kconfig needs to address. We iterate over what Kconfig needs to address
11 # by stepping through the questions it needs to address sequentially.
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-platform-kim | 21 UART configurations, so the baud-rate needs to be set
47 by the sysfs_notify. The value would be '1' when UART needs
49 is no more required and needs to be closed.
|
| /kernel/linux/linux-5.10/drivers/firmware/efi/ |
| D | x86_fake_mem.c | 22 * Given that efi_fake_memmap() needs to perform memblock in efi_fake_memmap_early()
23 * allocations it needs to run after e820__memblock_setup(). in efi_fake_memmap_early()
25 * address range that potentially needs to mark the memory as in efi_fake_memmap_early()
|
| /kernel/linux/linux-5.10/Documentation/networking/dsa/ |
| D | configuration.rst | 91 # The master interface needs to be brought up before the slave ports.
104 # The master interface needs to be brought up before the slave ports.
131 # The master interface needs to be brought up before the slave ports.
175 # The master interface needs to be brought up before the slave ports.
219 # The master interface needs to be brought up before the slave ports.
260 # The master interface needs to be brought up before the slave ports.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | writing_usb_driver.rst | 24 needs to be created. Some vendors are open with their USB protocols and
35 different pieces and what needs to be done to customize it to your
49 The first thing a Linux USB driver needs to do is register itself with
80 this user-space interaction. The skeleton driver needs this kind of
104 When the driver is unloaded from the system, it needs to deregister
145 The driver now needs to verify that this device is actually one that it
156 function is called with the device pointer. The driver needs to clean
261 it. It needs to be able to shut down any current reads and writes and
|
| /kernel/linux/linux-5.10/arch/arm/kernel/ |
| D | io.c | 43 * This needs to be optimized.
59 * This needs to be optimized.
75 * This needs to be optimized.
|