Home
last modified time | relevance | path

Searched +full:per +full:- +full:peripheral (Results 1 – 25 of 251) sorted by relevance

1234567891011

/linux-6.8/Documentation/devicetree/bindings/memory-controllers/
Dmc-peripheral-props.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/mc-peripheral-props.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Peripheral-specific properties for a Memory Controller bus.
10 Many Memory Controllers need to add properties to peripheral devices.
13 to be defined in the peripheral node because they are per-peripheral
20 - Marek Vasut <marex@denx.de>
26 bank-width:
32 - reg
[all …]
/linux-6.8/Documentation/spi/
Dpxa2xx.rst7 (see Documentation/spi/spi-summary.rst). The driver has the following features
9 - Support for any PXA2xx and compatible SSP.
10 - SSP PIO and SSP DMA data transfers.
11 - External and Internal (SSPFRM) chip selects.
12 - Per peripheral device (chip) configuration.
13 - Full suspend, freeze, resume support.
21 ---------------------------------
23 arch/.../mach-*/board-*.c as a "platform device". The host controller configuration
33 peripheral devices (chips) attached to this SPI host controller.
40 For the new platforms the description of the controller and peripheral devices
[all …]
/linux-6.8/Documentation/devicetree/bindings/serial/
Dfsl-imx-uart.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/serial/fsl-imx-uart.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Fabio Estevam <festevam@gmail.com>
15 - const: fsl,imx1-uart
16 - const: fsl,imx21-uart
17 - items:
18 - enum:
19 - fsl,imx25-uart
[all …]
/linux-6.8/Documentation/devicetree/bindings/spi/
Dspi-peripheral-props.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/spi/spi-peripheral-props.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Peripheral-specific properties for a SPI bus.
10 Many SPI controllers need to add properties to peripheral devices. They could
11 be common properties like spi-max-frequency, spi-cpha, etc. or they could be
13 need to be defined in the peripheral node because they are per-peripheral and
19 - Mark Brown <broonie@kernel.org>
27 - minimum: 0
[all …]
/linux-6.8/include/linux/dma/
Dimx-dma.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Copyright 2004-2009 Freescale Semiconductor, Inc. All Rights Reserved.
14 * This enumerates peripheral types. Used for SDMA.
29 IMX_DMATYPE_EXT, /* External peripheral */
61 return !strcmp(dev_name(chan->device->dev), "ipu-core"); in imx_dma_is_ipu()
66 return !strcmp(chan->device->dev->driver->name, "imx-sdma") || in imx_dma_is_general_purpose()
67 !strcmp(chan->device->dev->driver->name, "imx-dma"); in imx_dma_is_general_purpose()
71 * struct sdma_peripheral_config - SDMA config for audio
78 * @words_per_fifo: numbers of words per FIFO fetch/fill, 1 means
79 * one channel per FIFO, 2 means 2 channels per FIFO..
[all …]
/linux-6.8/Documentation/driver-api/
Dspi.rst1 Serial Peripheral Interface (SPI)
4 SPI is the "Serial Peripheral Interface", widely used with embedded
7 often in the range of 1-20 MHz), a "Master Out, Slave In" (MOSI) data
9 duplex protocol; for each bit shifted out the MOSI line (one per clock)
12 additional chipselect line is usually active-low (nCS); four signals are
13 normally used for each peripheral, plus sometimes an interrupt.
19 peripherals and does not implement such a peripheral itself. (Interfaces
33 board-specific initialization code. A :c:type:`struct spi_driver
46 .. kernel-doc:: include/linux/spi/spi.h
49 .. kernel-doc:: drivers/spi/spi.c
[all …]
Dsm501.rst15 ----
27 peripheral set as platform devices for the specific drivers.
29 The core re-uses the platform device system as the platform device
31 need to create a new bus-type and the associated code to go with it.
35 ---------
37 Each peripheral has a view of the device which is implicitly narrowed to
38 the specific set of resources that peripheral requires in order to
43 as this is by-far the most resource-sensitive of the on-chip functions.
59 -------------
66 The PCI driver assumes that the PCI card behaves as per the Silicon
[all …]
/linux-6.8/include/drm/
Ddrm_mipi_dsi.h1 /* SPDX-License-Identifier: GPL-2.0-only */
5 * Copyright (C) 2012-2013, Samsung Electronics, Co., Ltd.
18 /* request ACK from peripheral */
24 * struct mipi_dsi_msg - read/write DSI buffer
49 * struct mipi_dsi_packet - represents a MIPI DSI packet in protocol format
67 * struct mipi_dsi_host_ops - DSI bus operations
99 * struct mipi_dsi_host - DSI host device
124 /* enable hsync-end packets in vsync-pulse and v-porch area */
126 /* disable hfront-porch area */
128 /* disable hback-porch area */
[all …]
/linux-6.8/drivers/spi/
Dspi-geni-qcom.c1 // SPDX-License-Identifier: GPL-2.0
2 // Copyright (c) 2017-2018, The Linux foundation. All rights reserved.
6 #include <linux/dma-mapping.h>
7 #include <linux/dma/qcom-gpi-dma.h>
16 #include <linux/soc/qcom/geni-se.h>
108 struct geni_se *se = &mas->se; in spi_slv_setup()
110 writel(SPI_SLAVE_EN, se->base + SE_SPI_SLAVE_EN); in spi_slv_setup()
111 writel(GENI_IO_MUX_0_EN, se->base + GENI_OUTPUT_CTRL); in spi_slv_setup()
112 writel(START_TRIGGER, se->base + SE_GENI_CFG_SEQ_START); in spi_slv_setup()
113 dev_dbg(mas->dev, "spi slave setup done\n"); in spi_slv_setup()
[all …]
/linux-6.8/include/linux/soundwire/
Dsdw_amd.h1 /* SPDX-License-Identifier: GPL-2.0+ */
21 * is invoked. If set, a complete bus reset and re-enumeration will
22 * be performed when the bus restarts. In-band wake interrupts are
57 * struct amd_sdw_manager - amd manager driver context
62 * @reg_mask: register mask structure per manager instance
64 * @amd_sdw_work: peripheral status work queue
67 * @status: peripheral devices status array
74 * @wake_en_mask: wake enable mask per SoundWire manager
/linux-6.8/Documentation/devicetree/bindings/spmi/
Dqcom,spmi-pmic-arb.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/spmi/qcom,spmi-pmic-arb.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Stephen Boyd <sboyd@kernel.org>
14 controller with wrapping arbitration logic to allow for multiple on-chip
21 - $ref: spmi.yaml
25 const: qcom,spmi-pmic-arb
29 - items: # V1
30 - description: core registers
[all …]
/linux-6.8/Documentation/devicetree/bindings/phy/
Dnvidia,tegra186-xusb-padctl.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra186-xusb-padctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
21 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
22 super-speed USB. Other lanes are for various types of low-speed, full-speed
23 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
24 contains a software-configurable mux that sits between the I/O controller
[all …]
Dnvidia,tegra194-xusb-padctl.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra194-xusb-padctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
21 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
22 super-speed USB. Other lanes are for various types of low-speed, full-speed
23 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
24 contains a software-configurable mux that sits between the I/O controller
[all …]
Dnvidia,tegra124-xusb-padctl.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra124-xusb-padctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
21 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
22 super-speed USB. Other lanes are for various types of low-speed, full-speed
23 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
24 contains a software-configurable mux that sits between the I/O controller
[all …]
Dnvidia,tegra210-xusb-padctl.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra210-xusb-padctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
21 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
22 super-speed USB. Other lanes are for various types of low-speed, full-speed
23 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
24 contains a software-configurable mux that sits between the I/O controller
[all …]
/linux-6.8/Documentation/devicetree/bindings/sound/
Dapple,mca.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 MCA is an I2S transceiver peripheral found on M1 and other Apple chips. It is
15 - Martin Povišer <povik+lin@cutebit.org>
18 - $ref: dai-common.yaml#
23 - enum:
24 - apple,t6000-mca
25 - apple,t8103-mca
26 - apple,t8112-mca
[all …]
/linux-6.8/sound/soc/codecs/
Dcs35l56-sdw.c1 // SPDX-License-Identifier: GPL-2.0-only
26 static int cs35l56_sdw_read_one(struct sdw_slave *peripheral, unsigned int reg, void *buf) in cs35l56_sdw_read_one() argument
30 ret = sdw_nread_no_pm(peripheral, reg, 4, (u8 *)buf); in cs35l56_sdw_read_one()
32 dev_err(&peripheral->dev, "Read failed @%#x:%d\n", reg, ret); in cs35l56_sdw_read_one()
45 struct sdw_slave *peripheral = context; in cs35l56_sdw_read() local
54 return cs35l56_sdw_read_one(peripheral, reg, val_buf); in cs35l56_sdw_read()
57 bytes = SDW_REG_NO_PAGE - (reg & SDW_REGADDR); /* to end of page */ in cs35l56_sdw_read()
61 ret = sdw_nread_no_pm(peripheral, reg, bytes, buf8); in cs35l56_sdw_read()
63 dev_err(&peripheral->dev, "Read failed @%#x..%#x:%d\n", in cs35l56_sdw_read()
64 reg, reg + bytes - 1, ret); in cs35l56_sdw_read()
[all …]
/linux-6.8/Documentation/driver-api/usb/
Dgadget.rst11 This document presents a Linux-USB "Gadget" kernel mode API, for use
17 - Supports USB 2.0, for high speed devices which can stream data at
18 several dozen megabytes per second.
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
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
32 API. This helps the OTG support, and looks forward to more-symmetric
[all …]
/linux-6.8/Documentation/devicetree/bindings/pinctrl/
Datmel,at91-pinctrl.txt10 Please refer to pinctrl-bindings.txt in this directory for details of the
18 such as pull-up, multi drive, etc.
21 - compatible: "atmel,at91rm9200-pinctrl" or "atmel,at91sam9x5-pinctrl"
22 or "atmel,sama5d3-pinctrl" or "microchip,sam9x60-pinctrl"
23 - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
28 Each column will represent the possible peripheral of the pinctrl
32 Peripheral: 2 ( A and B)
41 For each peripheral/bank we will describe in a u32 if a pin can be
44 Let's take the pioA on peripheral B
45 From the datasheet Table 10-2.
[all …]
/linux-6.8/drivers/gpio/
Dgpio-realtek-otto.c1 // SPDX-License-Identifier: GPL-2.0-only
19 * Pin select: (0) "normal", (1) "dedicate peripheral"
20 * Not used on RTL8380/RTL8390, peripheral selection is managed by control bits
21 * in the peripheral registers.
29 /* Two bits per GPIO in IMR registers */
42 * realtek_gpio_ctrl - Realtek Otto GPIO driver data
49 * @bank_read: Read a bank setting as a single 32-bit value
50 * @bank_write: Write a bank setting as a single 32-bit value
53 * The DIR, DATA, and ISR registers consist of four 8-bit port values, packed
54 * into a single 32-bit register. Use @bank_read (@bank_write) to get (assign)
[all …]
/linux-6.8/Documentation/devicetree/bindings/dma/
Dst,stm32-dma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/st,stm32-dma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The STM32 DMA is a general-purpose direct memory access controller capable of
13 described in the dma.txt file, using a four-cell specifier for each
19 -bit 9: Peripheral Increment Address
22 -bit 10: Memory Increment Address
25 -bit 15: Peripheral Increment Offset Size
26 0x0: offset size is linked to the peripheral bus width
[all …]
Dimg-mdc-dma.txt1 * IMG Multi-threaded DMA Controller (MDC)
4 - compatible: Must be "img,pistachio-mdc-dma".
5 - reg: Must contain the base address and length of the MDC registers.
6 - interrupts: Must contain all the per-channel DMA interrupts.
7 - clocks: Must contain an entry for each entry in clock-names.
8 See ../clock/clock-bindings.txt for details.
9 - clock-names: Must include the following entries:
10 - sys: MDC system interface clock.
11 - img,cr-periph: Must contain a phandle to the peripheral control syscon
13 - img,max-burst-multiplier: Must be the maximum supported burst size multiplier.
[all …]
Dnvidia,tegra20-apbdma.txt4 - compatible: Should be "nvidia,<chip>-apbdma"
5 - reg: Should contain DMA registers location and length. This should include
6 all of the per-channel registers.
7 - interrupts: Should contain all of the per-channel DMA interrupts.
8 - clocks: Must contain one entry, for the module clock.
9 See ../clocks/clock-bindings.txt for details.
10 - resets : Must contain an entry for each entry in reset-names.
12 - reset-names : Must include the following entries:
13 - dma
14 - #dma-cells : Must be <1>. This dictates the length of DMA specifiers in
[all …]
/linux-6.8/Documentation/devicetree/bindings/interrupt-controller/
Dbrcm,bcm2836-l1-intc.txt1 BCM2836 per-CPU interrupt controller
3 The BCM2836 has a per-cpu interrupt controller for the timer, PMU
5 peripheral (GPU) events, which chain to the BCM2835-style interrupt
10 - compatible: Should be "brcm,bcm2836-l1-intc"
11 - reg: Specifies base physical address and size of the
13 - interrupt-controller: Identifies the node as an interrupt controller
14 - #interrupt-cells: Specifies the number of cells needed to encode an
32 compatible = "brcm,bcm2836-l1-intc";
34 interrupt-controller;
35 #interrupt-cells = <2>;
[all …]
/linux-6.8/include/linux/platform_data/
Ddma-dw.h1 /* SPDX-License-Identifier: GPL-2.0 */
6 * Copyright (C) 2010-2011 ST Microelectronics
22 * struct dw_dma_slave - Controller-specific information about a slave
28 * @p_master: peripheral master for transfers on allocated channel
43 * struct dw_dma_platform_data - Controller configuration parameters
49 * @data_width: Maximum data width supported by hardware per AHB master
51 * @multi_block: Multi block transfers supported by hardware per channel.
53 * per channel (in units of CTL.SRC_TR_WIDTH/CTL.DST_TR_WIDTH).
54 * @protctl: Protection control signals setting per channel.

1234567891011