Lines Matching +full:master +full:- +full:level
1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * FSI master definitions. These comprise the core <--> master interface,
4 * to allow the core to interact with the (hardware-specific) masters.
16 * Master registers
19 * the hub master in POWER processors.
31 #define FSI_MVER 0x74 /* R: master version/type */
34 #define FSI_MESRB0 0x1d0 /* R: Master error status */
36 #define FSI_MSCSB0 0x1d4 /* R: Master sub command stack */
37 #define FSI_MATRB0 0x1d8 /* R: Master address trace */
38 #define FSI_MDTRB0 0x1dc /* R: Master data trace */
61 #define FSI_MRESP_RST_MCR 0x08000000 /* Reset FSI master reg. */
67 /* master 0 in error */
77 * These are used by low level masters that bit-bang out the protocol
101 #define FSI_CMD_SAME_AR 0x3 /* but only a 2-bit opcode... */
107 #define FSI_RESP_ERRC 3 /* Slave reports master CRC error */
112 /* fsi-master definition and flags */
143 * fsi_master_unregister() functions will take ownership of the master, and
144 * ->dev in particular. The registration path performs a get_device(), which
148 * This means that master implementations *may* need to hold their own
149 * reference (via get_device()) on master->dev. In particular, if the device's
150 * ->release callback frees the fsi_master, then fsi_master_unregister will
154 * fails, dev->release will have been invoked.
156 extern int fsi_master_register(struct fsi_master *master);
157 extern void fsi_master_unregister(struct fsi_master *master);
159 extern int fsi_master_rescan(struct fsi_master *master);