[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231217121133.74703-1-ayushdevel1325@gmail.com>
Date: Sun, 17 Dec 2023 17:41:31 +0530
From: Ayush Singh <ayushdevel1325@...il.com>
To: greybus-dev@...ts.linaro.org
Cc: Ayush Singh <ayushdevel1325@...il.com>,
johan@...nel.org,
elder@...nel.org,
gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org,
jkridner@...gleboard.org,
nm@...com
Subject: [PATCH V3 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.
---
V3:
- Rebase on char-misc-next
V2: https://lists.linaro.org/archives/list/greybus-dev@lists.linaro.org/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@lists.linaro.org/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
Powered by blists - more mailing lists