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: [net-next 0/3] tef-path: reduce number of SPI core requests to set UINC bit
Date: Wed, 25 Nov 2020 15:52:19 +0100 [thread overview]
Message-ID: <20201125145221.22241-1-mkl@pengutronix.de> (raw)
Hello,
as Thomas wants to test the rx-path improvements, here is the same idea for the
TEF-path.
This is a short series to reduce the number SPI core requests to increment the
UINC bit after TEF handling. This is done by chaining the individual UINC bit
changes into a single SPI message consisting of several transfers.
I'll add proper commit messages to patch 1 and 2 later.
Happy testing,
Marc
next reply other threads:[~2020-11-25 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 14:52 Marc Kleine-Budde [this message]
2020-11-25 14:52 ` [net-next 1/3] can: mcp251xfd: convert tef_ring Marc Kleine-Budde
2020-11-25 14:52 ` [net-next 2/3] can: mcp251xfd: move mcp251xfd_tef_ring definition Marc Kleine-Budde
2020-11-25 14:52 ` [net-next 3/3] can: mcp251xfd: tef-path: reduce number of SPI core requests to set UINC bit Marc Kleine-Budde
2020-11-25 15:11 ` [net-next 0/3] " Manivannan Sadhasivam
2020-11-25 15:17 ` Marc Kleine-Budde
2020-11-26 12:48 ` Thomas.Kopp
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=20201125145221.22241-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 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).