All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Dong Aisheng <b29396@freescale.com>, linux-can@vger.kernel.org
Cc: wg@grandegger.com, varkabhadram@gmail.com,
	netdev@vger.kernel.org, socketcan@hartkopp.net,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V1 4/4] can: m_can: allow to send std frame on CAN FD mode
Date: Wed, 05 Nov 2014 11:41:34 +0100	[thread overview]
Message-ID: <5459FEDE.9050405@pengutronix.de> (raw)
In-Reply-To: <1415174326-6623-4-git-send-email-b29396@freescale.com>

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

On 11/05/2014 08:58 AM, Dong Aisheng wrote:
> The current code sends all CAN frames on CAN FD format(with BRS or not)
> if CAN_CTRLMODE_FD is enabled.
> However, even CAN_CTRLMODE_FD is enabled, the can tool may still
> send normal frames.
> e.g.
> ip link set can0 up type can bitrate 1000000 dbitrate 1000000 fd on
> cansend can0 123#112233
> 
> Therefore sending normal CAN frame on FD format seems not reasonable
> and the CAN FD incapable device may not be able to receive it correctly.
> 
> The patch switches the M_CAN operation mode to ISO11898-1 instead of
> staying on CAN FD operation mode by writing "11" to CMR bit if find
> we're sending a normal can skb.

With this patch applied and Olivre's version of 3/4, how does the
application send CAN-FD frames?
1. witch on CAN-FD via "ip fd on"
2. write a struct canfd_frame

Correct?

What happens if:
3. write a struct can_frame

A CAN frame is send?

Oliver are you okay with this behaviour?

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 V1 4/4] can: m_can: allow to send std frame on CAN FD mode
Date: Wed, 05 Nov 2014 11:41:34 +0100	[thread overview]
Message-ID: <5459FEDE.9050405@pengutronix.de> (raw)
In-Reply-To: <1415174326-6623-4-git-send-email-b29396@freescale.com>

On 11/05/2014 08:58 AM, Dong Aisheng wrote:
> The current code sends all CAN frames on CAN FD format(with BRS or not)
> if CAN_CTRLMODE_FD is enabled.
> However, even CAN_CTRLMODE_FD is enabled, the can tool may still
> send normal frames.
> e.g.
> ip link set can0 up type can bitrate 1000000 dbitrate 1000000 fd on
> cansend can0 123#112233
> 
> Therefore sending normal CAN frame on FD format seems not reasonable
> and the CAN FD incapable device may not be able to receive it correctly.
> 
> The patch switches the M_CAN operation mode to ISO11898-1 instead of
> staying on CAN FD operation mode by writing "11" to CMR bit if find
> we're sending a normal can skb.

With this patch applied and Olivre's version of 3/4, how does the
application send CAN-FD frames?
1. witch on CAN-FD via "ip fd on"
2. write a struct canfd_frame

Correct?

What happens if:
3. write a struct can_frame

A CAN frame is send?

Oliver are you okay with this behaviour?

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/1a6e3879/attachment-0001.sig>

  reply	other threads:[~2014-11-05 10:41 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
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 [this message]
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=5459FEDE.9050405@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.