All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Dong Aisheng <b29396@freescale.com>
Cc: linux-can@vger.kernel.org, wg@grandegger.com,
	varkabhadram@gmail.com, netdev@vger.kernel.org,
	socketcan@hartkopp.net, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 2/4] can: m_can: workaround for transmit data less than 4 bytes
Date: Wed, 05 Nov 2014 12:32:21 +0100	[thread overview]
Message-ID: <545A0AC5.80006@pengutronix.de> (raw)
In-Reply-To: <20141105103349.GA4007@shlinux1.ap.freescale.net>

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

On 11/05/2014 11:33 AM, Dong Aisheng wrote:
> On Wed, Nov 05, 2014 at 11:17:48AM +0100, Marc Kleine-Budde wrote:
>> On 11/05/2014 08:58 AM, Dong Aisheng wrote:
>>> At least on the i.MX6SX with M_CAN IP version 3.0.x, an issue with
>>
>> Can you add the imx mask revision, too and the exact m_can version (is
>> available).
>>
> 
> What do you mean imx mask revision?

In my imx6sdl/imx6q data sheet it's called: Chip Silicon Version
(USB_ANALOG_DIGPROG), I expect that the imx6sx has a the same register.

> By reading the Core Release Register (CREL), it seems the exact m_can
> version is 3.0.1. (CREL = 30130506).
> 
> So what about changing to as follows?
> "At least on the i.MX6SX with M_CAN IP version 3.0.1 (CREL = 30130506),
> an issue with"

Yes, please ass the imx silicon revision, too.

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/4] can: m_can: workaround for transmit data less than 4 bytes
Date: Wed, 05 Nov 2014 12:32:21 +0100	[thread overview]
Message-ID: <545A0AC5.80006@pengutronix.de> (raw)
In-Reply-To: <20141105103349.GA4007@shlinux1.ap.freescale.net>

On 11/05/2014 11:33 AM, Dong Aisheng wrote:
> On Wed, Nov 05, 2014 at 11:17:48AM +0100, Marc Kleine-Budde wrote:
>> On 11/05/2014 08:58 AM, Dong Aisheng wrote:
>>> At least on the i.MX6SX with M_CAN IP version 3.0.x, an issue with
>>
>> Can you add the imx mask revision, too and the exact m_can version (is
>> available).
>>
> 
> What do you mean imx mask revision?

In my imx6sdl/imx6q data sheet it's called: Chip Silicon Version
(USB_ANALOG_DIGPROG), I expect that the imx6sx has a the same register.

> By reading the Core Release Register (CREL), it seems the exact m_can
> version is 3.0.1. (CREL = 30130506).
> 
> So what about changing to as follows?
> "At least on the i.MX6SX with M_CAN IP version 3.0.1 (CREL = 30130506),
> an issue with"

Yes, please ass the imx silicon revision, too.

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141105/b6ee209c/attachment.sig>

  reply	other threads:[~2014-11-05 11:32 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05  7:58 [PATCH V2 1/4] can: m_can: update to support CAN FD features Dong Aisheng
2014-11-05  7:58 ` Dong Aisheng
2014-11-05  7:58 ` Dong Aisheng
2014-11-05  7:58 ` [PATCH V2 2/4] can: m_can: workaround for transmit data less than 4 bytes Dong Aisheng
2014-11-05  7:58   ` Dong Aisheng
2014-11-05  7:58   ` Dong Aisheng
2014-11-05 10:17   ` Marc Kleine-Budde
2014-11-05 10:17     ` Marc Kleine-Budde
2014-11-05 10:33     ` Dong Aisheng
2014-11-05 10:33       ` Dong Aisheng
2014-11-05 10:33       ` Dong Aisheng
2014-11-05 11:32       ` Marc Kleine-Budde [this message]
2014-11-05 11:32         ` Marc Kleine-Budde
2014-11-05 11:32         ` Dong Aisheng
2014-11-05 11:32           ` Dong Aisheng
2014-11-05 11:32           ` Dong Aisheng
2014-11-05  7:58 ` [PATCH V1 3/4] can: add can_is_canfd_skb() API Dong Aisheng
2014-11-05  7:58   ` Dong Aisheng
2014-11-05  7:58   ` Dong Aisheng
2014-11-05  9:39   ` Oliver Hartkopp
2014-11-05  9:39     ` Oliver Hartkopp
2014-11-05  7:58 ` [PATCH V1 4/4] can: m_can: allow to send std frame on CAN FD mode Dong Aisheng
2014-11-05  7:58   ` Dong Aisheng
2014-11-05  7:58   ` Dong Aisheng
2014-11-05 10:41   ` Marc Kleine-Budde
2014-11-05 10:41     ` Marc Kleine-Budde
2014-11-05 11:08     ` Oliver Hartkopp
2014-11-05 11:08       ` Oliver Hartkopp
2014-11-05 10:12 ` [PATCH V2 1/4] can: m_can: update to support CAN FD features Oliver Hartkopp
2014-11-05 10:12   ` Oliver Hartkopp
2014-11-05 11:26   ` Dong Aisheng
2014-11-05 11:26     ` Dong Aisheng
2014-11-05 11:26     ` Dong Aisheng
2014-11-05 13:10     ` Oliver Hartkopp
2014-11-05 13:10       ` Oliver Hartkopp
2014-11-05 12:47       ` Dong Aisheng
2014-11-05 12:47         ` Dong Aisheng
2014-11-05 12:47         ` Dong Aisheng
2014-11-05 13:15       ` Oliver Hartkopp
2014-11-05 13:15         ` Oliver Hartkopp
2014-11-05 12:47         ` Dong Aisheng
2014-11-05 12:47           ` Dong Aisheng
2014-11-05 12:47           ` Dong Aisheng
2014-11-05 13:19       ` Marc Kleine-Budde
2014-11-05 13:19         ` Marc Kleine-Budde
2014-11-05 13:46         ` Dong Aisheng
2014-11-05 13:46           ` Dong Aisheng
2014-11-05 13:46           ` Dong Aisheng
2014-11-05 14:35           ` Oliver Hartkopp
2014-11-05 14:35             ` Oliver Hartkopp
2014-11-05 11:35 ` Varka Bhadram
2014-11-05 11:35   ` Varka Bhadram
2014-11-05 11:36   ` Dong Aisheng
2014-11-05 11:36     ` Dong Aisheng
2014-11-05 11:36     ` Dong Aisheng

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=545A0AC5.80006@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=b29396@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-can@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    --cc=varkabhadram@gmail.com \
    --cc=wg@grandegger.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 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.