| /openbmc/linux/Documentation/netlink/specs/ |
| H A D | devlink.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
10 -
12 name: sb-pool-type
14 -
16 -
19 attribute-sets:
20 -
22 name-prefix: devlink-attr-
24 -
[all …]
|
| /openbmc/linux/drivers/media/cec/platform/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
14 The CEC bus is present in the HDMI connector and enables communication
15 between compatible devices.
25 CEC bus is present in the HDMI connector and enables communication
37 This driver if for the new AO-CEC module found in G12A SoCs,
38 usually named AO_CEC_B in documentation.
40 CEC bus is present in the HDMI connector and enables communication
41 between compatible devices.
44 tristate "Generic GPIO-based CEC driver"
51 This is a generic GPIO-based CEC driver.
[all …]
|
| /openbmc/linux/drivers/mailbox/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
5 Mailbox is a framework to control hardware communication between
6 on-chip processors through queued messages and interrupt driven
16 Apple SoCs have various co-processors required for certain
29 used in Secure mode only.
36 which provides unidirectional mailboxes between processing elements.
52 which can be used in Secure mode only.
60 send short messages between Highbank's A9 cores and the EnergyCore
70 running on the Cortex-M3 rWTM secure processor of the Armada 37xx
79 interprocessor communication involving DSP, IVA1.0 and IVA2 in
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | percpu-refcount.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
7 * This implements a refcount with similar semantics to atomic_t - atomic_inc(),
8 * atomic_dec_and_test() - but percpu.
10 * There's one important difference between percpu refs and normal atomic_t
15 * The refcount will have a range of 0 to ((1U << 31) - 1), i.e. one bit less
16 * than an atomic_t - this is because of the way shutdown works, see
20 * refcount hitting 0 - it can't, if it was in percpu mode. percpu_ref_kill()
21 * puts the ref back in single atomic_t mode, collecting the per cpu refs and
32 * In the aio code, kill_ioctx() is called when we wish to destroy a kioctx; it
44 * once - percpu_ref_kill() does this for you, it returns true once and false if
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/spi/ |
| H A D | cdns,qspi-nor-peripheral-props.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/spi/cdns,qspi-nor-peripheral-props.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Peripheral-specific properties for the Cadence QSPI controller.
10 See spi-peripheral-props.yaml for more info.
13 - Vaishnav Achath <vaishnav.a@ti.com>
16 # cdns,qspi-nor.yaml
17 cdns,read-delay:
20 Delay for read capture logic, in clock cycles.
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/spi/ |
| H A D | spi-cadence.txt | 2 --------------------------------------------
5 - compatible : should be "cdns,qspi-nor"
6 - reg : 1.Physical base address and size of SPI registers map.
8 - clocks : Clock phandles (see clock bindings for details).
9 - cdns,fifo-depth : Size of the data FIFO in words.
10 - cdns,fifo-width : Bus width of the data FIFO in bytes.
11 - cdns,trigger-address : 32-bit indirect AHB trigger address.
12 - cdns,is-decoded-cs : Flag to indicate whether decoder is used or not.
13 - status : enable in requried dts.
16 --------------------------
[all …]
|
| /openbmc/linux/Documentation/input/ |
| H A D | multi-touch-protocol.rst | 4 Multi-touch (MT) Protocol
7 :Copyright: |copy| 2009-2010 Henrik Rydberg <rydberg@euromail.se>
11 ------------
13 In order to utilize the full power of the new multi-touch and multi-user
15 objects in direct contact with the device surface, is needed. This
16 document describes the multi-touch (MT) protocol which allows kernel
30 --------------
34 packet. Since these events are ignored by current single-touch (ST)
36 in an existing driver.
48 All drivers mark the end of a multi-touch transfer by calling the usual
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/memory-controllers/ |
| H A D | ti-aemif.txt | 4 provide a glue-less interface to a variety of asynchronous memory devices like
11 Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
12 OMAP-L138 (DA850) - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
13 Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
17 - compatible: "ti,davinci-aemif"
18 "ti,keystone-aemif"
19 "ti,da850-aemif"
21 - reg: contains offset/length value for AEMIF control registers
24 - #address-cells: Must be 2. The partition number has to be encoded in the
25 first address cell and it may accept values 0..N-1
[all …]
|
| /openbmc/linux/include/linux/sched/ |
| H A D | sd_flags.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * sched-domains (multiprocessor balancing) flag declarations.
15 * is usually because the flag describes some shared resource (all CPUs in that
17 * behaviour that we want to disable at some point in the hierarchy for
20 * In those cases it doesn't make sense to have the flag set for a domain but
21 * not have it in (some of) its children: sched domains ALWAYS span their child
22 * domains, so operations done with parent domains will cover CPUs in the lower
40 * involves equalizing a metric between groups), or for flags describing some
41 * shared resource (which would be shared between groups).
89 * NEEDS_GROUPS: Per-CPU capacity is asymmetric between groups.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/ |
| H A D | arm,coresight-cti.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/arm/arm,coresight-cti.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 to one or more CoreSight components and/or a CPU, with CTIs interconnected in
17 The CTI component properties define the connections between the individual
21 number is defined at design time, the maximum of each defined in the DEVID
24 CTIs are interconnected in a star topology via the CTM, using a number of
26 described in the DEVID register. The star topology is not required to be
27 described in the bindings as the actual connections are software
[all …]
|
| /openbmc/qemu/docs/specs/ |
| H A D | ppc-spapr-numa.rst | 5 NUMA in sPAPR works different than the System Locality Distance
6 Information Table (SLIT) in ACPI. The logic is explained in the LOPAPR
9 of the elements that impacts how QEMU views NUMA in pseries.
12 --------------------------------------------
15 similar mean performance (or in our context here, distance) relative to
19 bit 0 of byte 5 of the ibm,architecture-vec-5 property. The format with
28 Mem M1 ---- Proc P1 |
29 ----------------- | Socket S1 ---|
32 Mem M2 ---- Proc P2 | |
33 ----------------- | Socket S2 ---|
[all …]
|
| /openbmc/linux/Documentation/mm/ |
| H A D | zsmalloc.rst | 6 supposed to work well under low memory conditions. In particular, it
9 (0-order) pages, it would suffer from very high fragmentation --
13 To overcome these issues, zsmalloc allocates a bunch of 0-order pages
15 pages act as a single higher-order page i.e. an object can span 0-order
20 since this satisfies the requirements of all its current users (in the
21 worst case, page is incompressible and is thus stored "as-is" i.e. in
29 issues on 32-bit systems where the VA region for kernel space mappings
59 the number of zspages with usage ratio between 10% and 20%
61 the number of zspages with usage ratio between 20% and 30%
63 the number of zspages with usage ratio between 30% and 40%
[all …]
|
| /openbmc/qemu/include/hw/misc/ |
| H A D | nrf51_rng.h | 5 * + Property "period_unfiltered_us": Time between two biased values in
7 * + Property "period_filtered_us": Time between two unbiased values in
24 * average generation time stated in the production specification;
25 * non-deterministic generation times are not modeled.
27 * Copyright 2018 Steffen Görtz <contrib@steffen-goertz.de>
30 * the COPYING file in the top-level directory.
69 /* Time between generation of successive unfiltered values in us */
71 /* Time between generation of successive filtered values in us */
|
| /openbmc/linux/net/dccp/ccids/lib/ |
| H A D | packet_history.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
4 * Copyright (c) 2005-7 The University of Waikato, Hamilton, New Zealand.
10 * or e-mail Ian McDonald - ian.mcdonald@jandi.co.nz
14 * Copyright (c) 2003 Nils-Erik Mattsson, Joacim Haggmark, Magnus Erixzon
17 * and to make it work as a loadable module in the DCCP stack written by
38 return tfrc_tx_hist_slab == NULL ? -ENOBUFS : 0; in tfrc_tx_packet_history_init()
54 return -ENOBUFS; in tfrc_tx_hist_add()
55 entry->seqno = seqno; in tfrc_tx_hist_add()
56 entry->stamp = ktime_get_real(); in tfrc_tx_hist_add()
57 entry->next = *headp; in tfrc_tx_hist_add()
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | field-order.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _field-order:
9 We have to distinguish between progressive and interlaced video.
13 odd and even field are transmitted, and due to a small delay between
22 fields are in fact captured at two different instances in time. An
23 object on screen may well move between one field and the next. For
29 combine to frames. We distinguish between top (aka odd) and bottom (aka
43 determined by the video standard. Hence the distinction between temporal
47 In V4L it is assumed that all video cameras transmit fields on the media
48 bus in the same order they were captured, so if the top field was
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | uncore-memory.json | 11 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)",
27 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)",
51 …ption": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Read Major Mode",
59 …tion": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Write Major Mode",
70 "PublicDescription": "Uncore Fixed Counter - uclks",
104 …s corrected. The iMC can correct up to 4 bit errors in independent channel mode and 8 bit errors …
108 "BriefDescription": "Cycles in a Major Mode; Isoch Major Mode",
112 …number of cycles spent in a major mode (selected by a filter) on the given channel. Major modea …
117 "BriefDescription": "Cycles in a Major Mode; Partial Major Mode",
121 …number of cycles spent in a major mode (selected by a filter) on the given channel. Major modea …
[all …]
|
| /openbmc/qemu/hw/display/ |
| H A D | framebuffer.h | 19 * @src_width: Number of bytes in framebuffer memory between two rows.
35 * @src_width: Number of bytes in framebuffer memory between two rows.
36 * @dest_row_pitch: Number of bytes in the surface data between two rows.
37 * Negative if the framebuffer is stored in the opposite order (e.g.
38 * bottom-to-top) compared to the framebuffer.
39 * @dest_col_pitch: Number of bytes in the surface data between two pixels.
40 * Negative if the framebuffer is stored in the opposite order (e.g.
41 * right-to-left) compared to the framebuffer.
49 * was drawn (either the last dirty row, or @rows-1 if @invalidate is true).
|
| /openbmc/linux/drivers/accel/habanalabs/common/ |
| H A D | security.h | 1 /* SPDX-License-Identifier: GPL-2.0
3 * Copyright 2016-2022 HabanaLabs, Ltd.
11 #include <linux/io-64-nonatomic-lo-hi.h>
24 * struct hl_special_block_info - stores address details of a particular type of
27 * @block_type: block type as described in every ASIC's block_types enum.
33 * @major_offset: address gap between 2 consecutive major blocks of particular type,
34 * e.g., offset between NIC0_UMR0_0 and NIC1_UMR0_0 is 0x80000.
35 * @minor_offset: address gap between 2 consecutive minor blocks of particular type,
36 * e.g., offset between NIC0_UMR0_0 and NIC0_UMR1_0 is 0x20000.
37 * @sub_minor_offset: address gap between 2 consecutive sub_minor blocks of particular
[all …]
|
| H A D | security.c | 1 // SPDX-License-Identifier: GPL-2.0
11 "Error due to un-priv read",
12 "Error due to un-secure read",
14 "Error due to un-priv write",
15 "Error due to un-secure write",
18 "External I/F write to un-mapped reg",
24 * hl_get_pb_block - return the relevant block within the block array
27 * @mm_reg_addr: register address in the desired block
46 dev_err(hdev->dev, "No protection domain was found for 0x%x\n", in hl_get_pb_block()
48 return -EDOM; in hl_get_pb_block()
[all …]
|
| /openbmc/linux/tools/memory-model/litmus-tests/ |
| H A D | README | 6 Test of read-read coherence, that is, whether or not two
10 Test of read-write coherence, that is, whether or not a read
15 Test of write-read coherence, that is, whether or not a write
20 Test of write-write coherence, that is, whether or not two
25 between each pairs of reads. In other words, is smp_mb()
33 between each pairs of reads. In other words, is anything at all
39 Tests whether the ordering provided by a lock-protected S
45 As below, but with store-release replaced with WRITE_ONCE()
46 and load-acquire replaced with READ_ONCE().
49 Can a release-acquire chain order a prior store against
[all …]
|
| /openbmc/linux/drivers/net/ethernet/freescale/ |
| H A D | ucc_geth.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * Copyright (C) Freescale Semicondutor, Inc. 2006-2009. All rights reserved.
12 * - Rearrange code and style fixes
40 u8 res0[0x100 - sizeof(struct ucc_fast)];
45 u32 hafdup; /* half-duplex reg. */
56 u8 res3[0x180 - 0x15A];
63 frames) transmitted that were between
67 frames) transmitted that were between 128
73 frames) received that were between MINLength
76 frames) received that were between 128
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | ComponentIntegrity.v1_3_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
34 "description": "The available OEM-specific actions for this resource.",
35 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
43 …"longDescription": "This object shall contain common identity-related authentication information.",
45 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
83 "description": "Information about communication between two components.",
84 …"longDescription": "This object shall contain information about communication between two componen…
86 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | ComponentIntegrity.v1_3_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
34 "description": "The available OEM-specific actions for this resource.",
35 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
43 …"longDescription": "This object shall contain common identity-related authentication information.",
45 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
83 "description": "Information about communication between two components.",
84 …"longDescription": "This object shall contain information about communication between two componen…
86 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| /openbmc/linux/drivers/dma-buf/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 userspace via Sync File fds for synchronization between drivers via
14 The first and main user for this is graphics in which a fence is
18 Documentation/driver-api/sync_file.rst.
30 WARNING: improper use of this can result in deadlocking kernel
39 A driver to let userspace turn memfd regions into dma-bufs.
43 bool "Move notify between drivers (EXPERIMENTAL)"
47 Don't pin buffers if the dynamic DMA-buf interface is available on
50 through DMA-buf.
52 execution context and memory management between drivers.
[all …]
|
| /openbmc/linux/Documentation/driver-api/pci/ |
| H A D | p2pdma.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 PCI Peer-to-Peer DMA Support
8 between two devices on the bus. This type of transaction is henceforth
9 called Peer-to-Peer (or P2P). However, there are a number of issues that
10 make P2P transactions tricky to do in a perfectly safe way.
13 transactions between hierarchy domains, and in PCIe, each Root Port
18 same PCI bridge, as such devices are all in the same PCI hierarchy
21 between hierarchies.
23 The second issue is that to make use of existing interfaces in Linux,
33 In a given P2P implementation there may be three or more different
[all …]
|