From ec320625be76641c9f4d594335330a5544716304 Mon Sep 17 00:00:00 2001 From: Viresh Kumar Date: Tue, 21 Jul 2015 17:44:13 +0530 Subject: [PATCH] greybus: Define cport/bundle for SVC protocol 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 Signed-off-by: Greg Kroah-Hartman --- drivers/staging/greybus/greybus_protocols.h | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/drivers/staging/greybus/greybus_protocols.h b/drivers/staging/greybus/greybus_protocols.h index 0056c2a30f22..44957bd8955b 100644 --- a/drivers/staging/greybus/greybus_protocols.h +++ b/drivers/staging/greybus/greybus_protocols.h @@ -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; -- 2.11.0