1
0
Fork 0

staging: vchi: Get rid of all useless callback reasons

They are neither produced nor expected, so just delete them.

Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Link: https://lore.kernel.org/r/20200629150945.10720-10-nsaenzjulienne@suse.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
zero-sugar-mainline-defconfig
Nicolas Saenz Julienne 2020-06-29 17:09:07 +02:00 committed by Greg Kroah-Hartman
parent 5d9272e28a
commit af22fd658a
1 changed files with 4 additions and 38 deletions

View File

@ -31,8 +31,6 @@ enum vchi_crc_control {
//callback reasons when an event occurs on a service
enum vchi_callback_reason {
VCHI_CALLBACK_REASON_MIN,
/*
* This indicates that there is data available handle is the msg id that
* was transmitted with the data
@ -41,44 +39,12 @@ enum vchi_callback_reason {
* Tasks get kicked by the callback, reset their event and try and read
* from the fifo until it fails
*/
VCHI_CALLBACK_MSG_AVAILABLE,
VCHI_CALLBACK_MSG_SENT,
VCHI_CALLBACK_MSG_SPACE_AVAILABLE, // XXX not yet implemented
// This indicates that a transfer from the other side has completed
VCHI_CALLBACK_BULK_RECEIVED,
//This indicates that data queued up to be sent has now gone
//handle is the msg id that was used when sending the data
VCHI_CALLBACK_BULK_SENT,
VCHI_CALLBACK_BULK_RX_SPACE_AVAILABLE, // XXX not yet implemented
VCHI_CALLBACK_BULK_TX_SPACE_AVAILABLE, // XXX not yet implemented
VCHI_CALLBACK_SERVICE_CLOSED,
/*
* this side has sent XOFF to peer due to lack of data consumption by
* service (suggests the service may need to take some recovery action
* if it has been deliberately holding off consuming data)
*/
VCHI_CALLBACK_SENT_XOFF,
VCHI_CALLBACK_SENT_XON,
// indicates that a bulk transfer has finished reading the source buffer
VCHI_CALLBACK_BULK_DATA_READ,
// power notification events (currently host side only)
VCHI_CALLBACK_PEER_OFF,
VCHI_CALLBACK_PEER_SUSPENDED,
VCHI_CALLBACK_PEER_ON,
VCHI_CALLBACK_PEER_RESUMED,
VCHI_CALLBACK_FORCED_POWER_OFF,
// some extra notifications provided by vchiq_arm
VCHI_CALLBACK_SERVICE_OPENED,
VCHI_CALLBACK_BULK_RECEIVE_ABORTED,
VCHI_CALLBACK_MSG_AVAILABLE,
VCHI_CALLBACK_BULK_SENT,
VCHI_CALLBACK_BULK_RECEIVED,
VCHI_CALLBACK_BULK_TRANSMIT_ABORTED,
VCHI_CALLBACK_REASON_MAX
VCHI_CALLBACK_BULK_RECEIVE_ABORTED,
};
// service control options