All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sharma Bhupesh <bhupesh.sharma@freescale.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Cc: "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: Thu, 10 Dec 2015 12:22:55 +0000	[thread overview]
Message-ID: <BY1PR0301MB1303A87AF2B3FFBB6CDA90EE82E90@BY1PR0301MB1303.namprd03.prod.outlook.com> (raw)
In-Reply-To: <56696DC8.8020708@pengutronix.de>

> -----Original Message-----
> From: Marc Kleine-Budde [mailto:mkl@pengutronix.de]
> Sent: Thursday, December 10, 2015 5:49 PM
> 
> On 12/10/2015 12:05 PM, Sharma Bhupesh wrote:
> >>> -----Original Message-----
> >>> From: Marc Kleine-Budde [mailto:mkl@pengutronix.de]
> >>> Sent: Thursday, May 14, 2015 9:12 PM
> >>> To: Sharma Bhupesh-B45370; arnd@arndb.de; linux-can@vger.kernel.org
> >>> Cc: bhupesh.linux@gmail.com; Arora Sakar-B45205; linux-arm-
> >>> kernel@lists.infradead.org
> >>> Subject: Re: [PATCH v2 5/5] can: flexcan: Add support for non
> >>> RX-FIFO mode
> >>>
> >>> On 05/14/2015 01:33 PM, Bhupesh Sharma wrote:
> >>>> This patch adds support for non RX-FIFO (legacy) mode in the
> >>>> flexcan driver.
> >>>>
> >>>> On certain SoCs, the RX-FIFO support might be broken, as a result
> >>>> we need to fall-back on the legacy (non RX-FIFO) mode to receive
> >>>> CAN frames.
> >>>>
> >>>> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@freescale.com>
> >>>> Signed-off-by: Sakar Arora <Sakar.Arora@freescale.com>
> >>>
> >>> The non FIFO mode doesn't guarantee the order of the incoming
> >>> frames, not does not even try to...this is not acceptable. I'm
> >>> currently working on a patch by David Jander that brings in non FIFO
> >>> mode, but tries to keep the order of the frames.
> >>
> >> That is already WIP at our end. V3 will contain the same change.
> >> If you are already working on it, I don't know how to proceed further
> >> as we had already v1 of this patchset with the non FIFO mode out
> >> since a month or so.
> >
> > I don't remember seeing a patch from you which supports non-FIFO mode
> for flexcan IP.
> > Since we now have Freescale LS1021A chip out in the field on which the
> > FIFO mode broken, we cannot use the upstream flexcan driver for
> enabling flexcan IP on these chips.
> >
> > Do you still have plans to work on this? Or should I submit my v3 with
> > in-order reception supported for rx frames.
> 
> The problem is, that the current code triggers a ordering issue (at least
> on the imx6) in non FIFO mode. The frames are not received as the
> documentation states. If you have access, take a look at "SR#
> 1-4074792564 : CAN Ordering Issues". It seems the freescale support
> doesn't have much interest in confirming the issue, nor bringing us in
> touch with the people who have access to the IP core source to see what's
> going on.
> 
> 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.

I can ask internally about more details on the "SR# 1-4074792564 : CAN Ordering Issues".

Regards,
Bhupesh

WARNING: multiple messages have this Message-ID (diff)
From: bhupesh.sharma@freescale.com (Sharma Bhupesh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 5/5] can: flexcan: Add support for non RX-FIFO mode
Date: Thu, 10 Dec 2015 12:22:55 +0000	[thread overview]
Message-ID: <BY1PR0301MB1303A87AF2B3FFBB6CDA90EE82E90@BY1PR0301MB1303.namprd03.prod.outlook.com> (raw)
In-Reply-To: <56696DC8.8020708@pengutronix.de>

> -----Original Message-----
> From: Marc Kleine-Budde [mailto:mkl at pengutronix.de]
> Sent: Thursday, December 10, 2015 5:49 PM
> 
> On 12/10/2015 12:05 PM, Sharma Bhupesh wrote:
> >>> -----Original Message-----
> >>> From: Marc Kleine-Budde [mailto:mkl at pengutronix.de]
> >>> Sent: Thursday, May 14, 2015 9:12 PM
> >>> To: Sharma Bhupesh-B45370; arnd at arndb.de; linux-can at vger.kernel.org
> >>> Cc: bhupesh.linux at gmail.com; Arora Sakar-B45205; linux-arm-
> >>> kernel at lists.infradead.org
> >>> Subject: Re: [PATCH v2 5/5] can: flexcan: Add support for non
> >>> RX-FIFO mode
> >>>
> >>> On 05/14/2015 01:33 PM, Bhupesh Sharma wrote:
> >>>> This patch adds support for non RX-FIFO (legacy) mode in the
> >>>> flexcan driver.
> >>>>
> >>>> On certain SoCs, the RX-FIFO support might be broken, as a result
> >>>> we need to fall-back on the legacy (non RX-FIFO) mode to receive
> >>>> CAN frames.
> >>>>
> >>>> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@freescale.com>
> >>>> Signed-off-by: Sakar Arora <Sakar.Arora@freescale.com>
> >>>
> >>> The non FIFO mode doesn't guarantee the order of the incoming
> >>> frames, not does not even try to...this is not acceptable. I'm
> >>> currently working on a patch by David Jander that brings in non FIFO
> >>> mode, but tries to keep the order of the frames.
> >>
> >> That is already WIP at our end. V3 will contain the same change.
> >> If you are already working on it, I don't know how to proceed further
> >> as we had already v1 of this patchset with the non FIFO mode out
> >> since a month or so.
> >
> > I don't remember seeing a patch from you which supports non-FIFO mode
> for flexcan IP.
> > Since we now have Freescale LS1021A chip out in the field on which the
> > FIFO mode broken, we cannot use the upstream flexcan driver for
> enabling flexcan IP on these chips.
> >
> > Do you still have plans to work on this? Or should I submit my v3 with
> > in-order reception supported for rx frames.
> 
> The problem is, that the current code triggers a ordering issue (at least
> on the imx6) in non FIFO mode. The frames are not received as the
> documentation states. If you have access, take a look at "SR#
> 1-4074792564 : CAN Ordering Issues". It seems the freescale support
> doesn't have much interest in confirming the issue, nor bringing us in
> touch with the people who have access to the IP core source to see what's
> going on.
> 
> 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.

I can ask internally about more details on the "SR# 1-4074792564 : CAN Ordering Issues".

Regards,
Bhupesh

  reply	other threads:[~2015-12-10 12:22 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 [this message]
2015-12-10 12:22             ` Sharma Bhupesh
2015-12-11 16:01             ` Robert Schwebel
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=BY1PR0301MB1303A87AF2B3FFBB6CDA90EE82E90@BY1PR0301MB1303.namprd03.prod.outlook.com \
    --to=bhupesh.sharma@freescale.com \
    --cc=Sakar.Arora@freescale.com \
    --cc=arnd@arndb.de \
    --cc=bhupesh.linux@gmail.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: 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.