Searched +full:work +full:- +full:around (Results 1 – 25 of 197) sorted by relevance
12345678
| /Documentation/process/ |
| D | 6.Followthrough.rst | 9 developers can make is to conclude that their work is now done. In truth,
11 with, possibly, quite a bit of work yet to be done.
16 code. You, as the author of that code, will be expected to work with the
23 ----------------------
31 - If you have explained your patch well, reviewers will understand its
35 Many of the changes you may be asked to make - from coding style tweaks
36 to substantial rewrites - come from the understanding that Linux will
37 still be around and under development a decade from now.
39 - Code review is hard work, and it is a relatively thankless occupation;
47 - Similarly, code reviewers are not trying to promote their employers'
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | design-patterns.rst | 35 return -ENOMEM;
36 spin_lock_init(&foo->lock);
43 state around to all functions that need access to the state and its members.
46 pass around a pointer to struct foo like this::
69 Continuing on the above example we add an offloaded work::
78 static void foo_work(struct work_struct *work)
80 struct foo *foo = container_of(work, struct foo, offload);
89 queue_work(foo->wq, &foo->offload);
97 foo->wq = create_singlethread_workqueue("foo-wq");
98 INIT_WORK(&foo->offload, foo_work);
[all …]
|
| /Documentation/devicetree/bindings/phy/ |
| D | mediatek,mt7988-xfi-tphy.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/phy/mediatek,mt7988-xfi-tphy.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MediaTek MT7988 XFI T-PHY
10 - Daniel Golle <daniel@makrotopia.org>
13 The MediaTek XFI SerDes T-PHY provides the physical SerDes lanes
15 MediaTek's 10G-capabale MT7988 SoC.
20 const: mediatek,mt7988-xfi-tphy
27 - description: XFI PHY clock
[all …]
|
| /Documentation/scsi/ |
| D | scsi-changer.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 This is for *real* Jukeboxes. It is *not* supported to work with
11 common small CD-ROM changers, neither one-lun-per-slot SCSI changers
19 -------------------
21 First some words about how changers work: A changer has 2 (possibly
24 later may be anything, a MOD, a CD-ROM, a tape or whatever. For the
25 changer device this is a "don't care", he *only* shuffles around the
29 The SCSI changer model is complex, compared to - for example - IDE-CD
34 media transport this one shuffles around the media, i.e. the
42 CD-ROM / Tape / whatever drive.
[all …]
|
| D | ChangeLog.sym53c8xx | 1 Sat May 12 12:00 2001 Gerard Roudier (groudier@club-internet.fr)
2 * version sym53c8xx-1.7.3c
3 - Ensure LEDC bit in GPCNTL is cleared when reading the NVRAM.
4 Fix sent by Stig Telfer <stig@api-networks.com>.
5 - Backport from SYM-2 the work-around that allows to support
7 - Check that we received at least 8 bytes of INQUIRY response
9 - Define scsi_set_pci_device() as nil for kernel < 2.4.4.
10 - + A couple of minor changes.
12 Sat Apr 7 19:30 2001 Gerard Roudier (groudier@club-internet.fr)
13 * version sym53c8xx-1.7.3b
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | fsl,plldig.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Wen He <wen.he_1@nxp.com>
19 const: fsl,ls1028a-plldig
27 '#clock-cells':
30 fsl,vco-hz:
34 the requested frequency. To work around this restriction the user may specify
41 - compatible
42 - reg
[all …]
|
| /Documentation/usb/ |
| D | ohci.rst | 5 23-Aug-2002
7 The "ohci-hcd" driver is a USB Host Controller Driver (HCD) that is derived
8 from the "usb-ohci" driver from the 2.4 kernel series. The "usb-ohci" code
20 - improved robustness; bugfixes; and less overhead
21 - supports the updated and simplified usbcore APIs
22 - interrupt transfers can be larger, and can be queued
23 - less code, by using the upper level "hcd" framework
24 - supports some non-PCI implementations of OHCI
25 - ... more
27 The "ohci-hcd" driver handles all USB 1.1 transfer types. Transfers of all
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | mdio.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andrew Lunn <andrew@lunn.ch>
11 - Florian Fainelli <f.fainelli@gmail.com>
12 - Heiner Kallweit <hkallweit1@gmail.com>
17 bus. These should follow the generic ethernet-phy.yaml document, or
22 pattern: '^mdio(-(bus|external))?(@.+|-([0-9]+))?$'
24 "#address-cells":
27 "#size-cells":
[all …]
|
| /Documentation/fb/ |
| D | vesafb.rst | 13 impossible; BIOS calls work in real mode only. VESA BIOS Extensions
20 * You can run XF68_FBDev on top of /dev/fb0 (=> non-accelerated X11
22 * Most important: boot logo :-)
33 Documentation/admin-guide/svga.rst for details.
74 If this does not work, this might be because your BIOS does not support
81 "vga=mode-number" you have to transform the numbers to decimal.
82 2. Note: Some newer versions of LILO appear to work with those hex values,
88 XF68_FBDev should work just fine, but it is non-accelerated. Running
89 another (accelerated) X-Server like XF86_SVGA might or might not work.
90 It depends on X-Server and graphics board.
[all …]
|
| /Documentation/core-api/ |
| D | workqueue.rst | 17 When such an asynchronous execution context is needed, a work item
22 While there are work items on the workqueue the worker executes the
23 functions associated with the work items one after the other. When
24 there is no work item left on the workqueue the worker becomes idle.
25 When a new work item gets queued, the worker begins executing again.
33 thread system-wide. A single MT wq needed to keep around the same
43 while an ST wq one for the whole system. Work items had to compete for
45 including proneness to deadlocks around the single execution context.
60 * Use per-CPU unified worker pools shared by all wq to provide
72 abstraction, the work item, is introduced.
[all …]
|
| D | idr.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
18 only ID allocation, and as a result is much more memory-efficient.
43 we will work with you to address your needs.
50 either use the callback-based idr_for_each() or the
51 iterator-style idr_for_each_entry(). You may need to use
65 to the IDR being unable to allocate memory. To work around this,
69 .. kernel-doc:: include/linux/idr.h
75 .. kernel-doc:: lib/idr.c
81 .. kernel-doc:: include/linux/idr.h
83 .. kernel-doc:: lib/idr.c
|
| /Documentation/nvme/ |
| D | feature-and-quirk-policy.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 - the NVMe Base specification
21 - various Command Set specifications (e.g. NVM Command Set)
22 - various Transport specifications (e.g. PCIe, Fibre Channel, RDMA, TCP)
23 - the NVMe Management Interface specification
32 useful or suitable for specific use-cases. It is important to note that Linux
44 on-wire protocol, does not contradict any of the NVMe specifications.
47 3. Has a clear, indisputable value-proposition and a wide consensus across
53 It is strongly recommended to work with the Linux NVMe and block layer
63 of the standards. Linux uses identifier-based quirks to work around such
|
| /Documentation/devicetree/bindings/spi/ |
| D | renesas,sh-msiof.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/spi/renesas,sh-msiof.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Geert Uytterhoeven <geert+renesas@glider.be>
13 - $ref: spi-controller.yaml#
18 - items:
19 - const: renesas,msiof-sh73a0 # SH-Mobile AG5
20 - const: renesas,sh-mobile-msiof # generic SH-Mobile compatible
22 - items:
[all …]
|
| /Documentation/security/ |
| D | sak.rst | 15 providing SAK. One is the ALT-SYSRQ-K sequence. You shouldn't use
20 ``loadkeys``. This will work whether or not sysrq support is compiled
28 What key sequence should you use? Well, CTRL-ALT-DEL is used to reboot
29 the machine. CTRL-ALT-BACKSPACE is magical to the X server. We'll
30 choose CTRL-ALT-PAUSE.
57 # ls -l /proc/[0-9]*/fd/* | grep console
58 l-wx------ 1 root root 64 Mar 18 00:46 /proc/579/fd/0 -> /dev/console
63 root 579 0.0 0.1 1088 436 ? S 00:43 0:00 gpm -t ps/2
66 be closing standard input. You can work around this by finding the
90 applications to malfunction - test everything well.
|
| /Documentation/doc-guide/ |
| D | contributing.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Documentation is an important part of any software-development project.
8 developers work more effectively. Without top-quality documentation, a lot
9 of time is wasted in reverse-engineering the code and making avoidable
23 ---------------------------
35 people ignore them, and they will never notice when their work adds new
36 ones. For this reason, eliminating warnings is one of the highest-priority
59 - Resource-managed devfreq_register_notifier()
61 - Resource-managed devfreq_unregister_notifier()
70 - Resource-managed devfreq_register_notifier()
[all …]
|
| /Documentation/sphinx/ |
| D | automarkup.py | 1 # SPDX-License-Identifier: GPL-2.0
4 # Apply kernel-specific tweaks after the initial document processing
29 RE_function = re.compile(r'\b(([a-zA-Z_]\w+)\(\))', flags=ascii_p3)
34 RE_generic_type = re.compile(r'\b(struct|union|enum|typedef)\s+([a-zA-Z_]\w+)',
41 RE_struct = re.compile(r'\b(struct)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
42 RE_union = re.compile(r'\b(union)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
43 RE_enum = re.compile(r'\b(enum)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
44 RE_typedef = re.compile(r'\b(typedef)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
50 RE_doc = re.compile(r'(\bDocumentation/)?((\.\./)*[\w\-/]+)\.(rst|txt)')
55 # Reserved C words that we should skip when cross-referencing
[all …]
|
| /Documentation/locking/ |
| D | pi-futex.rst | 2 Lightweight PI-futexes
7 - in the user-space fastpath a PI-enabled futex involves no kernel work
9 calls - just pure fast atomic ops in userspace.
11 - even in the slowpath, the system call and scheduling pattern is very
14 - the in-kernel PI implementation is streamlined around the mutex
17 read-write lock support), only the owner may unlock a lock, no
20 Priority Inheritance - why?
21 ---------------------------
23 The short reply: user-space PI helps achieving/improving determinism for
24 user-space applications. In the best-case, it can help achieve
[all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | bttv-devel.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 -------------------------
10 Making video work often is not a big deal, because this is handled
15 bttv-cards.c, which holds the information required for each board.
16 Sound will work only, if the correct entry is used (for video it often
24 example. The file Documentation/admin-guide/media/bttv-cardlist.rst has a list
29 card, you can check if one of the existing entries does work for you
35 module like ``msp3400`` to make sound work. If there isn't one for the
47 Still doesn't work? Looks like some driver hacking is required.
48 Below is a do-it-yourself description for you.
[all …]
|
| /Documentation/driver-api/usb/ |
| D | persist.rst | 1 .. _usb-persist:
14 bus must continue to supply suspend current (around 1-5 mA). This
16 detect connect-change events (devices being plugged in or unplugged).
35 system woke up, who cares? It'll still work the same when you type on
38 Unfortunately problems _can_ arise, particularly with mass-storage
41 filesystem on the device, you're out of luck -- everything in that
57 suspend-to-RAM. On almost all systems, no suspend current is
58 available during hibernation (also known as swsusp or suspend-to-disk).
65 suspended -- but it will crash as soon as it wakes up, which isn't
72 The kernel includes a feature called USB-persist. It tries to work
[all …]
|
| /Documentation/hwmon/ |
| D | lm80.rst | 10 Addresses scanned: I2C 0x28 - 0x2f
20 Addresses scanned: I2C 0x28 - 0x2f
28 - Frodo Looijaard <frodol@dds.nl>,
29 - Philip Edelbrock <phil@netroedge.com>
32 -----------
35 It is described as a 'Serial Interface ACPI-Compatible Microprocessor
47 should work in the same way (but this must be checked; the datasheet
48 is unclear about this). Measurements are guaranteed between -55 and
57 representable value is around 2600 RPM.
71 miss once-only alarms.
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 12 ----------
14 There are two distinctive motivators for this work, which are not satisfied by
18 - more efficient memory utilization by sharing ring buffer across CPUs;
19 - preserving ordering of events that happen sequentially in time, even across
23 Both are a result of a choice to have per-CPU perf ring buffer. Both can be
25 problem could technically be solved for perf buffer with some in-kernel
30 ------------------
56 The approach chosen has an advantage of re-using existing BPF map
62 combined with ``ARRAY_OF_MAPS`` and ``HASH_OF_MAPS`` map-in-maps to implement
75 - variable-length records;
[all …]
|
| /Documentation/arch/arm/ |
| D | arm.rst | 9 ---------------------
21 If you wish to cross-compile, then alter the following lines in the top
36 CROSS_COMPILE=<your-path-to-your-compiler-without-gcc>
40 CROSS_COMPILE=arm-linux-
48 ---------------
54 Bug reports should be sent to linux-arm-kernel@lists.arm.linux.org.uk,
64 -------------
66 Several new include directories have been created under include/asm-arm,
67 which are there to reduce the clutter in the top-level directory. These
71 `arch-*` machine/platform specific header files
[all …]
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 Things don't always have to be perfect - nitpicking often does more harm than
12 good. But appreciate beauty when you see it - and let people know.
26 you're not sure if it can happen and not sure how to handle it yet - make it a
33 expensive - but don't turn everything into a debug mode assertion, so that
52 elide - if we were working in a language with embedded correctness proofs that
56 invariants with runtime checks - much like the way people working in
60 Looking for ways to make your assertions simpler - and higher level - will
63 Good code is code where you can poke around and see what it's doing -
68 going on - fix that first.
[all …]
|
| /Documentation/timers/ |
| D | timekeeping.rst | 10 If you grep through the kernel source you will find a number of architecture-
12 architecture-specific overrides of the sched_clock() function and some
17 on this timeline, providing facilities such as high-resolution timers.
23 -------------
31 n bits which count from 0 to (2^n)-1 and then wraps around to 0 and start over.
36 shall be as stable and correct as possible as compared to a real-world wall
46 When the wall-clock accuracy of the clock source isn't satisfactory, there
48 the user-visible time to RTC clocks in the system or against networked time
76 Since a 32-bit counter at say 100 MHz will wrap around to zero after some 43
80 code knows when the counter will wrap around and can insert the necessary
[all …]
|
| /Documentation/trace/ |
| D | tracepoints.rst | 15 ----------------------
37 -----
40 - A tracepoint definition, placed in a header file.
41 - The tracepoint statement, in C code.
79 - subsys_eventname is an identifier unique to your event
81 - subsys is the name of your subsystem.
82 - eventname is the name of the event to trace.
84 - `TP_PROTO(int firstarg, struct task_struct *p)` is the prototype of the
87 - `TP_ARGS(firstarg, p)` are the parameters names, same as found in the
90 - if you use the header in multiple source files, `#define CREATE_TRACE_POINTS`
[all …]
|
12345678