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 <viresh.kumar@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>

diff --git a/drivers/staging/greybus/greybus_protocols.h b/drivers/staging/greybus/greybus_protocols.h
index 0056c2a30f22ae33f0d0ba8502e28ee1097cd681..44957bd8955b1c4be6cc7e96f780ca62881d76b2 100644 (file)
--- 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;