From: "Damien Riégel" <damien.riegel@silabs.com>
To: "Damien Riégel" <damien.riegel@silabs.com>,
"Jérôme Pouiller" <jerome.pouiller@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>,
"Gabriel Beaulieu" <gabriel.beaulieu@silabs.com>
Subject: Re: [PATCH v3 14/14] greybus: cpc: add CPC SDIO host driver
Date: Thu, 19 Feb 2026 09:38:36 -0500 [thread overview]
Message-ID: <DGJ0KBIEA248.1JH2YZU2MCUPY@silabs.com> (raw)
In-Reply-To: <DGDYJQU8IRVK.1WJLTV18VUFQQ@silabs.com>
On Fri Feb 13, 2026 at 11:00 AM EST, Damien Riégel wrote:
> On Fri Feb 13, 2026 at 4:35 AM EST, Jérôme Pouiller wrote:
>> In any case, I believe we can't publish a driver with VID = 0.
>
> Noted, the patchset can't be applied as is. I'll check what the process
> is to assign a VID/PID.
I'm still trying to figure out internally how I can get a VID/PID for
this driver. We thought we had a valid vendor ID we could use, based on
a JEDEC ID that we already have assigned, but upon further investigation
I don't think we have the right to derive an SDIO VID from that JEDEC
ID, so the whole process might take a bit of time.
In the meantime, may I suggest that we continue the review as if a valid
VID/PID was assigned? You can keep your "Reviewed-by" until we actually
have valid IDs. If we have to get in touch with external organizations,
it might take a few weeks or even months to get sorted, I have no idea
how long that process will be.
Alternatively, I could just drop the SDIO VID/PID and just rely on device
tree instead? That leaves the question of what the compatible string
should be. Rob Herring doesn't want a generic "silabs,greybus" string,
it must be a real product and we don't have that yet.
I'd be happy to take any input that helps make progress :)
thanks,
damien
prev parent reply other threads:[~2026-02-19 14:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 14:43 [PATCH v3 00/14] greybus: introduce CPC as transport layer Damien Riégel
2026-02-12 14:43 ` [PATCH v3 01/14] greybus: cpc: add minimal CPC Host Device infrastructure Damien Riégel
2026-02-12 14:43 ` [PATCH v3 02/14] greybus: cpc: introduce CPC cport structure Damien Riégel
2026-02-12 14:43 ` [PATCH v3 03/14] greybus: cpc: use socket buffers instead of gb_message in TX path Damien Riégel
2026-02-12 14:43 ` [PATCH v3 04/14] greybus: cpc: pack cport ID in Greybus header Damien Riégel
2026-02-12 14:43 ` [PATCH v3 05/14] greybus: cpc: switch RX path to socket buffers Damien Riégel
2026-02-12 14:43 ` [PATCH v3 06/14] greybus: cpc: introduce CPC header structure Damien Riégel
2026-02-12 14:43 ` [PATCH v3 07/14] greybus: cpc: account for CPC header size in RX and TX path Damien Riégel
2026-02-12 14:43 ` [PATCH v3 08/14] greybus: cpc: add and validate sequence numbers Damien Riégel
2026-02-12 14:43 ` [PATCH v3 09/14] greybus: cpc: acknowledge all incoming messages Damien Riégel
2026-02-12 14:43 ` [PATCH v3 10/14] greybus: cpc: use holding queue instead of sending out immediately Damien Riégel
2026-02-13 6:44 ` kernel test robot
2026-02-12 14:43 ` [PATCH v3 11/14] greybus: cpc: honour remote's RX window Damien Riégel
2026-02-13 21:56 ` kernel test robot
2026-02-12 14:43 ` [PATCH v3 12/14] greybus: cpc: let host device drivers dequeue TX frames Damien Riégel
2026-02-12 14:43 ` [PATCH v3 13/14] greybus: cpc: add private data pointer in CPC Host Device Damien Riégel
2026-02-12 14:43 ` [PATCH v3 14/14] greybus: cpc: add CPC SDIO host driver Damien Riégel
2026-02-13 0:31 ` kernel test robot
2026-02-13 9:35 ` Jérôme Pouiller
2026-02-13 16:00 ` Damien Riégel
2026-02-19 14:38 ` Damien Riégel [this message]
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=DGJ0KBIEA248.1JH2YZU2MCUPY@silabs.com \
--to=damien.riegel@silabs.com \
--cc=elder@kernel.org \
--cc=gabriel.beaulieu@silabs.com \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=jerome.pouiller@silabs.com \
--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®