Searched +full:back +full:- +full:end (Results 1 – 25 of 247) sorted by relevance
12345678910
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-pisp-be.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 .. _v4l2-meta-fmt-rpi-be-cfg:
9 Raspberry Pi PiSP Back End configuration format
12 The Raspberry Pi PiSP Back End memory-to-memory image signal processor is
14 to the `pispbe-config` output video device node using the
17 The PiSP Back End processes images in tiles, and its configuration requires
22 <https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf>`_
23 provide detailed description of the ISP back end configuration and programming
27 -------------------------
38 ---------------
[all …]
|
| /Documentation/admin-guide/media/ |
| D | raspberrypi-pisp-be.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Raspberry Pi PiSP Back End Memory-to-Memory ISP (pisp-be)
7 The PiSP Back End
10 The PiSP Back End is a memory-to-memory Image Signal Processor (ISP) which reads
13 pixel data back to memory through two distinct output channels.
18 The PiSP Back End ISP processes images in tiles. The handling of image
19 tessellation and the computation of low-level configuration parameters is
24 an image sensor through a MIPI CSI-2 compatible capture interface, storing them
25 in DRAM memory and processing them in the PiSP Back End to obtain images usable
29 The pisp-be driver
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | raspberrypi,pispbe.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Raspberry Pi PiSP Image Signal Processor (ISP) Back End
10 - Raspberry Pi Kernel Maintenance <kernel-list@raspberrypi.com>
11 - Jacopo Mondi <jacopo.mondi@ideasonboard.com>
14 The Raspberry Pi PiSP Image Signal Processor (ISP) Back End is an image
19 https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf
24 - enum:
25 - brcm,bcm2712-pispbe
[all …]
|
| /Documentation/gpu/amdgpu/display/ |
| D | dcn-overview.rst | 10 .. kernel-figure:: dc_pipeline_overview.svg
19 * **Display Pipe and Plane (DPP)**: This block provides pre-blend pixel
24 multiple planes, using global or per-pixel alpha.
36 the display pipe back to memory as video frames.
38 * **Multi-Media HUB (MMHUBBUB)**: Memory controller interface for DMCUB and DWB
43 the Display Micro-Controller Unit - version B (DMCUB), which is handled via
83 Front End and Back End
84 ----------------------
87 referred as **Front End (FE)** and **Back End (BE)**, where FE consists of:
100 a one-to-one mapping of the link encoder to PHY, but we can configure the DCN
[all …]
|
| /Documentation/admin-guide/perf/ |
| D | meson-ddr-pmu.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 meson_ddr_bw/chan_{1,2,3,4}_rw_bytes/ events are channel-specific events.
26 + arm - from CPU
27 + vpu_read1 - from OSD + VPP read
28 + gpu - from 3D GPU
29 + pcie - from PCIe controller
30 + hdcp - from HDCP controller
31 + hevc_front - from HEVC codec front end
32 + usb3_0 - from USB3.0 controller
33 + hevc_back - from HEVC codec back end
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | fsl,imx-asrc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/fsl,imx-asrc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 different output clock. The driver currently works as a Front End of DPCM
13 with other Back Ends Audio controller such as ESAI, SSI and SAI. It has
17 - Shawn Guo <shawnguo@kernel.org>
18 - Sascha Hauer <s.hauer@pengutronix.de>
23 - enum:
24 - fsl,imx35-asrc
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-cdc_ncm | 10 as-is, without any padding, and are terminated with a
14 back-to-back without any interleaving short USB
28 end" quirk. Defaults to 'N', except for devices
31 The "NDP to end" quirk makes the driver place the NDP
82 The following read-only attributes all represent fields of the
87 quoted from table 6-3 of CDC NCM: "NTB Parameter Structure".
94 - Bit 0: 16-bit NTB supported (set to 1)
95 - Bit 1: 32-bit NTB supported
96 - Bits 2 – 15: reserved (reset to zero; must be ignored by host)
|
| D | sysfs-bus-dax | 8 that back the dax device, and also by arch requirements.
16 device. Specified in the format <start>-<end>.
19 What: /sys/bus/dax/devices/daxX.Y/mapping[0..N]/end
28 start physical address for the given range. The 'end' attribute
29 indicates the end physical address for the given range. The
67 (RO) The target-node attribute is the Linux numa-node that a
68 device-dax instance may create when it is online. Prior to
74 What: $(readlink -f /sys/bus/dax/devices/daxX.Y)/../dax_region/available_size
84 What: $(readlink -f /sys/bus/dax/devices/daxX.Y)/../dax_region/size
92 What: $(readlink -f /sys/bus/dax/devices/daxX.Y)/../dax_region/align
[all …]
|
| /Documentation/bpf/ |
| D | bpf_devel_QA.rst | 10 Documentation/process/submitting-patches.rst. This document only describes
21 --------------------------------------------
48 ------------------------------------------------------------------------
49 A: BPF CI is GitHub based and hosted at https://github.com/kernel-patches/bpf.
55 - Create a fork of the aforementioned repository in your own account (one time
58 - Clone the fork locally, check out a new branch tracking either the bpf-next
59 or bpf branch, and apply your to-be-tested patches on top of it
61 - Push the local branch to your fork and create a pull request against
62 kernel-patches/bpf's bpf-next_base or bpf_base branch, respectively
68 Note furthermore that both base branches (bpf-next_base and bpf_base) will be
[all …]
|
| /Documentation/arch/powerpc/ |
| D | transactional_memory.rst | 18 guaranteed to either complete atomically or roll back and undo any partial
46 The 'tbegin' instruction denotes the start point, and 'tend' the end point.
49 transactional or non-transactional accesses within the system. In this
50 example, the transaction completes as though it were normal straight-line code
59 state will roll back to that at the 'tbegin', and control will continue from
69 - Conflicts with cache lines used by other processors
70 - Signals
71 - Context switches
72 - See the ISA for full documentation of everything that will abort transactions.
109 determine the transactional state -- if so, the second ucontext in uc->uc_link
[all …]
|
| /Documentation/usb/ |
| D | chipidea.rst | 6 -----------------------------------
12 -------------------------
29 otg-rev = <0x0200>;
30 adp-disable;
33 -------------------
38 2) Connect 2 boards with usb cable: one end is micro A plug, the other end
41 The A-device (with micro A plug inserted) should enumerate B-device.
45 On B-device::
49 B-device should take host role and enumerate A-device.
51 4) A-device switch back to host.
[all …]
|
| /Documentation/gpu/amdgpu/ |
| D | amdgpu-glossary.rst | 7 'Documentation/gpu/amdgpu/display/dc-glossary.rst'.
31 End Of Pipe/Pipeline
37 them. The name GART harkens back to the days of AGP when the platform
90 Multi-Media HUB
96 PowerPlay Library - PowerPlay is the power management component.
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,rpm-master-stats.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/qcom/qcom,rpm-master-stats.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Konrad Dybcio <konradybcio@kernel.org>
16 (particularly around entering hardware-driven low power modes: XO shutdown
17 and total system-wide power collapse) are first made at Master-level, and
21 our device has entered the desired low-power mode, how long it took to do so,
22 the duration of that residence, how long it took to come back online,
26 This scheme has been used on various SoCs in the 2013-2023 era, with some
[all …]
|
| /Documentation/staging/ |
| D | crc32.rst | 5 A CRC is a long-division remainder. You add the CRC to the message,
11 protocols put the end-of-frame flag after the CRC.
15 - We're working in binary, so the digits are only 0 and 1, and
16 - When dividing polynomials, there are no carries. Rather than add and
21 To produce a 32-bit CRC, the divisor is actually a 33-bit CRC polynomial.
24 familiar with the IEEE 754 floating-point format, it's the same idea.)
28 the best error-detecting properties, this should correspond to the
29 order they're actually sent. For example, standard RS-232 serial is
30 little-endian; the most significant bit (sometimes used for parity)
38 back into range. In binary, this is easy - it has to be either 0 or 1,
[all …]
|
| /Documentation/sound/soc/ |
| D | dpcm.rst | 18 DPCM re-uses all the existing component codec, platform and DAI drivers without
23 -------------------------------------
26 document for all examples :-
29 | Front End PCMs | SoC DSP | Back End DAIs | Audio devices |
32 PCM0 <------------> * * <----DAI0-----> Codec Headset
34 PCM1 <------------> * * <----DAI1-----> Codec Speakers
36 PCM2 <------------> * * <----DAI2-----> MODEM
38 PCM3 <------------> * * <----DAI3-----> BT
40 * * <----DAI4-----> DMIC
42 * * <----DAI5-----> FM
[all …]
|
| /Documentation/doc-guide/ |
| D | maintainer-profile.rst | 1 .. SPDX-License-Identifier: GPL-2.0
19 The mailing list for documentation is linux-doc@vger.kernel.org. Patches
20 should be made against the docs-next tree whenever possible.
23 -------------------------
34 beginners), userspace programmers, end users and/or system administrators,
38 ---------------
46 --------------
52 have not heard back within a week of sending a patch.
|
| /Documentation/arch/x86/ |
| D | mtrr.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 :Authors: - Richard Gooch <rgooch@atnf.csiro.au> - 3 Jun 1999
8 - Luis R. Rodriguez <mcgrof@do-not-panic.com> - April 9, 2015
17 non-PAT systems while a no-op but equally effective on PAT enabled systems.
37 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
46 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
50 The Centaur C6 (WinChip) has 8 MCRs, allowing write-combining. These
73 reg00: base=0x00000000 ( 0MB), size= 128MB: write-back, count=1
74 reg01: base=0x08000000 ( 128MB), size= 64MB: write-back, count=1
76 Creating MTRRs from the C-shell::
[all …]
|
| /Documentation/arch/sparc/ |
| D | adi.rst | 34 SPARC M7 processor, MMU uses bits 63-60 for version tags and ADI block
37 virtual addresses that contain 0xa in bits 63-60.
58 - Version tag values of 0x0 and 0xf are reserved. These values match any
61 - Version tags are set on virtual addresses from userspace even though
66 - When a task frees a memory page it had set version tags on, the page
67 goes back to free page pool. When this page is re-allocated to a task,
70 freed and allocated back to the same task, old version tags set by the
73 - ADI tag mismatches are not detected for non-faulting loads.
75 - Kernel does not set any tags for user pages and it is entirely a
78 swapped back in. It also preserves that version tags if a page is
[all …]
|
| /Documentation/RCU/ |
| D | rcubarrier.rst | 10 struct placed within the RCU-protected data structure and another pointer
16 call_rcu(&p->rcu, p_callback);
30 -------------------------------------
37 http://lwn.net/images/ns/kernel/rcu-drop.jpg.
39 We could try placing a synchronize_rcu() in the module-exit code path,
43 One might be tempted to try several back-to-back synchronize_rcu()
45 heavy RCU-callback load, then some of the callbacks might be deferred in
52 -------------
61 Pseudo-code using rcu_barrier() is as follows:
139 55 rcu_torture_stats_print(); /* -After- the stats thread is stopped! */
[all …]
|
| /Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 2 Reducing OS jitter due to per-cpu kthreads
5 This document lists per-CPU kthreads in the Linux kernel and presents
6 options to control their OS jitter. Note that non-per-CPU kthreads are
7 not listed here. To reduce OS jitter from non-per-CPU kthreads, bind
13 - Documentation/core-api/irq/irq-affinity.rst: Binding interrupts to sets of CPUs.
15 - Documentation/admin-guide/cgroup-v1: Using cgroups to bind tasks to sets of CPUs.
17 - man taskset: Using the taskset command to bind tasks to sets
20 - man sched_setaffinity: Using the sched_setaffinity() system
23 - /sys/devices/system/cpu/cpuN/online: Control CPU N's hotplug state,
26 - In order to locate kernel-generated OS jitter on CPU N:
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | cache.rst | 8 dm-cache is a device mapper target written by Joe Thornber, Heinz
15 This device-mapper solution allows us to insert this caching at
17 a thin-provisioning pool. Caching solutions that are integrated more
20 The target reuses the metadata library used in the thin-provisioning
23 The decision as to what data to migrate and when is left to a plug-in
46 Sub-devices
47 -----------
52 1. An origin device - the big, slow one.
54 2. A cache device - the small, fast one.
56 3. A small metadata device - records which blocks are in the cache,
[all …]
|
| /Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,merge.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chun-Kuang Hu <chunkuang.hu@kernel.org>
11 - Philipp Zabel <p.zabel@pengutronix.de>
14 Mediatek display merge, namely MERGE, is used to merge two slice-per-line
15 inputs into one side-by-side output.
24 - enum:
25 - mediatek,mt8173-disp-merge
26 - mediatek,mt8195-disp-merge
[all …]
|
| /Documentation/fb/ |
| D | vesafb.rst | 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.
81 "vga=mode-number" you have to transform the numbers to decimal.
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.
92 The X-Server must restore the video mode correctly, else you end up
103 * configure and load the DOS-Tools for the graphics board (if
145 ywrap Same as ypan, but assumes your gfx board can wrap-around
[all …]
|
| /Documentation/sound/designs/ |
| D | compress-offload.rst | 2 ALSA Compress-Offload API
5 Pierre-Louis.Bossart <pierre-louis.bossart@linux.intel.com>
18 in system-on-chip designs, and DSPs are also integrated in audio
20 reduction of power consumption compared to host-based
27 provide a control and data-streaming interface for audio DSPs.
29 The design of this API was inspired by the 2-year experience with the
39 - separation between byte counts and time. Compressed formats may have
41 may vary from frame-to-frame. As a result, it is not possible to
44 reliable audio-video synchronization, which requires precise
47 - Handling of multiple formats. PCM data only requires a specification
[all …]
|
| /Documentation/core-api/ |
| D | circular-buffers.rst | 12 (1) Convenience functions for determining information about power-of-2 sized
27 (*) Measuring power-of-2 buffers.
30 - The producer.
31 - The consumer.
41 (1) A 'head' index - the point at which the producer inserts items into the
44 (2) A 'tail' index - the point at which the consumer finds the next item in
53 indices should be wrapped to 0 when they reach the end of the buffer, thus
58 than 1 if multiple items or variable-sized items are to be included in the
60 be careful, however, as a region more than one unit in size may wrap the end of
63 Measuring power-of-2 buffers
[all …]
|
12345678910