[greybus-dev] [PATCH 0/1] Make gb-beagleplay driver Greybus compliant

In beagleplay beagleconnect setup, the AP is not directly connected to greybus nodes. The SVC and APBridge tasks are moved to cc1352 coprocessor. This means that there is a need to send cport information between linux host and cc1352.

In the initial version of the driver (and the reference implementation gbridge I was using), the greybus header pad bytes were being used. However, this was a violation of greybus spec.

The following patchset creates a wrapper around greybus message to send the cport information without using the pad bytes.

Ayush Singh (1): greybus: gb-beagleplay: Remove use of pad bytes

drivers/greybus/gb-beagleplay.c | 44 +++++++++++++++++++++++---------- 1 file changed, 31 insertions(+), 13 deletions(-)