Home
last modified time | relevance | path

Searched +full:fixed +full:- +full:layout (Results 1 – 25 of 255) sorted by relevance

1234567891011

/linux/Documentation/devicetree/bindings/nvmem/layouts/
H A Dfixed-layout.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/layouts/fixed-layout.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NVMEM layout for fixed NVMEM cells
10 Many NVMEM devices have hardcoded cells layout (offset and size of defined
13 This binding allows defining such NVMEM layout with its cells. It can be used
17 - Rafał Miłecki <rafal@milecki.pl>
21 const: fixed-layout
23 "#address-cells":
[all …]
H A Dnvmem-layout.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/layouts/nvmem-layout.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
11 - Michael Walle <michael@walle.cc>
12 - Miquel Raynal <miquel.raynal@bootlin.com>
18 perform their parsing. The nvmem-layout container is here to describe these.
21 - $ref: fixed-layout.yaml
22 - $ref: kontron,sl28-vpd.yaml
[all …]
H A Du-boot,env.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/nvmem/layouts/u-boot,env.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: U-Boot environment variables layout
10 U-Boot uses environment variables to store device parameters and
14 Data is stored using U-Boot specific formats (variant specific header and NUL
15 separated key-value pairs).
27 - Rafał Miłecki <rafal@milecki.pl>
32 - description: A standalone env data block
[all …]
/linux/arch/arm/boot/dts/ti/omap/
H A Dam335x-bone-common.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2012 Texas Instruments Incorporated - https://www.ti.com/
9 cpu0-supply = <&dcdc2_reg>;
19 stdout-path = "serial0:115200n8";
23 pinctrl-names = "default";
24 pinctrl-0 = <&user_leds_s0>;
26 compatible = "gpio-leds";
31 linux,default-trigger = "heartbeat";
32 default-state = "off";
38 linux,default-trigger = "mmc0";
[all …]
/linux/drivers/nvmem/
H A Dlayouts.c1 // SPDX-License-Identifier: GPL-2.0
3 * NVMEM layout bus handling
10 #include <linux/dma-mapping.h>
11 #include <linux/nvmem-consumer.h>
12 #include <linux/nvmem-provider.h>
31 struct nvmem_layout_driver *drv = to_nvmem_layout_driver(dev->driver); in nvmem_layout_bus_probe()
32 struct nvmem_layout *layout = to_nvmem_layout_device(dev); in nvmem_layout_bus_probe() local
34 if (!drv->probe || !drv->remove) in nvmem_layout_bus_probe()
35 return -EINVAL; in nvmem_layout_bus_probe()
37 return drv->probe(layout); in nvmem_layout_bus_probe()
[all …]
/linux/include/linux/
H A Dnvmem-provider.h1 /* SPDX-License-Identifier: GPL-2.0 */
6 * Copyright (C) 2013 Maxime Ripard <maxime.ripard@free-electrons.com>
36 #define NVMEM_DEVID_NONE (-1)
37 #define NVMEM_DEVID_AUTO (-2)
40 * struct nvmem_keepout - NVMEM register keepout range.
53 * struct nvmem_cell_info - NVMEM cell description
78 * struct nvmem_config - NVMEM device configuration
84 * @cells: Optional array of pre-defined NVMEM cells.
86 * @add_legacy_fixed_of_cells: Read fixed NVMEM cells from old OF syntax.
92 * @read_only: Device is read-only.
[all …]
/linux/Documentation/devicetree/bindings/mtd/partitions/
H A Dlinux,ubi.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 physical flash device and spreads the I/O load (i.e wear-leveling)
16 - Daniel Golle <daniel@makrotopia.org>
19 - $ref: partition.yaml#
30 "^ubi-volume-.*$":
31 $ref: /schemas/mtd/partitions/ubi-volume.yaml#
36 - compatible
41 - |
[all …]
H A Dbrcm,bcm963xx-cfe-nor-partitions.txt4 Most Broadcom BCM63XX SoC based devices follow the Broadcom reference layout for
6 NVRAM partition, and the remainder in-between for one to two firmware partitions
7 at fixed offsets. A valid firmware partition is identified by the ImageTag
12 - compatible : must be "brcm,bcm963xx-cfe-nor-partitions"
17 compatible = "cfi-flash";
19 bank-width = <2>;
22 compatible = "brcm,bcm963xx-cfe-nor-partitions";
/linux/Documentation/devicetree/bindings/nvmem/
H A Dnvmem.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
23 "#address-cells":
26 "#size-cells":
29 read-only:
34 wp-gpios:
36 GPIO to which the write-protect pin of the chip is connected.
37 The write-protect GPIO is asserted, when it's driven high
[all …]
H A Dnvmem-deprecated-cells.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/nvmem-deprecated-cells.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NVMEM old syntax for fixed cells
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
13 Before introducing NVMEM layouts all NVMEM (fixed) cells were defined
14 as direct device subnodes. That syntax was replaced by "fixed-layout"
18 "@[0-9a-f]+(,[0-7])?$":
21 - $ref: layouts/fixed-cell.yaml
[all …]
H A Dxlnx,zynqmp-nvmem.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/xlnx,zynqmp-nvmem.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 - Kalyani Akula <kalyani.akula@amd.com>
15 - Praveen Teja Kundanala <praveen.teja.kundanala@amd.com>
18 - $ref: nvmem.yaml#
22 const: xlnx,zynqmp-nvmem-fw
25 - compatible
30 - |
[all …]
/linux/arch/arm64/boot/dts/renesas/
H A Dr8a779f4.dtsi1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
3 * Device Tree Source for the R-Car S4-8 (R8A779F4) SoC
15 nvmem-layout {
16 compatible = "fixed-layout";
17 #address-cells = <1>;
18 #size-cells = <1>;
27 nvmem-cells = <&ufs_tune>;
28 nvmem-cell-names = "calibration";
/linux/arch/arm/boot/dts/broadcom/
H A Dbcm53016-meraki-mr32.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
6 * Copyright (C) 2018-2020 Christian Lamparter <chunkeey@gmail.com>
9 /dts-v1/;
12 #include "bcm5301x-nand-cs0-bch8.dtsi"
13 #include <dt-bindings/leds/common.h>
33 compatible = "gpio-leds";
39 panic-indicator;
49 compatible = "gpio-keys";
51 button-restart {
58 pwm-leds {
[all …]
H A Dbcm958625-meraki-mx6x-common.dtsi1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
5 * Copyright (C) 2020-2021 Matthew Hagan <mnhagan88@gmail.com>
8 #include "bcm-nsp.dtsi"
9 #include <dt-bindings/gpio/gpio.h>
10 #include <dt-bindings/input/input.h>
11 #include <dt-bindings/leds/common.h>
14 pwm-leds {
15 compatible = "pwm-leds";
17 led-1 {
21 max-brightness = <255>;
[all …]
/linux/arch/arm/boot/dts/nxp/imx/
H A Dimx6qdl-mba6a.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
5 * Copyright 2013-2021 TQ-Systems GmbH
6 * Author: Markus Niebel <Markus.Niebel@tq-group.com>
10 pinctrl-names = "default";
11 pinctrl-0 = <&pinctrl_enet>, <&pinctrl_enet_fix>;
15 lm75: temperature-sensor@49 {
18 vs-supply = <&reg_mba6_3p3v>;
25 vcc-supply = <&reg_mba6_3p3v>;
27 nvmem-layout {
28 compatible = "fixed-layout";
[all …]
H A Dimx6qdl-mba6b.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
5 * Copyright 2013-2021 TQ-Systems GmbH
6 * Author: Markus Niebel <Markus.Niebel@tq-group.com>
10 pinctrl-names = "default";
11 pinctrl-0 = <&pinctrl_enet>;
15 clock-frequency = <100000>;
16 pinctrl-names = "default", "gpio";
17 pinctrl-0 = <&pinctrl_i2c1>;
18 pinctrl-1 = <&pinctrl_i2c1_recovery>;
19 scl-gpios = <&gpio5 27 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
[all …]
/linux/arch/arm/boot/dts/qcom/
H A Dqcom-ipq4018-ap120c-ac.dtsi1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
3 #include "qcom-ipq4019.dtsi"
4 #include <dt-bindings/gpio/gpio.h>
5 #include <dt-bindings/input/input.h>
8 model = "ALFA Network AP120C-AC";
9 compatible = "alfa-network,ap120c-ac", "qcom,ipq4018";
16 stdout-path = "serial0:115200n8";
20 compatible = "gpio-keys";
22 key-reset {
31 i2c0_pins: i2c0-state {
[all …]
/linux/arch/arm64/boot/dts/broadcom/bcmbca/
H A Dbcm4908-asus-gt-ac5300.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
3 #include <dt-bindings/gpio/gpio.h>
4 #include <dt-bindings/input/input.h>
5 #include <dt-bindings/leds/common.h>
10 compatible = "asus,gt-ac5300", "brcm,bcm4908", "brcm,bcmbca";
11 model = "Asus GT-AC5300";
18 gpio-keys-polled {
19 compatible = "gpio-keys-polled";
20 poll-interval = <100>;
22 key-wifi {
[all …]
/linux/Documentation/driver-api/
H A Dioctl.rst18 the ioctl system call. While this can be any 32-bit number that uniquely
22 ``include/uapi/asm-generic/ioctl.h`` provides four macros for defining
36 An 8-bit number, often a character literal, specific to a subsystem
37 or driver, and listed in Documentation/userspace-api/ioctl/ioctl-number.rst
40 An 8-bit number identifying the specific command, unique for a give
45 encodes the ``sizeof(data_type)`` value in a 13-bit or 14-bit integer,
74 handler returns either -ENOTTY or -ENOIOCTLCMD, which also results in
75 -ENOTTY being returned from the system call. Some subsystems return
76 -ENOSYS or -EINVAL here for historic reasons, but this is wrong.
79 -ENOIOCTLCMD in order to use the fallback conversion into native
[all …]
/linux/drivers/gpu/drm/imagination/
H A Dpvr_rogue_fwif_stream.h1 /* SPDX-License-Identifier: GPL-2.0-only OR MIT */
12 * A command stream has the following layout :
13 * - A 64-bit header containing:
16 * - The main stream data.
17 * - The extension stream (optional), which is composed of:
21 * The main stream provides the base command data. This has a fixed layout based on the features
51 * Stream extension header - Geometry 0
60 * Stream extension header - Fragment 0
70 * Stream extension header - Compute 0
/linux/drivers/gpu/drm/nouveau/dispnv50/
H A Dwndwc57e.c35 struct nvif_push *push = &wndw->wndw.push; in wndwc57e_image_set()
42 NVVAL(NVC57E, SET_PRESENT_CONTROL, MIN_PRESENT_INTERVAL, asyw->image.interval) | in wndwc57e_image_set()
43 NVVAL(NVC57E, SET_PRESENT_CONTROL, BEGIN_MODE, asyw->image.mode) | in wndwc57e_image_set()
47 NVVAL(NVC57E, SET_SIZE, WIDTH, asyw->image.w) | in wndwc57e_image_set()
48 NVVAL(NVC57E, SET_SIZE, HEIGHT, asyw->image.h), in wndwc57e_image_set()
51 NVVAL(NVC57E, SET_STORAGE, BLOCK_HEIGHT, asyw->image.blockh) | in wndwc57e_image_set()
52 NVVAL(NVC57E, SET_STORAGE, MEMORY_LAYOUT, asyw->image.layout), in wndwc57e_image_set()
55 NVVAL(NVC57E, SET_PARAMS, FORMAT, asyw->image.format) | in wndwc57e_image_set()
61 NVVAL(NVC57E, SET_PLANAR_STORAGE, PITCH, asyw->image.blocks[0]) | in wndwc57e_image_set()
62 NVVAL(NVC57E, SET_PLANAR_STORAGE, PITCH, asyw->image.pitch[0] >> 6)); in wndwc57e_image_set()
[all …]
/linux/Documentation/arch/arm/
H A Dmemory.rst2 Kernel Memory Layout on ARM Linux
9 This document describes the virtual memory layout which the Linux
39 in proc-xscale.S to flush the whole data
53 ff800000 ffbfffff Permanent, fixed read-only mapping of the
59 VMALLOC_START VMALLOC_END-1 vmalloc() / ioremap() space.
68 PAGE_OFFSET high_memory-1 Kernel direct-mapped RAM region.
72 PKMAP_BASE PAGE_OFFSET-1 Permanent kernel mappings
76 MODULES_VADDR MODULES_END-1 Kernel module space
80 TASK_SIZE MODULES_VADDR-1 KASAn shadow memory when KASan is in use.
85 00001000 TASK_SIZE-1 User space mappings
[all …]
/linux/sound/aoa/soundbus/i2sbus/
H A Dcore.c1 // SPDX-License-Identifier: GPL-2.0-only
5 * Copyright 2006-2008 Johannes Berg <johannes@sipsolutions.net>
12 #include <linux/dma-mapping.h>
32 " no layout-id property is present");
46 r->size = (numcmds + 3) * sizeof(struct dbdma_cmd); in alloc_dbdma_descriptor_ring()
47 /* We use the PCI APIs for now until the generic one gets fixed in alloc_dbdma_descriptor_ring()
114 i2sbus_get_and_fixup_rsrc(struct device_node * np,int index,int layout,struct resource * res) i2sbus_get_and_fixup_rsrc() argument
158 int i, layout = 0, rlen, ok = force; i2sbus_add_dev() local
[all...]
/linux/tools/perf/Documentation/
H A Dintel-hybrid.txt2 ----------
[all...]
/linux/Documentation/fb/
H A Dapi.rst9 ---------------
12 with frame buffer devices. In-kernel APIs between device drivers and the frame
22 ---------------
24 Device and driver capabilities are reported in the fixed screen information
36 - FB_CAP_FOURCC
40 specifying color components layout.
44 --------------------
46 Pixels are stored in memory in hardware-dependent formats. Applications need
58 - FB_TYPE_PACKED_PIXELS
64 Padding at end of lines may be present and is then reported through the fixed
[all …]

1234567891011