From: Tom Evans <tom_usenet@optusnet.com.au>
To: David Jander <david@protonic.nl>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 0/8] RFC: more flexcan cleanups and SW FIFO IRQ offloading
Date: Fri, 4 Sep 2015 13:19:22 +1000 [thread overview]
Message-ID: <55E90DBA.2000003@optusnet.com.au> (raw)
In-Reply-To: <20150903103827.5d08e957@archvile>
On 03/09/15 18:38, David Jander wrote:
> On Thu, 3 Sep 2015 18:17:53 +1000
> Tom Evans <tom_usenet@optusnet.com.au> wrote:
>
>> On 03/09/15 16:58, Marc Kleine-Budde wrote:
>>> On 09/03/2015 08:32 AM, David Jander wrote:
>>>>>> this series adds a software FIFO implementation and switches
>>
>> Thank you both for explaining that.
And the further explanations and background in the followup email.
Could some of this be added to a documentation file somewhere, or added as a
paragraph above the QUIRKS table? The existing code definitions and commments
may be sufficient for people who have been fighting these chips for years, but
not for someone relatively new to these chips.
>> In an old generation kernel this might be optionally enabled
>
> Why would you want to do that?
For when a new driver is released, and doesn't work for some users.
> It should be known to either work or not for specific hardware (-version),
It should, but sometimes something goes wrong and someone may need to easily
back out of a new feature to be able to use a new kernel version.
Tom
next prev parent reply other threads:[~2015-09-04 3:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 10:31 [PATCH 0/8] RFC: more flexcan cleanups and SW FIFO IRQ offloading Marc Kleine-Budde
2015-09-01 10:31 ` [PATCH 1/8] can: flexcan: add missing register definitions Marc Kleine-Budde
2015-09-01 10:31 ` [PATCH 2/8] can: flexcan: activate individual RX masking and initialize reg_rximr Marc Kleine-Budde
2015-09-01 10:31 ` [PATCH 3/8] can: flexcan: add quirk FLEXCAN_QUIRK_ENABLE_EACEN_RRS Marc Kleine-Budde
2015-09-01 10:31 ` [PATCH 4/8] can: flexcan: reg_imask2_default Marc Kleine-Budde
2015-09-01 10:31 ` [PATCH 5/8] can: rx-fifo: introduce software rx-fifo implementation Marc Kleine-Budde
2015-09-01 10:32 ` [PATCH 6/8] can: flexcan: add support for rx-fifo based software FIFO implementation Marc Kleine-Budde
2015-09-01 10:32 ` [PATCH 7/8] can: flexcan: switch imx6 and vf610 to software based fifo Marc Kleine-Budde
2015-09-01 10:32 ` [PATCH 8/8] can: at91_can: switch to rx-fifo implementation Marc Kleine-Budde
2015-09-02 23:58 ` [PATCH 0/8] RFC: more flexcan cleanups and SW FIFO IRQ offloading Tom Evans
2015-09-03 6:32 ` David Jander
2015-09-03 6:58 ` Marc Kleine-Budde
2015-09-03 8:17 ` Tom Evans
2015-09-03 8:38 ` David Jander
2015-09-03 8:47 ` Marc Kleine-Budde
2015-09-04 3:19 ` Tom Evans [this message]
2015-09-03 8:45 ` 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=55E90DBA.2000003@optusnet.com.au \
--to=tom_usenet@optusnet.com.au \
--cc=david@protonic.nl \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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).