Home
last modified time | relevance | path

Searched +full:fsi +full:- +full:slave +full:- +full:engine (Results 1 – 15 of 15) sorted by relevance

/linux/Documentation/devicetree/bindings/fsi/
H A Dfsi.txt1 FSI bus & engine generic device tree bindings
4 The FSI bus is probe-able, so the OS is able to enumerate FSI slaves, and
6 nodes to probed engines. This allows for fsi engines to expose non-probeable
7 busses, which are then exposed by the device tree. For example, an FSI engine
8 that is an I2C master - the I2C bus can be described by the device tree under
9 the engine's device tree node.
11 FSI masters may require their own DT nodes (to describe the master HW itself);
13 the fsi-master-* binding specifications.
16 represent the FSI slaves and their slave engines. As a basic outline:
18 fsi-master {
[all …]
H A Dibm,p9-sbefifo.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/fsi/ibm,p9-sbefifo.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM FSI-attached SBEFIFO engine
10 - Eddie James <eajames@linux.ibm.com>
13 The SBEFIFO is an FSI CFAM engine that provides an interface to the
14 POWER processor Self Boot Engine (SBE). This node will always be a child
15 of an FSI CFAM node.
20 - ibm,p9-sbefifo
[all …]
H A Dibm,fsi2spi.yaml1 # SPDX-License-Identifier: (GPL-2.0-or-later)
3 ---
4 $id: http://devicetree.org/schemas/fsi/ibm,fsi2spi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM FSI-attached SPI controllers
10 - Eddie James <eajames@linux.ibm.com>
13 This binding describes an FSI CFAM engine called the FSI2SPI. Therefore this
14 node will always be a child of an FSI CFAM node. This FSI2SPI engine provides
20 - ibm,fsi2spi
24 - description: FSI slave address
[all …]
H A Dibm,p9-scom.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/fsi/ibm,p9-scom.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM FSI-attached SCOM engine
10 - Eddie James <eajames@linux.ibm.com>
13 The SCOM engine is an interface to the POWER processor PIB (Pervasive
14 Interconnect Bus). This node will always be a child of an FSI CFAM node.
19 - ibm,p9-scom
20 - ibm,i2cr-scom
[all …]
/linux/drivers/fsi/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # FSI subsystem
6 menuconfig FSI config
7 tristate "FSI support"
11 FSI - the FRU Support Interface - is a simple bus for low-level
12 access to POWER-based hardware.
14 if FSI
17 bool "Create '/dev/fsi' directory for char devices"
20 This option causes char devices created for FSI devices to be
21 located under a common /dev/fsi/ directory. Set to N unless your
[all …]
H A Dfsi-core.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * FSI core driver
8 * - Rework topology
9 * - s/chip_id/chip_loc
10 * - s/cfam/chip (cfam_id -> chip_id etc...)
15 #include <linux/fsi.h>
27 #include "fsi-master.h"
28 #include "fsi-slave.h"
31 #include <trace/events/fsi.h>
51 * FSI slave engine control register offsets
[all …]
H A Dfsi-master-hub.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * FSI hub master driver
9 #include <linux/fsi.h>
14 #include "fsi-master.h"
21 * FSI hub master support
24 * primary FSI master can access. For each link a primary master supports,
28 * The hub is controlled by a set of control registers exposed as a regular fsi
29 * device (the hub->upstream device), and provides access to the downstream FSI
30 * bus as through an address range on the slave itself (->addr and ->size).
33 * bus entirely through the fsi device address range, and so have a smaller
[all …]
H A Dfsi-sbefifo.c1 // SPDX-License-Identifier: GPL-2.0
18 #include <linux/fsi.h>
19 #include <linux/fsi-sbefifo.h>
35 #include <uapi/linux/fsi.h>
38 * The SBEFIFO is a pipe-like FSI device for communicating with
39 * the self boot engine on POWER processors.
50 #define SBEFIFO_UP 0x00 /* FSI -> Host */
51 #define SBEFIFO_DOWN 0x40 /* Host -> FSI */
53 /* Per-bank registers */
85 SBE_STATE_IPLING = 0x1, // IPL'ing - autonomous mode (transient)
[all …]
/linux/Documentation/devicetree/bindings/i2c/
H A Dibm,i2c-fsi.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/i2c/ibm,i2c-fsi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM FSI-attached I2C controller
10 - Eddie James <eajames@linux.ibm.com>
13 This I2C controller is an FSI CFAM engine, providing access to a number of
14 I2C busses. Therefore this node will always be a child of an FSI CFAM node.
19 - ibm,i2c-fsi
23 - description: FSI slave address
[all …]
/linux/drivers/spi/
H A Dspi-fsi.c1 // SPDX-License-Identifier: GPL-2.0-or-later
6 #include <linux/fsi.h>
71 struct fsi_device *fsi; /* FSI2SPI CFAM engine device */ member
86 static int fsi_spi_check_mux(struct fsi_device *fsi, struct device *dev) in fsi_spi_check_mux() argument
92 rc = fsi_slave_read(fsi->slave, FSI_MBOX_ROOT_CTRL_8, &root_ctrl_8_be, in fsi_spi_check_mux()
103 return -ENOLINK; in fsi_spi_check_mux()
112 rc = fsi_device_read(ctx->bridge->fsi, FSI2SPI_STATUS, &sts_be, in fsi_spi_check_status()
119 dev_err(ctx->dev, "Error with FSI2SPI interface: %08x.\n", sts); in fsi_spi_check_status()
120 return -EIO; in fsi_spi_check_status()
131 u32 cmd = offset + ctx->base; in fsi_spi_read_reg()
[all …]
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
13 dynamic device discovery; some are even write-only or read-only.
17 chips, analog to digital (and d-to-a) converters, and more.
36 # MASTER side ... talking to discrete SPI slave chips including microcontrollers
44 If your system has an master-capable SPI controller (which
46 controller and the protocol drivers for the SPI slave chips
56 by providing a high-level interface to send memory-like commands.
66 This enables support for SPI-NAND mode on the Airoha NAND
68 is implemented as a SPI-MEM controller.
90 to a SPI slave to Avalon bridge in a Intel MAX BMC.
[all …]
H A DMakefile1 # SPDX-License-Identifier: GPL-2.0
6 ccflags-$(CONFIG_SPI_DEBUG) := -DDEBUG
8 # small core, mostly translating board-specific
10 obj-$(CONFIG_SPI_MASTER) += spi.o
11 obj-$(CONFIG_SPI_MEM) += spi-mem.o
12 obj-$(CONFIG_SPI_MUX) += spi-mux.o
13 obj-$(CONFIG_SPI_SPIDEV) += spidev.o
14 obj-$(CONFIG_SPI_LOOPBACK_TEST) += spi-loopback-test.o
17 obj-$(CONFIG_SPI_AIROHA_SNFI) += spi-airoha-snfi.o
18 obj-$(CONFIG_SPI_ALTERA) += spi-altera-platform.o
[all …]
/linux/drivers/i2c/busses/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
16 for Cypress CCGx Type-C controller. Individual bus drivers
25 controller is part of the 7101 device, which is an ACPI-compliant
29 will be called i2c-ali1535.
37 controller is part of the 7101 device, which is an ACPI-compliant
41 will be called i2c-ali1563.
51 will be called i2c-ali15x3.
63 will be called i2c-amd756.
70 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
76 will be called i2c-amd756-s4882.
[all …]
/linux/arch/sh/kernel/cpu/sh4a/
H A Dsetup-sh7724.c1 // SPDX-License-Identifier: GPL-2.0
30 #include <cpu/dma-register.h>
189 .slave = sh7724_dmae_slaves,
223 /* IRQ for channels 0-3 */
229 /* IRQ for channels 4-5 */
257 /* IRQ for channels 0-3 */
263 /* IRQ for channels 4-5 */
271 .name = "sh-dma-engine",
281 .name = "sh-dma-engine",
303 .name = "sh-sci",
[all …]
/linux/
H A DMAINTAINERS5 ---------------------------------------------------
21 W: *Web-page* with status/info
23 B: URI for where to file *bugs*. A web-page with detailed bug
28 patches to the given subsystem. This is either an in-tree file,
29 or a URI. See Documentation/maintainer/maintainer-entry-profile.rst
46 N: [^a-z]tegra all files whose path contains tegra
64 ----------------
83 3WARE SAS/SATA-RAID SCSI DRIVERS (3W-XXXX, 3W-9XXX, 3W-SAS)
85 L: linux-scsi@vger.kernel.org
88 F: drivers/scsi/3w-*
[all …]