| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/regulator/ |
| D | renesas,raa215300.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Biju Das <biju.das.jz@bp.renesas.com>
13 The RAA215300 is a high-performance, low-cost 9-channel PMIC designed for
14 32-bit and 64-bit MCU and MPU applications. It supports DDR3, DDR3L, DDR4,
16 built-in Real-Time Clock (RTC), 32kHz crystal oscillator, and coin cell
18 ideal for System-On-Module (SOM) applications. A spread spectrum feature
19 provides an ease-of-use solution for noise-sensitive audio or RF applications.
25 …-power-management/multi-channel-power-management-ics-pmics/ssdsoc-power-management-ics-pmic-and-pm…
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/vc04_services/interface/ |
| D | TODO | 4 some of the ones we want:
6 - vc_mem (https://github.com/raspberrypi/linux/blob/rpi-4.4.y/drivers/char/broadcom/vc_mem.c)
12 - VCSM (https://github.com/raspberrypi/linux/tree/rpi-4.4.y/drivers/char/broadcom/vc_sm)
14 This driver is used for talking about regions of VC memory across
16 to manage these buffers as dmabufs so that we can zero-copy import
19 2) Garbage-collect unused code
21 One of the reasons this driver wasn't upstreamed previously was that
23 days. Once we have the set of VCHI-using drivers we want in tree, we
24 should be able to do a sweep of the code to see what's left that's
32 vchiq_test -f 1
[all …]
|
| /kernel/linux/linux-6.6/drivers/scsi/isci/ |
| D | remote_node_table.h | 7 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
10 * it under the terms of version 2 of the GNU General Public License as
14 * WITHOUT ANY WARRANTY; without even the implied warranty of
18 * You should have received a copy of the GNU General Public License
20 * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
26 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
29 * Redistribution and use in source and binary forms, with or without
33 * * Redistributions of source code must retain the above copyright
34 * notice, this list of conditions and the following disclaimer.
36 * notice, this list of conditions and the following disclaimer in
[all …]
|
| /kernel/linux/linux-5.10/drivers/scsi/isci/ |
| D | remote_node_table.h | 7 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
10 * it under the terms of version 2 of the GNU General Public License as
14 * WITHOUT ANY WARRANTY; without even the implied warranty of
18 * You should have received a copy of the GNU General Public License
20 * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
26 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
29 * Redistribution and use in source and binary forms, with or without
33 * * Redistributions of source code must retain the above copyright
34 * notice, this list of conditions and the following disclaimer.
36 * notice, this list of conditions and the following disclaimer in
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | renesas,rza1-ports.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/renesas,rza1-ports.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacopo Mondi <jacopo+renesas@jmondi.org>
11 - Geert Uytterhoeven <geert+renesas@glider.be>
14 The Renesas SoCs of the RZ/A1 family feature a combined Pin and GPIO
16 Pin multiplexing and GPIO configuration is performed on a per-pin basis
17 writing configuration values to per-port register sets.
18 Each "port" features up to 16 pins, each of them configurable for GPIO
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | renesas,rza1-ports.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/renesas,rza1-ports.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacopo Mondi <jacopo+renesas@jmondi.org>
11 - Geert Uytterhoeven <geert+renesas@glider.be>
14 The Renesas SoCs of the RZ/A1 family feature a combined Pin and GPIO
16 Pin multiplexing and GPIO configuration is performed on a per-pin basis
17 writing configuration values to per-port register sets.
18 Each "port" features up to 16 pins, each of them configurable for GPIO
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/fpga/ |
| D | fpga-mgr.rst | 5 --------
7 The FPGA manager core exports a set of functions for programming an FPGA with
9 hidden away in a low level driver which registers a set of ops with the core.
15 memory for the buffer should be avoided, users are encouraged to use a scatter
20 FPGA image as well as image-specific particulars such as whether the image was
24 --------------------------------
26 To add another FPGA manager, write a driver that implements a set of ops. The
39 struct device *dev = &pdev->dev;
46 return -ENOMEM;
72 Alternatively, the probe function could call one of the resource managed
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_fru_eeprom.c | 4 * Permission is hereby granted, free of charge, to any person obtaining a
5 * copy of this software and associated documentation files (the "Software"),
7 * the rights to use, copy, modify, merge, publish, distribute, sublicense,
8 * and/or sell copies of the Software, and to permit persons to whom the
12 * all copies or substantial portions of the Software.
14 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
15 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
18 * OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
19 * ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
38 * TODO: See if we can figure this out dynamically instead of in is_fru_eeprom_supported()
[all …]
|
| D | mes_api_def.h | 4 * Permission is hereby granted, free of charge, to any person obtaining a
5 * copy of this software and associated documentation files (the "Software"),
7 * the rights to use, copy, modify, merge, publish, distribute, sublicense,
8 * and/or sell copies of the Software, and to permit persons to whom the
12 * all copies or substantial portions of the Software.
14 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
15 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
18 * OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
19 * ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
32 * for all API to ease the debugging and parsing of ring buffer.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/devlink/ |
| D | devlink-info.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
7 The ``devlink-info`` mechanism enables device drivers to report device
10 The original motivation for the ``devlink-info`` API was twofold:
12 - making it possible to automate device and firmware management in a fleet
13 of machines in a vendor-independent fashion (see also
14 :ref:`Documentation/networking/devlink/devlink-flash.rst <devlink_flash>`);
15 - name the per component FW versions (as opposed to the crowded ethtool
18 ``devlink-info`` supports reporting multiple types of objects. Reporting driver
19 versions is generally discouraged - here, and via any other Linux API.
21 .. list-table:: List of top level info objects
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | devlink-info.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
7 The ``devlink-info`` mechanism enables device drivers to report device
10 The original motivation for the ``devlink-info`` API was twofold:
12 - making it possible to automate device and firmware management in a fleet
13 of machines in a vendor-independent fashion (see also
14 :ref:`Documentation/networking/devlink/devlink-flash.rst <devlink_flash>`);
15 - name the per component FW versions (as opposed to the crowded ethtool
18 ``devlink-info`` supports reporting multiple types of objects. Reporting driver
19 versions is generally discouraged - here, and via any other Linux API.
21 .. list-table:: List of top level info objects
[all …]
|
| /kernel/linux/linux-6.6/Documentation/bpf/ |
| D | map_array.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
9 - ``BPF_MAP_TYPE_ARRAY`` was introduced in kernel version 3.19
10 - ``BPF_MAP_TYPE_PERCPU_ARRAY`` was introduced in version 4.6
13 storage. The key type is an unsigned 32-bit integer (4 bytes) and the map is
14 of constant size. The size of the array is defined in ``max_entries`` at
15 creation time. All array elements are pre-allocated and zero initialized when
18 stored can be of any size, however, all array elements are aligned to 8
22 setting the flag ``BPF_F_MMAPABLE``. The map definition is page-aligned and
23 starts on the first page. Sufficient page-sized and page-aligned blocks of
25 which in some cases will result in over-allocation of memory. The benefit of
[all …]
|
| D | ringbuf.rst | 12 ----------
15 existing perf buffer, which prompted creation of a new ring buffer
18 - more efficient memory utilization by sharing ring buffer across CPUs;
19 - preserving ordering of events that happen sequentially in time, even across
23 Both are a result of a choice to have per-CPU perf ring buffer. Both can be
24 also solved by having an MPSC implementation of ring buffer. The ordering
25 problem could technically be solved for perf buffer with some in-kernel
30 ------------------
32 Single ring buffer is presented to BPF programs as an instance of BPF map of
37 ``BPF_MAP_TYPE_RINGBUF`` could represent an array of ring buffers, but not
[all …]
|
| /kernel/linux/linux-6.6/samples/bpf/ |
| D | xdp2skb_meta.sh | 3 # SPDX-License-Identifier: GPL-2.0
6 # Bash-shell example on using iproute2 tools 'tc' and 'ip' to load
8 # wrappers and even long options parsing is illustrated, for ease of
9 # use.
11 # Related to sample/bpf/xdp2skb_meta_kern.c, which contains BPF-progs
19 [ -z "$TC" ] && TC=tc
20 [ -z "$IP" ] && IP=ip
24 echo "Usage: $0 [-vfh] --dev ethX"
25 echo " -d | --dev : Network device (required)"
26 echo " --flush : Cleanup flush TC and XDP progs"
[all …]
|
| /kernel/linux/linux-5.10/samples/bpf/ |
| D | xdp2skb_meta.sh | 3 # SPDX-License-Identifier: GPL-2.0
6 # Bash-shell example on using iproute2 tools 'tc' and 'ip' to load
8 # wrappers and even long options parsing is illustrated, for ease of
9 # use.
11 # Related to sample/bpf/xdp2skb_meta_kern.c, which contains BPF-progs
19 [ -z "$TC" ] && TC=tc
20 [ -z "$IP" ] && IP=ip
24 echo "Usage: $0 [-vfh] --dev ethX"
25 echo " -d | --dev : Network device (required)"
26 echo " --flush : Cleanup flush TC and XDP progs"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/serial/ |
| D | rocket.rst | 9 ----------------
13 high-speed serial ports or modems. This driver supports up to a combination
14 of four RocketPort or RocketModems boards in one machine simultaneously.
43 There is a set of utilities and scripts provided with the external driver
44 (downloadable from http://www.comtrol.com) that ease the configuration and
45 setup of the ISA cards.
52 -----------------------
59 command from the root of the Linux source tree during the kernel build process.
64 installed in the system, the mapping of port names to serial ports is displayed
70 "alias char-major-46 rocket".
[all …]
|
| /kernel/linux/linux-5.10/Documentation/bpf/ |
| D | ringbuf.rst | 12 ----------
15 existing perf buffer, which prompted creation of a new ring buffer
18 - more efficient memory utilization by sharing ring buffer across CPUs;
19 - preserving ordering of events that happen sequentially in time, even across
23 Both are a result of a choice to have per-CPU perf ring buffer. Both can be
24 also solved by having an MPSC implementation of ring buffer. The ordering
25 problem could technically be solved for perf buffer with some in-kernel
30 ------------------
32 Single ring buffer is presented to BPF programs as an instance of BPF map of
37 ``BPF_MAP_TYPE_RINGBUF`` could represent an array of ring buffers, but not
[all …]
|
| /kernel/linux/linux-6.6/Documentation/gpu/ |
| D | introduction.rst | 5 The Linux DRM layer contains code intended to support the needs of
8 make use of DRM functions to make tasks like memory management,
17 [Insert diagram of typical DRM stack here]
23 are written as all-uppercase, for example: DRM, KMS, IOCTL, CRTC, and so
24 on. To aid in reading, documentations make full use of the markup
29 entries in function vtables (and structure members in general) please use
37 documentation than runtime noise this provides more value. And on top of
44 Functions which have a non-\ ``void`` return value should have a section
47 section name should be all upper-case or not, and whether it should end
48 in a colon or not. Go with the file-local style. Other common section
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/util/ |
| D | record.c | 1 // SPDX-License-Identifier: GPL-2.0
6 #include "parse-events.h"
11 #include <subcmd/parse-options.h>
16 #include "../perf-sys.h"
26 struct evsel *leader = evsel->leader; in evsel__read_sampler()
30 if (evsel->leader == leader && evsel != evsel->leader) in evsel__read_sampler()
41 struct list_head *config_terms = &evsel->config_terms; in evsel__config_term_mask()
45 term_types |= 1 << term->type; in evsel__config_term_mask()
52 struct perf_event_attr *attr = &evsel->core.attr; in evsel__config_leader_sampling()
53 struct evsel *leader = evsel->leader; in evsel__config_leader_sampling()
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_fru_eeprom.c | 4 * Permission is hereby granted, free of charge, to any person obtaining a
5 * copy of this software and associated documentation files (the "Software"),
7 * the rights to use, copy, modify, merge, publish, distribute, sublicense,
8 * and/or sell copies of the Software, and to permit persons to whom the
12 * all copies or substantial portions of the Software.
14 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
15 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
18 * OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
19 * ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
38 * TODO: See if we can figure this out dynamically instead of in is_fru_eeprom_supported()
[all …]
|
| /kernel/linux/linux-6.6/drivers/cpufreq/ |
| D | maple-cpufreq.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2011 Dmitry Eremin-Solenikov
4 * Copyright (C) 2002 - 2005 Benjamin Herrenschmidt <benh@kernel.crashing.org>
5 * and Markus Demleitner <msdemlei@cl.uni-heidelberg.de>
26 #include <linux/of.h>
66 /* Power mode data is an array of the 32 bits PCR values to use for
67 * the various frequencies, retrieved from the device-tree
164 int rc = -ENODEV; in maple_cpufreq_init()
168 * to ease merging of two drivers in future. in maple_cpufreq_init()
189 /* Look for the powertune data in the device-tree */ in maple_cpufreq_init()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | xfs-maintainer-entry-profile.rst | 5 --------
6 XFS is a well known high-performance filesystem in the Linux kernel.
7 The aim of this project is to provide and maintain a robust and
10 Patches are generally merged to the for-next branch of the appropriate
12 After a testing period, the for-next branch is merged to the master
15 Kernel code are merged to the xfs-linux tree[0].
18 Ondisk format documentation are merged to the xfs-documentation tree[3].
21 list linux-xfs@vger.kernel.org.
24 -----
31 - **Outside Contributor**: Anyone who sends a patch but is not involved
[all …]
|
| /kernel/linux/linux-5.10/drivers/cpufreq/ |
| D | maple-cpufreq.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2011 Dmitry Eremin-Solenikov
4 * Copyright (C) 2002 - 2005 Benjamin Herrenschmidt <benh@kernel.crashing.org>
5 * and Markus Demleitner <msdemlei@cl.uni-heidelberg.de>
66 /* Power mode data is an array of the 32 bits PCR values to use for
67 * the various frequencies, retrieved from the device-tree
164 int rc = -ENODEV; in maple_cpufreq_init()
168 * to ease merging of two drivers in future. in maple_cpufreq_init()
189 /* Look for the powertune data in the device-tree */ in maple_cpufreq_init()
191 * On Maple this property is provided by PIBS in dual-processor config, in maple_cpufreq_init()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/core-api/irq/ |
| D | irq-domain.rst | 5 The current design of the Linux kernel uses a single large number
9 that each one gets assigned non-overlapping allocations of Linux
12 The number of interrupt controllers registered as unique irqchips
13 show a rising tendency: for example subdrivers of different kinds
18 Here the interrupt number loose all kind of correspondence to
24 For this reason we need a mechanism to separate controller-local
27 The irq_alloc_desc*() and irq_free_desc*() APIs provide allocation of
28 irq numbers, but they don't provide any support for reverse mapping of
29 the controller-local IRQ (hwirq) number into the Linux IRQ number
33 top of the irq_alloc_desc*() API. An irq_domain to manage mapping is
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/util/ |
| D | record.c | 1 // SPDX-License-Identifier: GPL-2.0
6 #include "parse-events.h"
11 #include <subcmd/parse-options.h>
16 #include "../perf-sys.h"
19 #include "mem-events.h"
44 struct list_head *config_terms = &evsel->config_terms; in evsel__config_term_mask()
48 term_types |= 1 << term->type; in evsel__config_term_mask()
55 struct perf_event_attr *attr = &evsel->core.attr; in evsel__config_leader_sampling()
60 if (!leader->sample_read) in evsel__config_leader_sampling()
71 * config terms or the leader. In the case of an AUX area event, the 2nd in evsel__config_leader_sampling()
[all …]
|