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

[Ayush Singh]

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.

---
V3:
- Rebase on char-misc-next
V2: https://lists.linaro.org/archives/list/greybus-dev@xxxxxxxxxxxxxxxx/thread/7YX5I6ZYZTNTAHBH3M3KAMOWXMTAWQNW/
- Add more comments explaining the new greybus hdlc frame payload
- Remove msg len warnings. These checks are also performed by
`greybus_data_rcvd` and thus no need for it here.

V1: https://lists.linaro.org/archives/list/greybus-dev@xxxxxxxxxxxxxxxx/thread/Y3ELHKLKTP5TQZ5LYKCE6GHWMA3PUOTV/


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

 drivers/greybus/gb-beagleplay.c | 58 ++++++++++++++++++++++++---------
 1 file changed, 43 insertions(+), 15 deletions(-)


base-commit: e909abe885e2f399be7ac0560a010d7429f951e1
-- 
2.43.0