Lines Matching +full:message +full:- +full:based

1 /* SPDX-License-Identifier: GPL-2.0 */
3  * Copyright (c) 2011-2017, The Linux Foundation
18 /* SLIMbus message types. Related to interpretation of message code. */
91  * struct slim_framer - Represents SLIMbus framer.
94  * Manager is responsible for framer hand-over.
111  * struct slim_msg_txn - Message to be sent by the controller.
115  * @mt: Header field. Message type.
116  * @mc: Header field. LSB is message code for type mt.
120  *	(relevant for message-codes involving read operation)
121  * @la: Logical address of the device this message is going to.
123  * @msg: Elemental access message to be read/written
125  *	for tid based transactions.
139 /* Frequently used message transaction structures */
173  *	scheduling, message bandwidth reservation) is done. Message APIs can
260  * struct slim_channel  - SLIMbus channel, used for state machine
279  * struct slim_port  - SLIMbus port
303  * @SLIM_PROTO_ASYNC_SMPLX: Asynchronous Protocol-Simplex
304  * @SLIM_PROTO_ASYNC_HALF_DUP: Asynchronous Protocol-Half-duplex
305  * @SLIM_PROTO_EXT_SMPLX: Extended Asynchronous Protocol-Simplex
306  * @SLIM_PROTO_EXT_HALF_DUP: Extended Asynchronous Protocol-Half-duplex
320  * struct slim_stream_runtime  - SLIMbus stream runtime instance
347  * struct slim_controller  - Controls every instance of SLIMbus
350  * @id: Board-specific number identifier for this controller/bus
362  * @xfer_msg: Transfer a message on this controller (this can be a broadcast
363  *	control/status message like data channel setup, or a unicast message
367  *	send unicast message to this device with its logical address.
372  * @wakeup: This function pointer implements controller-specific procedure
373  *	to wake it up from clock-pause. Framework will call this to bring
375  * @enable_stream: This function pointer implements controller-specific procedure
377  * @disable_stream: This function pointer implements controller-specific procedure
382  *	Device management means Logical address assignment/removal based on
383  *	enumeration (report-present, report-absent) of a device.
384  *	Bandwidth allocation is done dynamically by the manager based on active
385  *	channels on the bus, message-bandwidth requests made by SLIMbus devices.
386  *	Based on current bandwidth usage, manager chooses a frequency to run
387  *	the bus at (in steps of 'clock-gear', 1 through 10, each clock gear
389  *	Manager is also responsible for entering (and exiting) low-power-mode
393  *	previous framer being powered-on.
397  *	reporting information such as loss-of-synchronization, data
398  *	slot-collision.