Hi Greg and all,
This series performs a set of cleanups, correctness fixes, and
remaining TODO removals across the Greybus drivers in
drivers/staging/greybus.
Greybus has existed in staging for a long time, and many FIXMEs,
outdated comments, and partial implementations had accumulated over the
years. While reviewing and compile-testing the drivers I found a number of
places where the comments were obsolete, logic was incomplete, or newer
subsystem APIs had evolved.
This series addresses those issues without changing any fundamental
design or architecture. All changes are self-contained, straightforward,
and focues on improving correctness and maintainability.
The patches include:
* Removal of obsolete FIXMEs that no longer reflect the current code
or hardware behavior.
* Correctness fixes in several protocol drivers (UART, RAW, USB,
Loopback, Firmware core, Audio).
* Small improvements to error handling and shutdown paths.
* Cleanup of commented-out or dead code.
* Removal of the now-completed GPIO and PWM TODO items.
* Removal of the empty Greybus TODO file.
All patches were compile-tested with COMPILE_TEST=y and all Greybus
options enabled. Runtime smoke testing was performed where possible.
This series does not attempt to graduate Greybus out of staging; these
changes are preparatory cleanups only.
Thanks for your time and review.
Ayaan Mirza Baig (13):
staging: greybus: Remove completed GPIO conversion TODO item
staging: greybus: pwm: move activation into pwm apply and remove
request()
staging: greybus: remove empty TODO file
staging: greybus: audio: remove obsolete INPUT_PROP_NO_DUMMY_RELEASE
FIXME
staging: greybus: audio: remove obsolete FIXME and document topology
ownership
staging: greybus: bootrom: remove obsolete FIXME about SVC parallel
event handling
staging: greybus: bootrom: remove obsolete FIXME around firmware
filename logging
staging: greybus: fw-core: remove obsolete S2 Loader runtime PM FIXME
staging: greybus: loopback: remove incorrect FIXME about async wait
staging: greybus: raw: handle disconnect while chardev is open
staging: greybus: uart: clear unsupported termios bits
staging: greybus: usb: validate hub control response length
staging: greybus: usb: remove obsolete FIXME about bridged-PHY support
drivers/staging/greybus/TODO | 5 -----
drivers/staging/greybus/audio_codec.c | 7 +------
drivers/staging/greybus/audio_module.c | 6 ++++--
drivers/staging/greybus/bootrom.c | 10 ++--------
drivers/staging/greybus/fw-core.c | 4 ++--
drivers/staging/greybus/loopback.c | 6 +-----
drivers/staging/greybus/pwm.c | 19 +++++++++++--------
drivers/staging/greybus/raw.c | 18 ++++++++++++++++--
drivers/staging/greybus/uart.c | 10 ++++++++--
drivers/staging/greybus/usb.c | 23 ++++++++---------------
10 files changed, 53 insertions(+), 55 deletions(-)
delete mode 100644 drivers/staging/greybus/TODO
--
2.51.0
Check the return values of send_control() and send_line_coding() during
device initialization in gb_uart_probe(). If these operations fail, the
device will be left in an inconsistent state, so propagate the error to
properly fail the probe.
Both functions call gb_operation_sync() which can fail with errors such
as -ENOMEM, -ENODEV, or -ETIMEDOUT. Ignoring these errors means the TTY
device would be registered despite incomplete initialization.
Signed-off-by: Nirbhay Sharma <nirbhay.lkd(a)gmail.com>
---
drivers/staging/greybus/uart.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/greybus/uart.c b/drivers/staging/greybus/uart.c
index 10df5c37c83e..5cece0a6606f 100644
--- a/drivers/staging/greybus/uart.c
+++ b/drivers/staging/greybus/uart.c
@@ -879,14 +879,18 @@ static int gb_uart_probe(struct gbphy_device *gbphy_dev,
if (retval)
goto exit_put_port;
- send_control(gb_tty, gb_tty->ctrlout);
+ retval = send_control(gb_tty, gb_tty->ctrlout);
+ if (retval)
+ goto exit_connection_disable;
/* initialize the uart to be 9600n81 */
gb_tty->line_coding.rate = cpu_to_le32(9600);
gb_tty->line_coding.format = GB_SERIAL_1_STOP_BITS;
gb_tty->line_coding.parity = GB_SERIAL_NO_PARITY;
gb_tty->line_coding.data_bits = 8;
- send_line_coding(gb_tty);
+ retval = send_line_coding(gb_tty);
+ if (retval)
+ goto exit_connection_disable;
retval = gb_connection_enable(connection);
if (retval)
--
2.48.1
Hi,
This patchset brings support for Silicon Labs' CPC (Co-Processor
Communication) protocol as transport layer for Greybus. This is
introduced as a module that sits between Greybus and CPC Host Device
Driver implementations, like SDIO or SPI, which are not part of this
RFC. If there's no push back with this RFC, the final patchset ready for
upstream will include the SDIO driver.
The goal of this module is to implement some of the features of Unipro
that Greybus relies upon, like reliable transmission. CPC takes care of
detecting transmission errors and retransmit frames if necessary. That
feature is not part of the RFC to keep it concise, but it's planned for
a future patchset. There's also a flow-control feature, to prevent from
sending messages to cports that don't have anymore room.
In order to implement these features, a 4-byte header is prepended to
Greybus messages, making the whole header 12 bytes (Greybus header
itself being 8 bytes).
This RFC starts by implementing a shim layer that sits between physical
bus drivers (like SDIO and SPI) and Greybus, and progressively add more
elements to it to make it useful in its own right.
+----------------------------------------------------+
| Greybus |
+----------------------------------------------------+
/|\
|
\|/
+----------------------------------------------------+
| CPC |
+----------------------------------------------------+
/|\ /|\ /|\
| | |
\|/ \|/ \|/
+----------+ +---------+ +-----------+
| SDIO | | SPI | | Others |
+----------+ +---------+ +-----------+
Changes in v2:
- v1 included a new protocol for Bluetooth HCI, this has been dropped
to focus on CPC itself
- likewise, there was an SPI driver, it has been dropped of this RFC
for the same reason
- v1 introduced CPC in a big commit, this time it's been split in
smaller commits to make review manageable
Damien Riégel (12):
greybus: cpc: add minimal CPC Host Device infrastructure
greybus: cpc: introduce CPC cport structure
greybus: cpc: use socket buffers instead of gb_message in TX path
greybus: cpc: pack cport ID in Greybus header
greybus: cpc: switch RX path to socket buffers
greybus: cpc: introduce CPC header structure
greybus: cpc: account for CPC header size in RX and TX path
greybus: cpc: add and validate sequence numbers
greybus: cpc: acknowledge all incoming messages
greybus: cpc: use holding queue instead of sending out immediately
greybus: cpc: honour remote's RX window
greybus: cpc: let host device drivers dequeue TX frames
MAINTAINERS | 6 +
drivers/greybus/Kconfig | 2 +
drivers/greybus/Makefile | 2 +
drivers/greybus/cpc/Kconfig | 10 ++
drivers/greybus/cpc/Makefile | 6 +
drivers/greybus/cpc/cpc.h | 76 +++++++++
drivers/greybus/cpc/cport.c | 107 ++++++++++++
drivers/greybus/cpc/header.c | 146 +++++++++++++++++
drivers/greybus/cpc/header.h | 54 +++++++
drivers/greybus/cpc/host.c | 287 +++++++++++++++++++++++++++++++++
drivers/greybus/cpc/host.h | 58 +++++++
drivers/greybus/cpc/protocol.c | 169 +++++++++++++++++++
12 files changed, 923 insertions(+)
create mode 100644 drivers/greybus/cpc/Kconfig
create mode 100644 drivers/greybus/cpc/Makefile
create mode 100644 drivers/greybus/cpc/cpc.h
create mode 100644 drivers/greybus/cpc/cport.c
create mode 100644 drivers/greybus/cpc/header.c
create mode 100644 drivers/greybus/cpc/header.h
create mode 100644 drivers/greybus/cpc/host.c
create mode 100644 drivers/greybus/cpc/host.h
create mode 100644 drivers/greybus/cpc/protocol.c
--
2.49.0