linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org, Thomas Kopp <thomas.kopp@microchip.com>
Subject: Re: [net-next 0/3] tef-path: reduce number of SPI core requests to set UINC bit
Date: Wed, 25 Nov 2020 20:41:11 +0530	[thread overview]
Message-ID: <20201125151111.GC20836@thinkpad> (raw)
In-Reply-To: <20201125145221.22241-1-mkl@pengutronix.de>

Hi Marc,

Unrelated to this change, is it you or anyone working on internal
loopback support for this driver? If not, then I'll just pick up.

Thanks,
Mani

On Wed, Nov 25, 2020 at 03:52:19PM +0100, Marc Kleine-Budde wrote:
> 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
> 

  parent reply	other threads:[~2020-11-25 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 14:52 [net-next 0/3] tef-path: reduce number of SPI core requests to set UINC bit Marc Kleine-Budde
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 ` Manivannan Sadhasivam [this message]
2020-11-25 15:17   ` [net-next 0/3] " 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=20201125151111.GC20836@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --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).