public inbox for linux-can@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: dev@sebastianhaas.info, linux-can@vger.kernel.org
Subject: Re: [RFC] can: Introducing CANFD for af_can & can-raw
Date: Wed, 21 Mar 2012 16:47:37 +0100	[thread overview]
Message-ID: <2683498.lh8gVOy8oT@ws-stein> (raw)
In-Reply-To: <4F69DCEF.20800@pengutronix.de>

Am Mittwoch, 21. März 2012, 14:51:43 schrieb Marc Kleine-Budde:
> On 03/21/2012 02:29 PM, Alexander Stein wrote:
> >> Further, there are only certain dlc values allowed for CAN FD. We must
> >> decide if the enforce these values or simply do padding with "0"
> >> somewhere.> 
> > What I understand from the proposal is that DLCs >8 are optional. So you
> > might get hardware which still supports only 8 bytes. How can/should
> > this be handled?
> 
> I haven't read the pdf that Kurt linked in the original mail. Is the
> usage of dlc > 8 optional or the support of dlc > 8 in hardware?

Quoted from section 6:
> The CAN FD protocol allows frames with more than eight data bytes. It is
> not required that all CAN FD implementations support longer frames, CAN
> FD implementations may be limited to a subset of DATA FIELD length. A CAN FD
> implementation that supports only up to e.g. eight data bytes in a frame
> shall not treat longer received frames as an error, fault-free longer
> frames shall be acknowledged and shall take part in acceptance filtering.
> Received data bytes that exceed the CAN FD’s data handling capacity shall
> be discarded. A such limited CAN FD implementation that is requested to
> transmit a longer frame shall fill up the data bytes in the frame that
> exceed the data handling capacity with a constant byte pattern. This
> pattern shall be chosen so that it does not cause the insertion of STUFF
> BITS, e.g. 0xCC.

Sounds to me like hardware support of dlc > 8 is optional. Even in the fact 
that you want the controller to send more than e.g. 8 bytes the controller 
shall insert stuff bits (0xCC) for unsupported data bytes.

Alexander
-- 
Dipl.-Inf. Alexander Stein

SYS TEC electronic GmbH
August-Bebel-Str. 29
D-07973 Greiz

Tel: +49-3661-6279-0, Fax: +49-3661-6279-99
eMail:    Alexander.Stein@systec-electronic.com
Internet: http://www.systec-electronic.com

Managing Director: Dipl.-Phys. Siegmar Schmidt
Commercial registry: Amtsgericht Jena, HRB 205563

      reply	other threads:[~2012-03-21 15:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21  9:10 [RFC] can: Introducing CANFD for af_can & can-raw Kurt Van Dijck
     [not found] ` <E1SAIM4-0007a6-Sf@smtprelay03.ispgateway.de>
2012-03-21 11:05   ` Kurt Van Dijck
2012-03-21 11:43     ` Marc Kleine-Budde
2012-03-21 12:08       ` Kurt Van Dijck
2012-03-21 12:32         ` Marc Kleine-Budde
2012-03-21 12:51           ` Kurt Van Dijck
2012-03-21 13:19             ` Marc Kleine-Budde
2012-03-21 13:21           ` Oliver Hartkopp
2012-03-21 13:53             ` Kurt Van Dijck
2012-03-21 14:49               ` Oliver Hartkopp
2012-03-21 15:26                 ` Oliver Hartkopp
2012-03-22  9:03                 ` Kurt Van Dijck
2012-03-21 14:56               ` Wolfgang Grandegger
2012-03-21 15:05                 ` Oliver Hartkopp
2012-03-22  9:24                   ` Kurt Van Dijck
2012-03-22  9:32                     ` Marc Kleine-Budde
2012-03-22  9:38                     ` Wolfgang Grandegger
2012-03-22 10:13                       ` Kurt Van Dijck
2012-03-23 11:01                         ` Wolfgang Grandegger
2012-03-22  9:57                   ` Kurt Van Dijck
2012-03-22 10:06                     ` Wolfgang Grandegger
2012-03-22 10:35                       ` Kurt Van Dijck
2012-03-22 11:00                         ` Wolfgang Grandegger
2012-03-22 12:25                           ` Oliver Hartkopp
2012-03-22 12:47                             ` Kurt Van Dijck
2012-03-21 13:29           ` Alexander Stein
2012-03-21 13:34             ` Kurt Van Dijck
2012-03-21 13:51             ` Marc Kleine-Budde
2012-03-21 15:47               ` Alexander Stein [this message]

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=2683498.lh8gVOy8oT@ws-stein \
    --to=alexander.stein@systec-electronic.com \
    --cc=dev@sebastianhaas.info \
    --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