Home
last modified time | relevance | path

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

/linux/Documentation/devicetree/bindings/fsi/
H A Dibm,p9-fsi-controller.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/fsi/ibm,p9-fsi-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM FSI-attached FSI Hub Controller
10 - Eddie James <eajames@linux.ibm.com>
13 The FSI Hub Controller is an FSI controller, providing a number of FSI links,
14 located on a CFAM. Therefore this node will always be a child of an FSI CFAM
20 - ibm,p9-fsi-controller
24 - description: FSI slave address
[all …]
H A Dibm,p9-occ.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/fsi/ibm,p9-occ.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM FSI-attached On-Chip Controller (OCC)
10 - Eddie James <eajames@linux.ibm.com>
13 The POWER processor On-Chip Controller (OCC) helps manage power and
14 thermals for the system, accessed through the FSI-attached SBEFIFO
20 - ibm,p9-occ
21 - ibm,p10-occ
[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
15 of an FSI CFAM node.
20 - ibm,p9-sbefifo
21 - ibm,odyssey-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>
14 Interconnect Bus). This node will always be a child of an FSI CFAM node.
19 - ibm,p9-scom
20 - ibm,i2cr-scom
24 - description: FSI slave address
[all …]
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-fsi1 What: /sys/bus/platform/devices/../fsi-master/fsi0/rescan
4 Contact: linux-fsi@lists.ozlabs.org
6 Initiates a FSI master scan for all connected slave devices
9 What: /sys/bus/platform/devices/../fsi-master/fsi0/break
12 Contact: linux-fsi@lists.ozlabs.org
14 Sends an FSI BREAK command on a master's communication
19 What: /sys/bus/platform/devices/../fsi-master/fsi0/slave@00:00/term
22 Contact: linux-fsi@lists.ozlabs.org
24 Sends an FSI terminate command from the master to its
32 What: /sys/bus/platform/devices/../fsi-master/fsi0/slave@00:00/raw
[all …]
/linux/Documentation/devicetree/bindings/spi/
H A Dibm,spi-fsi.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/spi/ibm,spi-fsi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM FSI-attached SPI Controller
10 - Eddie James <eajames@linux.ibm.com>
13 A SPI controller found on IBM Power processors, accessed over FSI from a
20 - ibm,spi-fsi
26 - compatible
27 - reg
[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/i2c/busses/
H A Di2c-fsi.c1 // SPDX-License-Identifier: GPL-2.0+
3 * FSI-attached I2C controller algorithm
18 #include <linux/fsi.h>
149 struct fsi_device *fsi; member
163 static int fsi_i2c_read_reg(struct fsi_device *fsi, unsigned int reg, in fsi_i2c_read_reg() argument
169 rc = fsi_device_read(fsi, reg, &data_be, sizeof(data_be)); in fsi_i2c_read_reg()
178 static int fsi_i2c_write_reg(struct fsi_device *fsi, unsigned int reg, in fsi_i2c_write_reg() argument
183 return fsi_device_write(fsi, reg, &data_be, sizeof(data_be)); in fsi_i2c_write_reg()
193 rc = fsi_i2c_write_reg(i2c->fsi, I2C_FSI_INT_MASK, &interrupt); in fsi_i2c_dev_init()
198 rc = fsi_i2c_write_reg(i2c->fsi, I2C_FSI_MODE, &mode); in fsi_i2c_dev_init()
[all …]
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/include/sound/
H A Dsh_fsi.h1 /* SPDX-License-Identifier: GPL-2.0
3 * Fifo-attached Serial Interface (FSI) support for SH7724
19 #define SH_FSI_CLK_CPG (1 << 2) /* FSIxCK + FSI-DIV */
/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.
44 If your system has an master-capable SPI controller (which
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.
127 in the Aspeed AST2600, AST2500 and AST2400 SoCs when attached
155 supports spi-mem interface.
234 this code to manage the per-word or per-transfer accesses to the
[all …]
/linux/sound/soc/sh/
H A Dfsi.c1 // SPDX-License-Identifier: GPL-2.0
3 // Fifo-attached Serial Interface (FSI) support for SH7724
12 #include <linux/dma-mapping.h>
46 /* core register (depend on FSI version) */
151 * FSI driver use below type name for variable
165 * |<-------------------- period--------------------->|
168 * ||<----- frame ----->|<------ frame ----->| ... |
169 * |+--------------------+--------------------+- ... |
171 * |+--------------------+--------------------+- ... |
176 * FSI FIFO image
[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 …]