linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Damien Riégel" <damien.riegel@silabs.com>
Cc: greybus-dev@lists.linaro.org, linux-kernel@vger.kernel.org,
	linux-devel@silabs.com, Alex Elder <elder@kernel.org>,
	Johan Hovold <johan@kernel.org>
Subject: Re: [RFC 2/6] greybus: cpc: add core logic
Date: Wed, 16 Jul 2025 15:21:08 +0200	[thread overview]
Message-ID: <2025071645-awkward-spotted-9d25@gregkh> (raw)
In-Reply-To: <20250705004036.3828-3-damien.riegel@silabs.com>

On Fri, Jul 04, 2025 at 08:40:32PM -0400, Damien Riégel wrote:
> This step adds the basic infrastructure in order to use CPC as backend
> in Greybus. The goal of CPC is to add reliablity, by implementing error
> detection and retransmission for links that don't have that capability
> by default.
> 
> When Greybus establishes the connection between two CPorts, CPC will
> create an endpoint for this connection. Greybus messages will then be
> encapsulated in CPC frames, which basically are a custom header +
> Greybus header + Greybus payload.
> 
> As this is still evolving and not the main point of the RFC, the whole
> core is squashed in one big commit, but it will definitely be split into
> more digestible commits as we refine it.
> 
> Signed-off-by: Damien Riégel <damien.riegel@silabs.com>
> ---
>  MAINTAINERS                    |   6 +
>  drivers/greybus/Kconfig        |   2 +
>  drivers/greybus/Makefile       |   2 +
>  drivers/greybus/cpc/Kconfig    |  12 ++
>  drivers/greybus/cpc/Makefile   |   6 +
>  drivers/greybus/cpc/cpc.h      | 135 ++++++++++++++++
>  drivers/greybus/cpc/endpoint.c | 158 +++++++++++++++++++
>  drivers/greybus/cpc/header.c   | 212 +++++++++++++++++++++++++
>  drivers/greybus/cpc/header.h   |  81 ++++++++++
>  drivers/greybus/cpc/host.c     | 113 ++++++++++++++
>  drivers/greybus/cpc/protocol.c | 274 +++++++++++++++++++++++++++++++++
>  11 files changed, 1001 insertions(+)

I like the idea, but you are going to have to break this up into smaller
pieces in order to get us to be able to review it well, sorry.

thanks

greg k-h

  reply	other threads:[~2025-07-16 13:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-05  0:40 [RFC 0/6] Introducing CPC support in Greybus Damien Riégel
2025-07-05  0:40 ` [RFC 1/6] greybus: move host controller drivers comment in Makefile Damien Riégel
2025-07-16 13:20   ` Greg Kroah-Hartman
2025-07-05  0:40 ` [RFC 2/6] greybus: cpc: add core logic Damien Riégel
2025-07-16 13:21   ` Greg Kroah-Hartman [this message]
2025-07-05  0:40 ` [RFC 3/6] greybus: cpc: add SPI driver Damien Riégel
2025-07-05  0:40 ` [RFC 4/6] greybus: add API for async unidirectional transfer Damien Riégel
2025-07-16 13:21   ` Greg Kroah-Hartman
2025-07-05  0:40 ` [RFC 5/6] greybus: match device with bundle ID Damien Riégel
2025-07-16 13:19   ` Greg Kroah-Hartman
2025-07-05  0:40 ` [RFC 6/6] greybus: add class driver for Silabs Bluetooth Damien Riégel
2025-07-16 13:23   ` Greg Kroah-Hartman

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=2025071645-awkward-spotted-9d25@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=damien.riegel@silabs.com \
    --cc=elder@kernel.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;
as well as URLs for NNTP newsgroup(s).