linux.git/include/linux/can/dev.h, branch v3.18.40

can: fix handling of unmodifiable configuration options

2016-06-03T15:30:37+00:00

[ Upstream commit bb208f144cf3f59d8f89a09a80efd04389718907 ]

As described in 'can: m_can: tag current CAN FD controllers as non-ISO'
(6cfda7fbebe) it is possible to define fixed configuration options by
setting the according bit in 'ctrlmode' and clear it in 'ctrlmode_supported'.
This leads to the incovenience that the fixed configuration bits can not be
passed by netlink even when they have the correct values (e.g. non-ISO, FD).

This patch fixes that issue and not only allows fixed set bit values to be set
again but now requires(!) to provide these fixed values at configuration time.
A valid CAN FD configuration consists of a nominal/arbitration bittiming, a
data bittiming and a control mode with CAN_CTRLMODE_FD set - which is now
enforced by a new can_validate() function. This fix additionally removed the
inconsistency that was prohibiting the support of 'CANFD-only' controller
drivers, like the RCar CAN FD.

For this reason a new helper can_set_static_ctrlmode() has been introduced to
provide a proper interface to handle static enabled CAN controller options.

Reported-by: Ramesh Shanmugasundaram 
Signed-off-by: Oliver Hartkopp 
Reviewed-by: Ramesh Shanmugasundaram  
Cc:  # >= 3.18
Signed-off-by: Marc Kleine-Budde 
Signed-off-by: Sasha Levin

can: dev: add can_is_canfd_skb() API

2014-11-18T12:23:31+00:00

The CAN device drivers can use can_is_canfd_skb() to check if the frame to send
is on CAN FD mode or normal CAN mode.

Acked-by: Oliver Hartkopp 
Signed-off-by: Dong Aisheng 
Signed-off-by: Marc Kleine-Budde

can: unify identifiers to ensure unique include processing

2014-05-19T07:38:24+00:00

Armin pointed me to the fact that the identifier which is used to ensure the
unique include processing in lunux/include/uapi/linux/can.h is CAN_H.
This clashed with his own source as includes from libraries and APIs should
use an underscore '_' at the identifier start.

This patch fixes the protection identifiers in all CAN relavant includes.

Reported-by: Armin Burchardt 
Signed-off-by: Oliver Hartkopp 
Signed-off-by: Marc Kleine-Budde

can: allow to change the device mtu for CAN FD capable devices

2014-03-07T08:18:23+00:00

The configuration for CAN FD depends on CAN_CTRLMODE_FD enabled in the driver
specific ctrlmode_supported capabilities.

The configuration can be done either with the 'fd { on | off }' option in the
'ip' tool from iproute2 or by setting the CAN netdevice MTU to CAN_MTU (16) or
to CANFD_MTU (72).

Signed-off-by: Oliver Hartkopp 
Acked-by: Stephane Grosjean 
Signed-off-by: Marc Kleine-Budde

can: introduce the data bitrate configuration for CAN FD

2014-03-07T08:18:22+00:00

As CAN FD offers a second bitrate for the data section of the CAN frame the
infrastructure for storing and configuring this second bitrate is introduced.
Improved the readability of the if-statement by inserting some newlines.

Signed-off-by: Oliver Hartkopp 
Acked-by: Stephane Grosjean 
Signed-off-by: Marc Kleine-Budde

can: add ability to allocate CANFD frame in skb data

2014-02-04T08:34:33+00:00

This patch adds the ability of allocating a CANFD frame data structure in the
skb data area.

Signed-off-by: Stephane Grosjean 
Acked-by: Oliver Hartkopp 
Signed-off-by: Marc Kleine-Budde

can: export a safe netdev_priv wrapper for candev

2013-01-26T15:58:59+00:00

In net_device notifier calls, it was impossible to determine
if a CAN device is based on candev in a safe way.
This patch adds such test in order to access candev storage
from within those notifiers.

Signed-off-by: Kurt Van Dijck 
Acked-by: Oliver Hartkopp 
Signed-off-by: Fabio Baltieri 
Signed-off-by: Marc Kleine-Budde

can: add tx/rx LED trigger support

2013-01-26T15:58:59+00:00

This patch implements the functions to add two LED triggers, named
-tx and -rx, to a canbus device driver.

Triggers are called from specific handlers by each CAN device driver and
can be disabled altogether with a Kconfig option.

The implementation keeps the LED on when the interface is UP and blinks
the LED on network activity at a configurable rate.

This only supports can-dev based drivers, as it uses some support field
in the can_priv structure.

Supported drivers should call devm_can_led_init() and can_led_event() as
needed.

Cleanup is handled automatically by devres, so no *_exit function is
needed.

Supported events are:
- CAN_LED_EVENT_OPEN: turn on tx/rx LEDs
- CAN_LED_EVENT_STOP: turn off tx/rx LEDs
- CAN_LED_EVENT_TX: trigger tx LED blink
- CAN_LED_EVENT_RX: trigger tx LED blink

Cc: Wolfgang Grandegger 
Cc: Marc Kleine-Budde 
Signed-off-by: Fabio Baltieri 
Acked-by: Oliver Hartkopp 
Signed-off-by: Marc Kleine-Budde

can: mark bittiming_const pointer in struct can_priv as const

2012-07-20T10:31:05+00:00

This patch marks the bittiming_const pointer as in the struct can_pric as
"const". This allows us to mark the struct can_bittiming_const in the CAN
drivers as "const", too.

Signed-off-by: Marc Kleine-Budde

candev: add/update helpers for CAN FD

2012-06-19T19:40:14+00:00

- update sanity checks
- add DLC to length conversion helpers
  - can_dlc2len() - get data length from can_dlc with sanitized can_dlc
  - can_len2dlc() - map the sanitized data length to an appropriate DLC

Signed-off-by: Oliver Hartkopp 
Signed-off-by: Marc Kleine-Budde