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 14:29:05 +0100 [thread overview]
Message-ID: <1683048.Xku7xyE0R6@ws-stein> (raw)
In-Reply-To: <4F69CA74.3020607@pengutronix.de>
Am Mittwoch, 21. März 2012, 13:32:52 schrieb Marc Kleine-Budde:
> On 03/21/2012 01:08 PM, Kurt Van Dijck wrote:
> > On Wed, Mar 21, 2012 at 12:43:31PM +0100, Marc Kleine-Budde wrote:
> >> On 03/21/2012 12:05 PM, Kurt Van Dijck wrote:
> >>> Hi Sebastian,
> >>>
> >>> On the ICC, Bosch presentend CANFD[1].
> >>> I'll share my interpretation:
> >>> * CANFD is meant as a successor of CAN.
> >>>
> >>> * it addressess data throughput in 2 ways:
> >>> - higher data bitrate for data using a second
> >>>
> >>> set of bittimings.
> >>>
> >>> - longer message payload (up to 64 byte).
> >>>
> >>> * it remains very compatible to CAN, although _NOT_
> >>>
> >>> bus-compatible (ie. you put it on a seperate bus).
> >>
> >> This means:
> >> You cannot have a Bus using one (or more) of the CAN-FD features with
> >> non CAN-FD compatible nodes.
> >>
> >> From my point of view this can be translated into a new property in
> >> "can.ctrlmode_supported". A device adds "CAN_CTRLMODE_CANFD" if it
> >> supports CAN FD mode. Then it's a global setting to put the device
> >> into
> >> CAN FD mode.
> >
> > Yep, good idea.
> >
> >> In the TX path the stack should refuse the new 64 byte frames at all
> >> or
> >> frames with dlc > 8 byes if the device is not in CAN FD mode.
> >
> > I did not yet do such think since I did not implement CANFD on device
> > level yet. I think can_send() is a good place to put such tricks.
>
> Yes, for CAN_RAW, but in the driver we must extend the
> "can_dropped_invalid_skb()" function, too: drop frames with dlc >8 if
> device is not in CAN FD mode.
>
> 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?
Alexnder
--
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
next prev parent reply other threads:[~2012-03-21 13:29 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 [this message]
2012-03-21 13:34 ` Kurt Van Dijck
2012-03-21 13:51 ` Marc Kleine-Budde
2012-03-21 15:47 ` Alexander Stein
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=1683048.Xku7xyE0R6@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