From: "Damien Riégel" <damien.riegel@silabs.com>
To: "Damien Riégel" <damien.riegel@silabs.com>,
greybus-dev@lists.linaro.org, "Johan Hovold" <johan@kernel.org>,
"Alex Elder" <elder@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: "Silicon Labs Kernel Team" <linux-devel@silabs.com>
Subject: Re: [RFC PATCH v2 00/12] greybus: introduce CPC as transport layer
Date: Tue, 25 Nov 2025 10:26:36 -0500 [thread overview]
Message-ID: <DEHVQ7YAUOG8.2TPWJBM6MTXLT@silabs.com> (raw)
In-Reply-To: <20251114150738.32426-1-damien.riegel@silabs.com>
Hi Greg, Johan, and Alex,
On Fri Nov 14, 2025 at 10:07 AM EST, Damien Riégel wrote:
> 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.
Gentle poke about this RFC, I would really appreciate any kind of
feedback on it.
If it's too big I can try to make it smaller to make the review easier.
As we're committing to Greybus to enable the coexistence of different
radio stacks in one chip, we want to make sure we're heading in the
right direction and that our work has a chance to get upstreamed.
Thank you!
--
Damien
next prev parent reply other threads:[~2025-11-25 15:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 15:07 Damien Riégel
2025-11-14 15:07 ` [RFC PATCH v2 01/12] greybus: cpc: add minimal CPC Host Device infrastructure Damien Riégel
2025-11-14 16:44 ` Yacin Belmihoub-Martel
2025-11-14 16:51 ` Yacin Belmihoub-Martel
2025-11-14 16:55 ` Yacin Belmihoub-Martel
2025-11-14 15:07 ` [RFC PATCH v2 02/12] greybus: cpc: introduce CPC cport structure Damien Riégel
2025-11-14 15:07 ` [RFC PATCH v2 03/12] greybus: cpc: use socket buffers instead of gb_message in TX path Damien Riégel
2025-11-14 15:07 ` [RFC PATCH v2 04/12] greybus: cpc: pack cport ID in Greybus header Damien Riégel
2025-11-14 15:07 ` [RFC PATCH v2 05/12] greybus: cpc: switch RX path to socket buffers Damien Riégel
2025-11-14 15:07 ` [RFC PATCH v2 06/12] greybus: cpc: introduce CPC header structure Damien Riégel
2025-11-14 15:07 ` [RFC PATCH v2 07/12] greybus: cpc: account for CPC header size in RX and TX path Damien Riégel
2025-11-14 15:07 ` [RFC PATCH v2 08/12] greybus: cpc: add and validate sequence numbers Damien Riégel
2025-11-14 15:07 ` [RFC PATCH v2 09/12] greybus: cpc: acknowledge all incoming messages Damien Riégel
2025-11-14 15:07 ` [RFC PATCH v2 10/12] greybus: cpc: use holding queue instead of sending out immediately Damien Riégel
2025-11-14 19:53 ` Yacin Belmihoub-Martel
2025-11-14 15:07 ` [RFC PATCH v2 11/12] greybus: cpc: honour remote's RX window Damien Riégel
2025-11-14 20:28 ` Yacin Belmihoub-Martel
2025-11-14 15:07 ` [RFC PATCH v2 12/12] greybus: cpc: let host device drivers dequeue TX frames Damien Riégel
2025-11-25 15:26 ` Damien Riégel [this message]
2025-11-26 12:33 ` [RFC PATCH v2 00/12] greybus: introduce CPC as transport layer Greg Kroah-Hartman
2025-12-01 15:39 ` Damien Riégel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DEHVQ7YAUOG8.2TPWJBM6MTXLT@silabs.com \
--to=damien.riegel@silabs.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-devel@silabs.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®