| /Linux-v5.4/arch/powerpc/platforms/cell/spufs/ |
| D | hw_ops.c | 27 struct spu_problem __iomem *prob = spu->problem; in spu_hw_mbox_read()
43 return in_be32(&ctx->spu->problem->mb_stat_R); in spu_hw_mbox_stat_read()
53 stat = in_be32(&spu->problem->mb_stat_R); in spu_hw_mbox_stat_poll()
85 struct spu_problem __iomem *prob = spu->problem; in spu_hw_ibox_read()
106 struct spu_problem __iomem *prob = spu->problem; in spu_hw_wbox_write()
126 out_be32(&ctx->spu->problem->signal_notify1, data); in spu_hw_signal1_write()
131 out_be32(&ctx->spu->problem->signal_notify2, data); in spu_hw_signal2_write()
178 return in_be32(&ctx->spu->problem->spu_npc_RW); in spu_hw_npc_read()
183 out_be32(&ctx->spu->problem->spu_npc_RW, val); in spu_hw_npc_write()
188 return in_be32(&ctx->spu->problem->spu_status_R); in spu_hw_status_read()
[all …]
|
| D | switch.c | 83 struct spu_problem __iomem *prob = spu->problem; in check_spu_isolate()
203 struct spu_problem __iomem *prob = spu->problem; in save_spu_runcntl()
222 struct spu_problem __iomem *prob = spu->problem; in save_spu_status()
296 struct spu_problem __iomem *prob = spu->problem; in do_mfc_mssync()
368 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querymask()
379 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querytype()
390 struct spu_problem __iomem *prob = spu->problem; in save_ppu_tagstatus()
503 struct spu_problem __iomem *prob = spu->problem; in save_spu_npc()
587 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb_stat()
597 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb()
[all …]
|
| /Linux-v5.4/fs/afs/ |
| D | addr_list.c | 72 const char *problem; in afs_parse_text_addrs() local
90 problem = "nul"; in afs_parse_text_addrs()
99 problem = "brace1"; in afs_parse_text_addrs()
104 problem = "brace2"; in afs_parse_text_addrs()
160 problem = "family"; in afs_parse_text_addrs()
166 problem = "nostop"; in afs_parse_text_addrs()
179 problem = "port"; in afs_parse_text_addrs()
186 problem = "pval"; in afs_parse_text_addrs()
194 problem = "weird"; in afs_parse_text_addrs()
212 problem, p - text, (int)len, (int)len, text); in afs_parse_text_addrs()
[all …]
|
| /Linux-v5.4/arch/powerpc/platforms/cell/ |
| D | spu_manage.c | 63 iounmap(spu->problem); in spu_unmap()
146 spu->problem = spu_map_prop_old(spu, node, "problem"); in spu_map_device_old()
147 if (!spu->problem) in spu_map_device_old()
225 ret = spu_map_resource(spu, 1, (void __iomem**)&spu->problem, in spu_map_device()
250 spu->problem_phys, spu->problem); in spu_map_device()
332 spu->local_store, spu->problem, spu->priv1, in of_create_spu()
|
| /Linux-v5.4/Documentation/translations/zh_CN/ |
| D | SecurityBugs | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | IRQ.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | io_ordering.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | sparse.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /Linux-v5.4/Documentation/process/ |
| D | 3.Early-stage.rst | 13 Specifying the problem
17 clear description of the problem to be solved. In some cases, this step is
19 example. In others, though, it is tempting to confuse the real problem
31 immediate problem. To the wider kernel community, though, it was seen as a
53 the right solution to the problem than they were with a specific module.
54 The moral of the story is to focus on the problem - not a specific solution
61 - What, exactly, is the problem which needs to be solved?
63 - Who are the users affected by this problem? Which use cases should the
66 - How does the kernel fall short in addressing that problem now?
78 - It may well be that the problem is addressed by the kernel in ways which
[all …]
|
| /Linux-v5.4/Documentation/networking/device_drivers/3com/ |
| D | vortex.txt | 198 decision. If you think that Tx checksums are causing a problem, you
217 "Variables to work-around the Compaq PCI BIOS32 problem"....
320 On a side note, adding HAS_NWAY seems to share a problem with the
335 If autonegotiation is a problem, you may need to specify "speed
345 Maintainers find that accurate and complete problem reports are
348 the bottom of the problem.
350 If you believe you have a driver problem here are some of the
353 - Is it really a driver problem?
359 - OK, it's a driver problem.
366 problem. If it's a kernel crash then you should refer to the
[all …]
|
| /Linux-v5.4/Documentation/translations/zh_CN/arm64/ |
| D | tagged-pointers.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | legacy_instructions.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | memory.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | silicon-errata.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| D | booting.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /Linux-v5.4/arch/powerpc/platforms/ps3/ |
| D | spu.c | 124 unsigned long problem, unsigned long ls, unsigned long shadow, in _dump_areas() argument
129 pr_debug("%s:%d: problem: %lxh\n", func, line, problem); in _dump_areas()
178 iounmap(spu->problem); in spu_unmap()
210 spu->problem = ioremap(spu->problem_phys, in setup_areas()
213 if (!spu->problem) { in setup_areas()
230 (unsigned long)spu->problem, (unsigned long)spu->local_store, in setup_areas()
|
| /Linux-v5.4/Documentation/core-api/ |
| D | debug-objects.rst | 78 problem before the real initialization of the object happens. E.g. it
101 problem before the real initialization of the object happens. E.g. it
125 problem before the real activation of the object happens. E.g. it can
164 provided by the caller. The fixup function can correct the problem
180 fixup function can correct the problem before the real free of the
196 fixup function can correct the problem by calling debug_object_init
213 This function is called from the debug code whenever a problem in
231 This function is called from the debug code whenever a problem in
259 This function is called from the debug code whenever a problem in
272 This function is called from the debug code whenever a problem in
[all …]
|
| /Linux-v5.4/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 29 # But that is a problem, because this means that in order to determine
37 # obvious that an easy to solution to this problem should just be the removal
43 # CORE also consist of a solution to this recursive problem.
|
| /Linux-v5.4/Documentation/networking/ |
| D | skfp.txt | 90 is not there, then you may have a hardware problem or PCI
95 Some COMPAQ machines have a problem with PCI under
104 forwarding or there is a problem with the routing table
108 If your problem is not listed here, please contact our
217 document for details about this problem.
|
| /Linux-v5.4/Documentation/translations/zh_CN/arm/ |
| D | Booting | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /Linux-v5.4/Documentation/power/ |
| D | basic-pm-debugging.rst | 112 that there is a problem with the tasks freezer subsystem that should be
128 make sure to report the problem with the driver.
136 If the "platform" test fails, there is a problem with the handling of the
142 work (of course, this only may be an issue on SMP systems) and the problem
149 the problem is most probably hardware-related and serious, so it should be
154 indicates a serious problem that very well may be related to the hardware, but
163 probably is a problem with a driver statically compiled into the kernel and you
165 individually. Otherwise, there is a problem with a modular driver and you can
175 before hibernation, and please report the problem with it(them).
209 techniques to find the problem. First, if there is a serial port in your box,
|
| /Linux-v5.4/Documentation/arm/nwfpe/ |
| D | notes.rst | 4 There seems to be a problem with exp(double) and our emulator. I haven't
25 This code will cause this problem:
|
| D | nwfpe.rst | 44 attempting to isolate the problem. Please report them, but don't
45 expect quick action. Bugs still exist. The problem remains in isolating
47 problem are a godsend.
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | sysfs-tagging.txt | 7 The problem. Network devices show up in sysfs and with the network
11 To avoid that problem and allow existing applications in network
|
| /Linux-v5.4/Documentation/ide/ |
| D | ChangeLog.ide-cd.1994-2004 | 3 * 1.01 Nov 2, 1994 -- Fixed problem with starting request in
24 * Aztech drives, which seem to have the same problem.
84 * Work around sporadic Sony55e audio play problem.
86 * problem with "hde=cdrom" with no drive present. -ml
241 * - Fixed a problem with WPI CDS-32X drive - it
255 * - Fix small problem with ide_cdrom_capacity
257 * 4.59 Aug 11, 2000 - Fix changer problem in cdrom_read_toc, we weren't
|
