iv/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

greybus: Define cport/bundle for SVC protocol

Browse Source 
For now, the plan is to use a single cport for both control and svc
protocol. Defining separate macros for control and svc protocol's
cport/bundle would make the code more flexible, in case we need two
separate cports in future.

Lets define cport/bundle for svc protocol as well.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
This commit is contained in:
Viresh Kumar 2015-07-21 17:44:13 +05:30 committed by Greg Kroah-Hartman
parent c8dd60db6c
commit ec320625be
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
drivers/staging/greybus/greybus_protocols.h
View File

@ -59,11 +59,19 @@
#define GB_DEVICE_ID_AP 1
#define GB_DEVICE_ID_MODULES_START 2
/* Bundle-id and cport-id for control cport */
/*
* Bundle/cport for control/svc cport: The same bundle/cport is shared by both
* CONTROL and SVC protocols for communication between AP and SVC.
*/
#define GB_SVC_BUNDLE_ID 0
#define GB_SVC_CPORT_ID 2
#define GB_CONTROL_BUNDLE_ID 0
#define GB_CONTROL_CPORT_ID 2
/* Control Protocol */
/* version request has no payload */
struct gb_protocol_version_response {
__u8 major;