From: Marc Kleine-Budde <mkl@pengutronix.de>
To: linux-can@vger.kernel.org
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Thomas Kopp <thomas.kopp@microchip.com>
Subject: [PATCH net-next 0/8] can: mcp251xfd: add support for multiple
Date: Thu, 17 Feb 2022 11:38:18 +0100 [thread overview]
Message-ID: <20220217103826.2299157-1-mkl@pengutronix.de> (raw)
Hello,
this patch series enables support for multiple RX-FIFOs and prepares
the driver for RX/TX IRQ coalescing support. I have a working IRQ
coalescing proof of concept series, but it needs cleanups und more
testing. I hope I can find some time to polish the remaining patches
and get them upstream in this merge window.
regards,
Marc
P.S.: The mcp251xfd-dump tool of can-utils does not yet support the
changed order of RX and TX FIFOs, I'm working on an update, too.
next reply other threads:[~2022-02-17 10:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 10:38 Marc Kleine-Budde [this message]
2022-02-17 10:38 ` [PATCH net-next 1/8] can: mcp251xfd: introduce struct mcp251xfd_tx_ring::nr and ::fifo_nr and make use of it Marc Kleine-Budde
2022-02-17 10:38 ` [PATCH net-next 2/8] can: mcp251xfd: mcp251xfd_ring_init(): split ring_init into separate functions Marc Kleine-Budde
2022-02-17 10:38 ` [PATCH net-next 3/8] can: mcp251xfd: ring: prepare to change order of TX and RX FIFOs Marc Kleine-Budde
2022-02-17 10:38 ` [PATCH net-next 4/8] can: mcp251xfd: ring: " Marc Kleine-Budde
2022-02-17 10:38 ` [PATCH net-next 5/8] can: mcp251xfd: ring: mcp251xfd_ring_init(): checked RAM usage of ring setup Marc Kleine-Budde
2022-02-17 10:38 ` [PATCH net-next 6/8] can: mcp251xfd: ring: update FIFO setup debug info Marc Kleine-Budde
2022-02-17 10:38 ` [PATCH net-next 7/8] can: mcp251xfd: prepare for multiple RX-FIFOs Marc Kleine-Budde
2022-02-17 10:38 ` [PATCH net-next 8/8] can: mcp251xfd: mcp251xfd_priv: introduce macros specifying the number of supported TEF/RX/TX rings Marc Kleine-Budde
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=20220217103826.2299157-1-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=thomas.kopp@microchip.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.