Home
last modified time | relevance | path

Searched +full:hardware +full:- +full:wise (Results 1 – 22 of 22) sorted by relevance

/Documentation/devicetree/bindings/leds/
Dqcom,pm8058-led.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/qcom,pm8058-led.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
17 hard-wired usecase.
19 Hardware-wise the different LEDs support slightly different output currents.
24 - $ref: common.yaml#
29 - qcom,pm8058-led
30 - qcom,pm8058-keypad-led
[all …]
/Documentation/devicetree/bindings/spi/
Dspi-controller.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/spi/spi-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Mark Brown <broonie@kernel.org>
20 pattern: "^spi(@.*|-([0-9]|[1-9][0-9]+))?$"
22 "#address-cells":
25 "#size-cells":
28 cs-gpios:
32 increased automatically with max(cs-gpios, hardware chip selects).
[all …]
/Documentation/usb/
Dusb-serial.rst45 --------------------------------------
58 -----------------------------------------------
72 This goes against the current documentation for pilot-xfer and other
73 packages, but is the only way that it will work due to the hardware
77 (this is usually /dev/ttyUSB1 if you do not have any other usb-serial
99 Kroah-Hartman at greg@kroah.com
103 -------------------
115 significant advantage of using USB is speed - I can get 73 to 113
120 contains the necessary packages and a simple step-by-step howto.
129 iPAQ - disable autosync by going to the Start/Settings/Connections menu
[all …]
/Documentation/core-api/
Dunaligned-memory-access.rst32 which will compile to multiple-byte memory access instructions, namely when
59 - Some architectures are able to perform unaligned memory accesses
61 - Some architectures raise processor exceptions when unaligned accesses
64 - Some architectures raise processor exceptions when unaligned accesses
67 - Some architectures are not capable of unaligned memory access, but will
131 structure type. This GCC-specific attribute tells the compiler never to
141 non-packed case, so the packed attribute should only be used when avoiding
167 In the above function, when the hardware has efficient unaligned access
168 capability, there is no issue with this code. But when the hardware isn't
177 16-bit-aligned addresses. It is up to the caller to ensure this alignment or
[all …]
/Documentation/driver-api/
Dlibata.rst12 transports for ATA and ATAPI devices, and SCSI<->ATA translation for ATA
16 internals, and a couple sample ATA low-level drivers.
22 is defined for every low-level libata
23 hardware driver, and it controls how the low-level driver interfaces
26 FIS-based drivers will hook into the system with ``->qc_prep()`` and
27 ``->qc_issue()`` high-level hooks. Hardware which behaves in a manner
28 similar to PCI IDE hardware may utilize several generic helpers,
33 ----------------------------------------------------------
35 Post-IDENTIFY device configuration
44 Typically used to apply device-specific fixups prior to issue of SET
[all …]
/Documentation/networking/
Dscaling.rst1 .. SPDX-License-Identifier: GPL-2.0
13 multi-processor systems.
17 - RSS: Receive Side Scaling
18 - RPS: Receive Packet Steering
19 - RFS: Receive Flow Steering
20 - Accelerated Receive Flow Steering
21 - XPS: Transmit Packet Steering
28 (multi-queue). On reception, a NIC can send different packets to different
33 generally known as “Receive-side Scaling” (RSS). The goal of RSS and
35 Multi-queue distribution can also be used for traffic prioritization, but
[all …]
/Documentation/admin-guide/media/
Dcec.rst1 .. SPDX-License-Identifier: GPL-2.0
7 Supported hardware in mainline
12 - Exynos4
13 - Exynos5
14 - STIH4xx HDMI CEC
15 - V4L2 adv7511 (same HW, but a different driver from the drm adv7511)
16 - stm32
17 - Allwinner A10 (sun4i)
18 - Raspberry Pi
19 - dw-hdmi (Synopsis IP)
[all …]
/Documentation/admin-guide/
Dreporting-issues.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
36 ensure it's vanilla (IOW: not patched and not using add-on modules). Also make
44 to pin-point the culprit with a bisection; if you succeed, include its
45 commit-id and CC everyone in the sign-off-by chain.
51 Step-by-step guide how to report issues to the kernel maintainers
58 step-by-step approach. It still tries to be brief for readability and leaves
59 out a lot of details; those are described below the step-by-step guide in a
68 * Are you facing an issue with a Linux kernel a hardware or software vendor
89 kernel modules on-the-fly, which solutions like DKMS might be doing locally
169 --------------------------------------------------------------
[all …]
Dverify-bugs-and-bisect-regressions.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
9 currently supported by developers -- to then explain how to locate the change
14 commodity hardware who want to report a kernel bug to the upstream Linux
22 read and navigate this document -- especially when you want to look something
26 https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
32 over to the* ':ref:`step-by-step guide <introguide_bissbs>`' *below. It utilizes
45 *segment 2*. Then you can submit a preliminary report -- or continue with
47 full-fledged regression report. In the following example 6.0.13 is assumed to be
55 # * Ensure Secure Boot permits booting self-compiled Linux kernels.
59 git clone -o mainline --no-checkout \
[all …]
Dquickly-build-trimmed-linux.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
9 testing purposes, but perfectly fine for day-to-day use, too.
15 section below: it contains a step-by-step guide, which is more detailed, but
21 self-compiled Linux kernels; install compilers and everything else needed for
26 git clone --depth 1 -b master \
34 make -j $(nproc --all)
37 command -v installkernel && sudo make modules_install install
43 git fetch --depth 1 origin
45 git checkout --force --detach origin/master
49 make -j $(nproc --all)
[all …]
/Documentation/userspace-api/media/dvb/
Dlegacy_dvb_audio.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later OR GPL-2.0
15 hardware. It can be accessed through ``/dev/dvb/adapter?/audio?``. Data
35 -----
39 ---------------------
46 .. code-block:: c
56 .. flat-table::
57 :header-rows: 0
58 :stub-columns: 0
60 - ..
62 - ``AUDIO_SOURCE_DEMUX``
[all …]
Dlegacy_dvb_osd.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later OR GPL-2.0
14 The DVB OSD device controls the OnScreen-Display of the AV7110 based
15 DVB-cards with hardware MPEG2 decoder. It can be accessed through
20 The OSD is not a frame-buffer like on many other cards.
22 The color-depth is limited depending on the memory size installed.
31 -----------
36 .. code-block:: c
39 /* All functions return -2 on "not open" */
67 .. note:: All functions return -2 on "not open"
69 .. flat-table::
[all …]
Dlegacy_dvb_video.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later OR GPL-2.0
15 hardware. It can be accessed through ``/dev/dvb/adapter0/video0``. Data
40 --------------
45 .. code-block:: c
56 .. flat-table::
57 :header-rows: 0
58 :stub-columns: 0
60 - ..
62 - ``VIDEO_FORMAT_4_3``
64 - Select 4:3 format.
[all …]
/Documentation/driver-api/mtd/
Dnand_ecc.rst2 NAND Error-correction Code
11 After that the speed was increased by 35-40%.
63 - cp0 is the parity that belongs to all bit0, bit2, bit4, bit6.
69 - cp2 is the parity over bit0, bit1, bit4 and bit5
70 - cp3 is the parity over bit2, bit3, bit6 and bit7.
71 - cp4 is the parity over bit0, bit1, bit2 and bit3.
72 - cp5 is the parity over bit4, bit5, bit6 and bit7.
78 - rp0 is the parity of all even bytes (0, 2, 4, 6, ... 252, 254)
79 - rp1 is the parity of all odd bytes (1, 3, 5, 7, ..., 253, 255)
80 - rp2 is the parity of all bytes 0, 1, 4, 5, 8, 9, ...
[all …]
/Documentation/userspace-api/
Dperf_ring_buffer.rst1 .. SPDX-License-Identifier: GPL-2.0
15 2.2.2 Per-thread mode
16 2.2.3 Per-CPU mode
19 2.3.1 Producer-consumer model
37 plays an important role for hardware tracing with Intel PT, Arm
55 -------------------
63 +---------------------------+
65 +---------------------------+
66 `-> Tail `-> Head
86 read-only mapping, which is to be addressed in the section
[all …]
/Documentation/arch/sparc/oradax/
Ddax-hv-api.txt3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
13 …The following APIs provide access via the Hypervisor to hardware assisted data processing function…
16 live-migration and other system management activities.
19 …The Data Analytics Accelerator (DAX) functionality is a collection of hardware coprocessors that p…
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
28 …e Completion Area and, unless execution order is specifically restricted through the use of serial-
45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
51 36.1.1.1. "ORCL,sun4v-dax" Device Compatibility
54 • No-op/Sync
[all …]
/Documentation/userspace-api/media/v4l/
Dext-ctrls-codec-stateless.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _codec-stateless-controls:
10 stateless decoder and encoders (i.e. hardware accelerators).
18 .. _codec-stateless-control-id:
23 .. _v4l2-codec-stateless-h264:
28 necessary parameters for configuring a stateless hardware decoding
43 .. flat-table:: struct v4l2_ctrl_h264_sps
44 :header-rows: 0
45 :stub-columns: 0
48 * - __u8
[all …]
Dsubdev-formats.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _v4l2-mbus-format:
14 .. flat-table:: struct v4l2_mbus_framefmt
15 :header-rows: 0
16 :stub-columns: 0
19 * - __u32
20 - ``width``
21 - Image width in pixels.
22 * - __u32
23 - ``height``
[all …]
/Documentation/cdrom/
Dcdrom-standard.rst2 A Linux CD-ROM standard
14 Linux is probably the Unix-like operating system that supports
15 the widest variety of hardware devices. The reasons for this are
18 - The large list of hardware devices available for the many platforms
19 that Linux now supports (i.e., i386-PCs, Sparc Suns, etc.)
20 - The open design of the operating system, such that anybody can write a
22 - There is plenty of source code around as examples of how to write a driver.
25 hardware has allowed Linux to support many different hardware devices.
29 This divergence of behavior has been very significant for CD-ROM
32 their drivers totally inconsistent, the writers of Linux CD-ROM
[all …]
/Documentation/virt/uml/
Duser_mode_linux_howto_v2.rst1 .. SPDX-License-Identifier: GPL-2.0
22 hardware emulation. In fact, it does not. As long as a virtualization
24 has a driver for, the devices do not need to emulate real hardware.
25 Most OSes today have built-in support for a number of "fake"
27 User Mode Linux takes this concept to the ultimate extreme - there
30 concepts which map onto something provided by the host - files, sockets,
36 The UML kernel is just a process running on Linux - same as any other
57 * You can run a usermode kernel as a non-root user (you may need to
69 * You are not bound by "emulating" hardware, so you can try weird and
71 real hardware such as time travel and making your system clock
[all …]
/Documentation/devicetree/bindings/cpu/
Didle-states.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/cpu/idle-states.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
11 - Anup Patel <anup@brainfault.org>
15 1 - Introduction
18 ARM and RISC-V systems contain HW capable of managing power consumption
19 dynamically, where cores can be put in different low-power states (ranging
22 run-time, can be specified through device tree bindings representing the
[all …]
/Documentation/filesystems/xfs/
Dxfs-online-fsck-design.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Heading 3 uses "----"
25 - To help kernel distributors understand exactly what the XFS online fsck
28 - To help people reading the code to familiarize themselves with the relevant
31 - To help developers maintaining the system by capturing the reasons
59 - Provide a hierarchy of names through which application programs can associate
62 - Virtualize physical storage media across those names, and
64 - Retrieve the named data blobs at any time.
66 - Examine resource usage.
79 cross-references different types of metadata records with each other to look
[all …]