| /openbmc/linux/include/sound/sof/ |
| H A D | channel_map.h | 1 /* SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause) */
16 * \brief Channel map, specifies transformation of one-to-many or many-to-one.
18 * In case of one-to-many specifies how the output channels are computed out of
20 * in case of many-to-one specifies how a single target channel is computed
23 * Channel index specifies position of the channel in the stream on the 'one'
29 * Channel mask describes which channels are taken into account on the "many"
30 * side. Bit[i] set to 1 means that i-th channel is used for computation
34 * one per each channel set in the mask (left to right, LS bit set in the
35 * mask corresponds to ch_coeffs[0]).
49 * More than one transformation per a single channel is allowed (in case
|
| /openbmc/linux/drivers/remoteproc/ |
| H A D | pru_rproc.h | 1 /* SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause) */
5 * Copyright (C) 2014-2020 Texas Instruments Incorporated - https://www.ti.com/
6 * Suman Anna <s-anna@ti.com>
13 * struct pruss_int_map - PRU system events _to_ channel and host mapping
15 * @chnl: channel number assigned to a given @event
16 * @host: host number assigned to a given @chnl
18 * PRU system events are mapped to channels, and these channels are mapped
19 * to host interrupts. Events can be mapped to channels in a one-to-one or
20 * many-to-one ratio (multiple events per channel), and channels can be
21 * mapped to host interrupts in a one-to-one or many-to-one ratio (multiple
[all …]
|
| /openbmc/linux/Documentation/kernel-hacking/ |
| H A D | false-sharing.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 coherence of one cache line stored in multiple CPU's caches; then
20 Member 'refcount'(A) and 'name'(B) _share_ one cache line like below::
22 +-----------+ +-----------+
24 +-----------+ +-----------+
28 +----------------------+ +----------------------+
30 +----------------------+ +----------------------+
32 ---------------------------+------------------+-----------------------------
34 +----------------------+
36 +----------------------+
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | maintainer-soc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 --------
10 The SoC subsystem is a place of aggregation for SoC-specific code.
13 * devicetrees for 32- & 64-bit ARM and RISC-V
14 * 32-bit ARM board files (arch/arm/mach*)
15 * 32- & 64-bit ARM defconfigs
16 * SoC-specific drivers across architectures, in particular for 32- & 64-bit
17 ARM, RISC-V and Loongarch
19 These "SoC-specific drivers" do not include clock, GPIO etc drivers that have
20 other top-level maintainers. The drivers/soc/ directory is generally meant
[all …]
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | summary.rst | 2 Introduction to I2C and SMBus
6 a protocol developed by Philips. It is a slow two-wire protocol (variable
7 speed, up to 400 kHz), with a high speed extension (3.4 MHz). It provides
8 an inexpensive bus for connecting many types of devices with infrequent or
14 The latest official I2C specification is the `"I2C-bus specification and user
16 published by NXP Semiconductors. However, you need to log-in to the site to
18 `here <https://web.archive.org/web/20210813122132/https://www.nxp.com/docs/en/user-guide/UM10204.pd…
21 a subset of I2C protocols and signaling. Many I2C devices will work on an
22 SMBus, but some SMBus protocols add semantics beyond what is required to
28 use its protocols on many I2C systems. However, there are systems that don't
[all …]
|
| /openbmc/linux/drivers/usb/gadget/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-G
[all...] |
| /openbmc/linux/Documentation/userspace-api/media/drivers/ |
| H A D | imx-uapi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 ---------
18 - V4L2_EVENT_IMX_FRAME_INTERVAL_ERROR
20 The user application can subscribe to this event from the ipuX_csiY
30 -----------------------------------
33 NTSC/PAL signal re-sync (too little or too many video lines). When
34 this happens, the IPU triggers a mechanism to re-establish vertical
36 from image to image, and can last a long time before a stable image is
38 permanent split image (one frame contains lines from two consecutive
43 value for the current standard, by about one frame time (60 usec),
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/influxdb/influxdb/ |
| H A D | influxdb.conf | 1 ### Welcome to the InfluxDB configuration file.
8 # Once every 24 hours InfluxDB will report usage data to usage.influxdata.com
11 # Change this option to true to disable reporting.
12 # reporting-disabled = false
14 # Bind address to use for the RPC service for backup and restore.
15 # bind-address = "127.0.0.1:8088"
29 # retention-autocreate = true
32 # logging-enabled = true
38 ### flushed from the WAL. "dir" may need to be changed to a suitable place
48 wal-dir = "/var/lib/influxdb/wal"
[all …]
|
| /openbmc/linux/drivers/mtd/ubi/ |
| H A D | ubi-media.h | 1 /* SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause) */
10 * This file defines the layout of UBI headers and all the other UBI on-flash
47 * @UBI_VTBL_AUTORESIZE_FLG: auto-resize this volume
51 * check. Main use-case for this flag is
52 * boot-time reduction
54 * %UBI_VTBL_AUTORESIZE_FLG flag can be set only for one volume in the volume
55 * table. UBI automatically re-sizes the volume which has this flag and makes
56 * the volume to be of largest possible size. This means that if after the
58 * present on the device, it automatically appends all of them to the volume
66 * The auto-resize feature is useful for device production purposes. For
[all …]
|
| /openbmc/u-boot/drivers/mtd/ubi/ |
| H A D | ubi-media.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
13 * This file defines the layout of UBI headers and all the other UBI on-flash
50 * @UBI_VTBL_AUTORESIZE_FLG: auto-resize this volume
52 * %UBI_VTBL_AUTORESIZE_FLG flag can be set only for one volume in the volume
53 * table. UBI automatically re-sizes the volume which has this flag and makes
54 * the volume to be of largest possible size. This means that if after the
56 * present on the device, it automatically appends all of them to the volume
64 * The auto-resize feature is useful for device production purposes. For
68 * exceed certain percent, e.g. 2%. When one creates an UBI image which will be
69 * flashed to the end devices in production, he does not know the exact amount
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | uncore-interconnect.json | 7 …"PublicDescription": "Counts the number of times when an inbound write (from a device to memory or…
16 …"PublicDescription": "Counts the number of times when an inbound write (from a device to memory or…
25 …t have not yet returned their data to the uncore. These writes are generally queued up in the swi…
34 …t have not yet returned their data to the uncore. These writes are generally queued up in the swi…
43 …utstanding in the uncore trying to acquire ownership in each cycle. This can be used with the wri…
52 …utstanding in the uncore trying to acquire ownership in each cycle. This can be used with the wri…
61 …he uncore in each cycle. This can be used with the read transaction count to calculate the averag…
70 …he uncore in each cycle. This can be used with the read transaction count to calculate the averag…
97 …to calculate the average latency in the uncore. The occupancy increments when the ownership fetch…
106 …to calculate the average latency in the uncore. The occupancy increments when the ownership fetch…
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/perf/ |
| H A D | riscv,pmu.yaml | 1 # SPDX-License-Identifier: BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: RISC-V SBI PMU events
10 - Atish Patra <atishp@rivosinc.com>
13 The SBI PMU extension allows supervisor software to configure, start and
18 The platform must provide information about PMU event to counter mappings
19 either via device tree or another way, specific to the platform.
20 Without the event to counter mappings, the SBI PMU extension cannot be used.
25 or another way, specific to the platform.
[all …]
|
| /openbmc/linux/tools/testing/selftests/futex/include/ |
| H A D | futextest.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
13 * 2009-Nov-6: Initial version by Darren Hart <dvhart@linux.intel.com>
28 /* Define the newer op codes if the system header file is not up to date. */
51 * futex() - SYS_futex syscall wrapper
59 * @opflags: flags to be bitwise OR'd with op, such as FUTEX_PRIVATE_FLAG
68 * like-named arguments in the following wrappers except where noted below.
74 * futex_wait() - block on uaddr with optional timeout
84 * futex_wake() - wake one or more tasks blocked on uaddr
85 * @nr_wake: wake up to this many tasks
94 * futex_wait_bitset() - block on uaddr with bitset
[all …]
|
| /openbmc/linux/fs/btrfs/ |
| H A D | raid56.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Copyright (C) 2012 Fusion-io All rights reserved.
35 * bio_list and bio_list_lock are used to add more bios into the stripe
43 * plugging code to collect partial bios while plugged. The stripe
44 * locking code also uses it to hand off the stripe lock to the next
49 /* Flags that tell us if it is safe to merge with this bio. */
58 /* How many pages there are for the full stripe including P/Q */
61 /* How many sectors there are for the full stripe including P/Q */
70 /* How many pages there are for each stripe */
73 /* How many sectors there are for each stripe */
[all …]
|
| /openbmc/phosphor-host-ipmid/docs/ |
| H A D | contributing.md | 3 This document attempts to outline some basic rules to follow when contributing
4 to OpenBMC's IPMI stack. It does _not_ outline coding style; we follow the
5 [OpenBMC C++ style guide](https://github.com/openbmc/docs/blob/master/cpp-style-and-conventions)
10 A good commit does exactly one thing. We prefer many small, atomic commits to
11 one large commit which makes many functional changes.
13 - Too large: "convert foo to new API; also fix CVE 1234 in bar"
14 - Too small: "move abc.h to top of include list" and "move xyz.h to bottom of
16 - Just right: "convert foo to new API" and "convert foo from tab to space"
19 dependent on prior commits; Gerrit handles this situation well, so feel free to
21 possible, your commit should stand alone on top of master - "Fix whitespace in
[all …]
|
| /openbmc/docs/ |
| H A D | hw-vendor-repos-policy.md | 12 a request for a new repository or a bitbake recipe to be hosted under the
19 OpenBMC architecture (bitbake, d-bus, phosphor-dbus-interfaces, ...).
22 guidelines to be used by the OpenBMC TOF in their decision to approve or not
25 Both hardware-specific and vendor-specific repositories should meet the
26 following requirements to be eligible for a repository under OpenBMC:
34 5. It is a feature that is believed to be generally useful to the OpenBMC
36 - Determination made by the TOF
37 - Reference: "Create a new repository" TOF [process][tof]
38 6. It has an active OpenBMC community member that is willing to be a maintainer
40 Note that the first option should always be to look into hosting the repository
[all …]
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | transhuge.rst | 16 But in the future it can expand to other filesystems.
26 requiring larger clear-page copy-page in page faults which is a
32 factor will affect all subsequent accesses to the memory for the whole
44 hugepages but a significant speedup already happens if only one of
46 going to run faster.
48 THP can be enabled system wide or restricted to certain tasks or even
57 if compared to the reservation approach of hugetlbfs by allowing all
58 unused memory to be used as cache or other movable (or even unmovable
59 entities). It doesn't require reservation to prevent hugepage
60 allocation failures to be noticeable from userland. It allows paging
[all …]
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | gadget.rst | 11 This document presents a Linux-USB "Gadget" kernel mode API, for use
14 development project. This is the first such API released on Linux to
17 - Supports USB 2.0, for high speed devices which can stream data at
20 - Handles devices with dozens of endpoints just as well as ones with
21 just two fixed-function ones. Gadget drivers can be written so
22 they're easy to port to new hardware.
24 - Flexible enough to expose more complex USB device capabilities such
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
[all …]
|
| /openbmc/linux/Documentation/input/ |
| H A D | gamepad.rst | 1 ---------------------------
3 ---------------------------
10 Linux provides many different input drivers for gamepad hardware. To avoid
11 having user-space deal with different button-mappings for each gamepad, this
12 document defines how gamepads are supposed to report their data.
25 | <===DP===> |SE| |ST| (W) -|- (E) | |
35 D-Pad Left Right Action Pad
43 - Action-Pad
44 4 buttons in diamonds-shape (on the right side). The buttons are
47 - D-Pad (Direction-pad)
[all …]
|
| /openbmc/u-boot/drivers/core/ |
| H A D | Kconfig | 7 support, including scanning of platform data on start-up. If
15 Enable driver model in SPL. You will need to provide a
19 must provide CONFIG_SPL_SYS_MALLOC_F_LEN to set the size.
22 CONFIG_SPL_SYS_MALLOC_F_LEN for more details on how to enable it.
28 Enable driver model in TPL. You will need to provide a
32 must provide CONFIG_SPL_SYS_MALLOC_F_LEN to set the size.
35 CONFIG_SPL_SYS_MALLOC_F_LEN for more details on how to enable it.
44 strings. By default this is disabled for SPL builds to save space.
45 This will cause dm_warn() to be compiled out - it will do nothing
52 Say Y here if you want to compile in debug messages in DM core.
[all …]
|
| /openbmc/linux/drivers/net/ethernet/8390/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 If you have a network (Ethernet) card belonging to this class, say Y.
13 Note that the answer to this question doesn't directly affect the
14 kernel: saying N will just cause the configurator to skip all
24 Say Y here if you intend to attach an Asix AX88190-based PCMCIA
25 (PC-card) Fast Ethernet card to your computer. These cards are
26 nearly NE2000 compatible but need a separate driver due to a few
29 To compile this driver as a module, choose M here: the module will be
39 AX88796 driver, using platform bus to provide
55 This driver is for the Individual Computers X-Surf 100 Ethernet
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | nvidia,tegra186-gpio.txt | 4 controller. This binding document applies to both controllers. The register
5 layouts for the controllers share many similarities, but also some significant
9 The Tegra186 GPIO controller allows software to set the IO direction of, and
10 read/write the value of, numerous GPIO signals. Routing of GPIO signals to
14 a) Security registers, which allow configuration of allowed access to the GPIO
19 Access to this set of registers is not necessary in all circumstances. Code
20 that wishes to configure access to the GPIO registers needs access to these
21 registers to do so. Code which simply wishes to read or write GPIO data does not
22 need access to these registers.
27 documentation for rationale. Any particular GPIO client is expected to access
[all …]
|
| /openbmc/qemu/include/hw/mem/ |
| H A D | memory-device.h | 10 * See the COPYING file in the top-level directory.
16 #include "hw/qdev-core.h"
17 #include "qapi/qapi-types-machine.h"
20 #define TYPE_MEMORY_DEVICE "memory-device"
33 * All memory devices need to implement TYPE_MEMORY_DEVICE as an interface.
44 * Conceptually, memory devices only span one memory region. If multiple
45 * successive memory regions are used, a covering memory region has to
51 * that are RAM memory regions or aliases to RAM memory regions. Other
55 * memory region container, it's supported to dynamically (un)map subregions
71 * no address has been assigned to this memory device yet.
[all …]
|
| /openbmc/linux/arch/arm/common/ |
| H A D | vlock.S | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * vlock.S - simple voting lock implementation for ARM
5 * Created by: Dave Martin, 2012-08-16
6 * Copyright: (C) 2012-2013 Linaro Limited
15 .arch armv7-a
20 #define MANY(x...) x macro
23 #define MANY(x...) macro
26 @ voting lock for first-man coordination
43 * The vlock structure must reside in Strongly-Ordered or Device memory.
46 * writes to neighbouring locations within a cacheline do not interfere
[all …]
|
| /openbmc/docs/architecture/ |
| H A D | optionality.md | 3 OpenBMC does its best to be widely applicable to all BMC deployments in the
4 world, including many varieties of hardware. To do this requires care in the way
5 new features are developed, to ensure stability of systems over time. With that
6 as a goal, any given feature should fit into one of the following categories.
12 expected to remain widely applicable to all systems.
16 These are subsystems that, while widely applicable, a user might choose to
18 deployment, or not used. This might be done to save binary size in the flash
19 image, or might be done to reduce the security attack surface. These kids of
20 features should be architected to ensure that, when removed, they do not cause
21 functional impacts to other subsystems. Examples of these include the webui,
[all …]
|