Searched +full:everything +full:- +full:else (Results 1 – 25 of 65) sorted by relevance
123
| /Documentation/devicetree/bindings/serial/ |
| D | amlogic,meson-uart.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/serial/amlogic,meson-uart.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Neil Armstrong <narmstrong@baylibre.com>
15 of SoCs, and can be present either in the "Always-On" power domain or the
16 "Everything-Else" power domain.
18 The particularity of the "Always-On" Serial Interface is that the hardware
19 is active since power-on and does not need any clock gating and is usable
25 - description: Always-on power domain UART controller
[all …]
|
| /Documentation/devicetree/bindings/power/ |
| D | amlogic,meson-ee-pwrc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/power/amlogic,meson-ee-pwrc.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
8 title: Amlogic Meson Everything-Else Power Domains
11 - Neil Armstrong <narmstrong@baylibre.com>
14 The Everything-Else Power Domains node should be the child of a syscon
17 - compatible: Should be the following:
18 "amlogic,meson-gx-hhi-sysctrl", "simple-mfd", "syscon"
26 - amlogic,meson-g12a-pwrc
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | dma-controller.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/dma/dma-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vinod Koul <vkoul@kernel.org>
13 - $ref: "dma-common.yaml#"
15 # Everything else is described in the common file
18 pattern: "^dma-controller(@.*)?$"
21 - |
22 dma: dma-controller@48000000 {
[all …]
|
| /Documentation/driver-api/ |
| D | isa.rst | 27 now (for oldisa-only drivers) become::
52 unsigned int id`` pair directly -- with the device creation completely
59 ALSA would want to keep the old non-load behaviour, it could stick all
61 everything was found to be present and accounted for. If it wanted the
64 do everything in .probe() as before.
70 values have been passed in) and .probe() for everything else. This is
85 if (dev->platform_data == isa_driver) {
86 if (!isa_driver->match ||
87 isa_driver->match(dev, to_isa_dev(dev)->id))
89 dev->platform_data = NULL;
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | aspeed-lpc.txt | 5 The LPC bus is a means to bridge a host CPU to a number of low-bandwidth
11 The LPC controller is represented as a multi-function device to account for the
15 H8S/2168[1]", and everything else, where everything else is an eclectic
16 collection of functions with a esoteric register layout. "Everything else",
24 APB-to-LPC bridging amonst other functions.
27 as LPC firmware hub cycles, configuration of the LPC-to-AHB mapping, UART
39 [1] https://www.renesas.com/en-sg/doc/products/mpumcu/001/rej09b0078_h8s2168.pdf?key=7c888374547021…
40 …el.com/content/dam/www/public/us/en/documents/product-briefs/ipmi-second-gen-interface-spec-v2-rev…
46 - compatible: One of:
47 "aspeed,ast2400-lpc", "simple-mfd"
[all …]
|
| /Documentation/process/ |
| D | management-style.rst | 8 mirror the :ref:`process/coding-style.rst <codingstyle>` document to some
35 ------------
37 Everybody thinks managers make decisions, and that decision-making is
55 painful ones. Making small and non-consequential decisions is fine, and
65 **two** inconsequential decisions - the wrong one **and** the right one.
72 you cannot escape. A cornered rat may be dangerous - a cornered manager
80 back-tracking is very easy: just tell everybody that you were an
89 - admitting you were an idiot is harder than it looks. We all like to
92 - having somebody tell you that what you worked on for the last year
101 admitting up-front that you don't have a friggin' clue, and telling
[all …]
|
| D | 6.Followthrough.rst | 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
39 - Code review is hard work, and it is a relatively thankless occupation;
47 - Similarly, code reviewers are not trying to promote their employers'
92 What if you've tried to do everything right and things still aren't going
105 -----------------
111 things. In particular, there may be more than one tree - one, perhaps,
113 longer-term work.
[all …]
|
| /Documentation/sound/soc/ |
| D | codec.rst | 11 Each codec class driver *must* provide the following features:-
14 2. Codec control IO - using RegMap API
20 Optionally, codec drivers can also provide:-
31 -------------------------------
49 .name = "wm8731-hifi",
68 ----------------
76 -------------------------
83 Defines a single control as follows:-
92 Other macros include:-
107 Defines an single enumerated control as follows:-
[all …]
|
| /Documentation/media/v4l-drivers/ |
| D | pvrusb2.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 ----------
13 Its history started with the reverse-engineering effort by Björn
29 1. Low level wire-protocol implementation with the device.
38 tear-down, arbitration, and interaction with high level
61 --------
70 --------------------------------------
76 pvrusb2-audio.[ch] - This is glue logic that resides between this
80 pvrusb2-context.[ch] - This module implements the context for an
81 instance of the driver. Everything else eventually ties back to
[all …]
|
| /Documentation/sphinx/ |
| D | kfigure.py | 1 # -*- coding: utf-8; mode: python -*-
14 handling from the author's POV. Directives like ``kernel-figure`` implement
15 methods *to* always get the best output-format even if some tools are not
19 * ``.. kernel-image``: for image handling / a ``.. image::`` replacement
21 * ``.. kernel-figure``: for figure handling / a ``.. figure::`` replacement
23 * ``.. kernel-render``: for render markup / a concept to embed *render*
26 - ``DOT``: render embedded Graphviz's **DOC**
27 - ``SVG``: render embedded Scalable Vector Graphics (**SVG**)
28 - ... *developable*
33 available, the DOT language is inserted as literal-block.
[all …]
|
| /Documentation/ |
| D | kref.txt | 8 A lot of this was lifted from Greg Kroah-Hartman's 2004 OLS paper and
11 - http://www.kroah.com/linux/talks/ols_2004_kref_paper/Reprint-Kroah-Hartman-OLS2004.pdf
12 - http://www.kroah.com/linux/talks/ols_2004_kref_talk/
45 return -ENOMEM;
46 kref_init(&data->refcount);
56 1) If you make a non-temporary copy of a pointer, especially if
60 kref_get(&data->refcount);
62 If you already have a valid pointer to a kref-ed structure (the
67 kref_put(&data->refcount, data_release);
71 a valid pointer to a kref-ed structure without already
[all …]
|
| /Documentation/block/ |
| D | biovecs.rst | 8 Instead, we have a new struct bvec_iter which represents a range of a biovec -
16 In the new scheme of things, everything that must be mutated in order to
22 There are a bunch of new helper macros for hiding the gory details - in
37 wrapper around bio_advance_iter() that operates on bio->bi_iter, and also
40 There is a lower level advance function - bvec_iter_advance() - which takes
50 exactly one bvec at a time - for example, bio_copy_data() in fs/bio.c,
52 wouldn't necessarily be the same size, the old code was tricky convoluted -
56 The new code is much more straightforward - have a look. This sort of
62 completed (perhaps to copy the data somewhere else, or perhaps to resubmit
63 it somewhere else if there was an error) had to save the entire bvec array
[all …]
|
| /Documentation/ioctl/ |
| D | botching-up-ioctls.rst | 5 From: http://blog.ffwll.ch/2013/11/botching-up-ioctls.html
13 Which is nice, since there's no more insanity in the form of fake-generic, but
19 only cover technicalities and not the big-picture issues like what the command
25 -------------
28 will need to add a 32-bit compat layer:
33 * Align everything to the natural size and use explicit padding. 32-bit
34 platforms don't necessarily align 64-bit values to 64-bit boundaries, but
35 64-bit platforms do. So we always need padding to the natural size to get
38 * Pad the entire struct to a multiple of 64-bits if the structure contains
39 64-bit types - the structure size will otherwise differ on 32-bit versus
[all …]
|
| /Documentation/admin-guide/ |
| D | efi-stub.rst | 8 along with the EFI-specific entry point that the firmware loader
12 arch/arm/boot/compressed/efi-header.S and
13 arch/arm/boot/compressed/efi-stub.c. EFI stub code that is shared
18 kernel. The arm64 EFI stub lives in arch/arm64/kernel/efi-entry.S
19 and drivers/firmware/efi/libstub/arm64-stub.c.
30 --------------------------
43 --------------------------------------------
51 --------------------
55 stub-specific command line parameter, everything else is passed to the
60 is an EFI-style path and directory elements must be separated with
[all …]
|
| D | sysfs-rules.rst | 4 The kernel-exported sysfs exports internal kernel implementation details
11 low-level userspace applications, with a new kernel release, the users
12 of sysfs must follow some rules to use an as-abstract-as-possible way to
21 - Do not use libsysfs
23 offer any abstraction, it exposes all the kernel driver-core
31 - sysfs is always at ``/sys``
38 - devices are only "devices"
39 There is no such thing like class-, bus-, physical devices,
40 interfaces, and such that you can rely on in userspace. Everything is
41 just simply a "device". Class-, bus-, physical, ... types are just
[all …]
|
| D | sysrq.rst | 10 regardless of whatever else it is doing, unless it is completely locked up.
22 - 0 - disable sysrq completely
23 - 1 - enable all functions of sysrq
24 - >1 - bitmask of allowed sysrq functions (see below for detailed function
27 2 = 0x2 - enable control of console logging level
28 4 = 0x4 - enable control of keyboard (SAK, unraw)
29 8 = 0x8 - enable debugging dumps of processes etc.
30 16 = 0x10 - enable sync command
31 32 = 0x20 - enable remount read-only
32 64 = 0x40 - enable signalling of processes (term, kill, oom-kill)
[all …]
|
| /Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.rst | 15 ---------------------------------
20 go. Only very few driver-specific details have to be moved to other functions.
23 - open: Everything dealing with resource management (file-open checks, magic
25 driver specific start-function. Note that for some drivers, the start-function
26 also serves as the ping-function. If that is the case and you need start/stop
27 to be balanced (clocks!), you are better off refactoring a separate start-function.
29 - close: Same hints as for open apply.
31 - write: Can simply go, all defined behaviour is taken care of by the framework,
34 - ioctl: While the driver is allowed to have extensions to the IOCTL interface,
42 Needs the status-callback defined, otherwise returns 0
[all …]
|
| /Documentation/networking/ |
| D | 6pack.txt | 1 This is the 6pack-mini-HOWTO, written by
4 Internet: ajk@comnets.uni-bremen.de
5 AMPR-net: dg3kq@db0pra.ampr.org
16 - The PC is given full control over the radio
23 algorithms as everything is computed in the PC. It would even be possible
26 This kind of real-time control is especially important to supply several
30 - Each packet transferred over the serial line is supplied with a checksum,
49 db0bm.automation.fh-aachen.de. In the directory /incoming/dg3kq,
85 - In the linux kernel configuration program, select the code maturity level
88 - Select the amateur radio support menu and turn on the serial port 6pack
[all …]
|
| D | checksum-offloads.rst | 1 .. SPDX-License-Identifier: GPL-2.0
32 In brief, it allows to request the device fill in a single ones-complement
33 checksum defined by the sk_buff fields skb->csum_start and skb->csum_offset.
34 The device should compute the 16-bit ones-complement checksum (i.e. the
35 'IP-style' checksum) from csum_start to the end of the packet, and fill in the
41 pseudo-header for UDP or TCP).
49 skb->csum_start and skb->csum_offset as described above, and setting
50 skb->csum_not_inet: see skbuff.h comment (section 'D') for more details.
61 A driver declares its offload capabilities in netdev->hw_features; see
62 Documentation/networking/netdev-features.txt for more. Note that a device
[all …]
|
| /Documentation/virt/kvm/ |
| D | locking.txt | 5 ---------------------
9 - kvm->lock is taken outside vcpu->mutex
11 - kvm->lock is taken outside kvm->slots_lock and kvm->irq_lock
13 - kvm->slots_lock is taken outside kvm->irq_lock, though acquiring
16 On x86, vcpu->mutex is taken outside kvm->arch.hyperv.hv_lock.
18 Everything else is a leaf: no other lock is taken inside the critical
22 ------------
27 the mmu-lock on x86. Currently, the page fault can be fast in one of the
34 2. Write-Protection: The SPTE is present and the fault is
35 caused by write-protect. That means we just need to change the W bit of the
[all …]
|
| /Documentation/gpu/ |
| D | todo.rst | 10 Subsystem-wide refactorings
14 ---------------------------------------------
24 --------------------------------------------------
32 non-converted driver (again virtual HW drivers for KVM are still all
42 ---------------------------------------------------------
48 avoid confusion - the other helpers in that file are all deprecated legacy
54 ----------------------------------------------------
57 nonblocking commits, and every driver had to hand-roll them. This is fixed
67 -----------------------
72 a bit too severe. So there's some follow-up work to adjust the function
[all …]
|
| /Documentation/crypto/ |
| D | descore-readme.txt | 2 ------------------------------------------------------------------------------
4 des - fast & portable DES encryption & decryption.
31 2. PORTABILITY to any byte-addressable host with a 32bit unsigned C type
32 3. Plug-compatible replacement for KERBEROS's low-level routines.
35 register-starved machines. My discussions with Richard Outerbridge,
40 up in a parameterized fashion so it can easily be modified by speed-daemon
47 compile on a SPARCStation 1 (cc -O4, gcc -O2):
49 this code (byte-order independent):
58 the key setting routine. also, i have no interest in re-implementing
61 used as drop-in replacements with mit's code or any of the mit-
[all …]
|
| /Documentation/sh/ |
| D | new-machine.txt | 5 Paul Mundt <lethal@linux-sh.org>
16 of the board-specific code (with the exception of stboards) ended up
17 in arch/sh/kernel/ directly, with board-specific headers ending up in
18 include/asm-sh/. For the new kernel, things are broken out by board type,
22 Board-specific code:
25 |-- arch
26 | `-- sh
27 | `-- boards
28 | |-- adx
29 | | `-- board-specific files
[all …]
|
| /Documentation/locking/ |
| D | spinlocks.rst | 20 there is only one thread-of-control within the region(s) protected by that
26 Documentation/memory-barriers.txt
33 spinlock for most things - using more than one spinlock can make things a
43 example, internal driver data structures that nobody else ever touches).
45 NOTE! The spin-lock is safe only when you **also** use the lock itself
46 to do locking across CPU's, which implies that EVERYTHING that
50 ----
52 Lesson 2: reader-writer spinlocks.
56 to mostly read from the shared variables, the reader-writer locks
61 NOTE! reader-writer locks require more atomic memory operations than
[all …]
|
| /Documentation/PCI/ |
| D | acpi-info.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 The general rule is that the ACPI namespace should describe everything the
39 If the OS is expected to manage a non-discoverable device described via
50 These are all device-specific, non-architected things, so the only way a
52 the device-specific details. The host bridge registers also include ECAM
66 bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
67 With the exception of ECAM, the bridge register space is device-specific
78 PNP0C02 "motherboard" devices are basically a catch-all. There's no
80 anything else." So a PNP0C02 _CRS should claim any address space that is
82 and (2) should not be assigned by the OS to something else.
[all …]
|
123