From: Robert Schwebel <r.schwebel@pengutronix.de> To: Sharma Bhupesh <bhupesh.sharma@freescale.com> Cc: Marc Kleine-Budde <mkl@pengutronix.de>, "arnd@arndb.de" <arnd@arndb.de>, "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>, "bhupesh.linux@gmail.com" <bhupesh.linux@gmail.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, Arora Sakar <Sakar.Arora@freescale.com> Subject: Re: [PATCH v2 5/5] can: flexcan: Add support for non RX-FIFO mode Date: Fri, 11 Dec 2015 17:01:04 +0100 [thread overview] Message-ID: <20151211160104.GU30206@pengutronix.de> (raw) In-Reply-To: <BY1PR0301MB1303A87AF2B3FFBB6CDA90EE82E90@BY1PR0301MB1303.namprd03.prod.outlook.com> On Thu, Dec 10, 2015 at 12:22:55PM +0000, Sharma Bhupesh wrote: > > If we have to rely on the timestamps the next logical step is to add > > sorting by timestamp to the rx-fifo implementation. I'll send a > > patch series of the current state. > > With my current v3, I see no rx-frame ordering issues atleast on > LS1021A. Marc can post our testcases here on the list (maybe with the description from the service request); perhaps this can clarify the issues. > I can ask internally about more details on the "SR# 1-4074792564 : CAN > Ordering Issues". That would be quite helpful, thanks! Understanding the root cause of the issue is often a good start, maybe there is an option for a software workaround. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
WARNING: multiple messages have this Message-ID (diff)
From: r.schwebel@pengutronix.de (Robert Schwebel) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 5/5] can: flexcan: Add support for non RX-FIFO mode Date: Fri, 11 Dec 2015 17:01:04 +0100 [thread overview] Message-ID: <20151211160104.GU30206@pengutronix.de> (raw) In-Reply-To: <BY1PR0301MB1303A87AF2B3FFBB6CDA90EE82E90@BY1PR0301MB1303.namprd03.prod.outlook.com> On Thu, Dec 10, 2015 at 12:22:55PM +0000, Sharma Bhupesh wrote: > > If we have to rely on the timestamps the next logical step is to add > > sorting by timestamp to the rx-fifo implementation. I'll send a > > patch series of the current state. > > With my current v3, I see no rx-frame ordering issues atleast on > LS1021A. Marc can post our testcases here on the list (maybe with the description from the service request); perhaps this can clarify the issues. > I can ask internally about more details on the "SR# 1-4074792564 : CAN > Ordering Issues". That would be quite helpful, thanks! Understanding the root cause of the issue is often a good start, maybe there is an option for a software workaround. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2015-12-11 16:01 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-14 11:33 [PATCH v2 0/5] Add flexcan support for LS1021A SoCs Bhupesh Sharma 2015-05-14 11:33 ` Bhupesh Sharma 2015-05-14 11:33 ` [PATCH v2 1/5] doc/bindings: Add 'endianess' optional-property for FlexCAN controller Bhupesh Sharma 2015-05-14 11:33 ` Bhupesh Sharma 2015-05-14 11:33 ` [PATCH v2 2/5] arm/dts: Add nodes for flexcan devices present on LS1021A SoC Bhupesh Sharma 2015-05-14 11:33 ` Bhupesh Sharma 2015-05-14 11:33 ` [PATCH v2 3/5] can: flexcan: Add ls1021a flexcan device entry Bhupesh Sharma 2015-05-14 11:33 ` Bhupesh Sharma 2015-05-14 15:38 ` Marc Kleine-Budde 2015-05-14 15:38 ` Marc Kleine-Budde 2015-05-14 11:33 ` [PATCH v2 4/5] can: flexcan: Remodel FlexCAN register r/w APIs for BE instances Bhupesh Sharma 2015-05-14 11:33 ` Bhupesh Sharma 2015-05-18 16:17 ` Enrico Weigelt, metux IT consult 2015-05-18 16:17 ` Enrico Weigelt, metux IT consult 2015-05-18 16:37 ` Sharma Bhupesh 2015-05-18 16:37 ` Sharma Bhupesh 2015-05-14 11:33 ` [PATCH v2 5/5] can: flexcan: Add support for non RX-FIFO mode Bhupesh Sharma 2015-05-14 11:33 ` Bhupesh Sharma 2015-05-14 15:41 ` Marc Kleine-Budde 2015-05-14 15:41 ` Marc Kleine-Budde 2015-05-14 15:44 ` Sharma Bhupesh 2015-05-14 15:44 ` Sharma Bhupesh 2015-12-10 11:05 ` Sharma Bhupesh 2015-12-10 11:05 ` Sharma Bhupesh 2015-12-10 11:44 ` can: flexcan: Ancient Freescale Reference FlexCAN Driver and bug fixes so it works Tom Evans 2015-12-10 12:44 ` Marc Kleine-Budde 2015-12-10 12:44 ` Marc Kleine-Budde 2015-12-10 22:53 ` Tom Evans 2015-12-10 22:53 ` Tom Evans 2015-12-17 4:22 ` Tom Evans 2015-12-17 4:22 ` Tom Evans 2015-12-23 0:53 ` Tom Evans 2015-12-23 0:53 ` Tom Evans 2015-12-10 12:19 ` [PATCH v2 5/5] can: flexcan: Add support for non RX-FIFO mode Marc Kleine-Budde 2015-12-10 12:19 ` Marc Kleine-Budde 2015-12-10 12:22 ` Sharma Bhupesh 2015-12-10 12:22 ` Sharma Bhupesh 2015-12-11 16:01 ` Robert Schwebel [this message] 2015-12-11 16:01 ` Robert Schwebel 2015-05-15 0:09 ` Tom Evans 2015-05-15 0:09 ` Tom Evans
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=20151211160104.GU30206@pengutronix.de \ --to=r.schwebel@pengutronix.de \ --cc=Sakar.Arora@freescale.com \ --cc=arnd@arndb.de \ --cc=bhupesh.linux@gmail.com \ --cc=bhupesh.sharma@freescale.com \ --cc=linux-arm-kernel@lists.infradead.org \ --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: linkBe 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.