linux-toradex.git/include/linux/can/dev.h, branch v2.6.38.5

Fix some #includes in CAN drivers (rebased for net-next-2.6)

2010-04-13T10:32:42+00:00

In the current implementation, CAN drivers need to #include 
_before_ they #include , which is both ugly and
unnecessary.

Fix this by including  in  and remove the
#include  lines from drivers.

Signed-off-by: Hans J. Koch 
Signed-off-by: David S. Miller

can: netlink support for bus-error reporting and counters

2010-02-26T09:48:49+00:00

This patch makes the bus-error reporting configurable and allows to
retrieve the CAN TX and RX bus error counters via netlink interface.
I have added support for the SJA1000. The TX and RX bus error counters
are also copied to the data fields 6..7 of error messages when state
changes are reported.

Signed-off-by: Wolfgang Grandegger 
Signed-off-by: David S. Miller

can: Proper ctrlmode handling for CAN devices

2010-01-15T09:39:17+00:00

This patch adds error checking of ctrlmode values for CAN devices. As
an example all availabe bits are implemented in the mcp251x driver.

Signed-off-by: Christian Pellegrin 
Acked-by: Wolfgang Grandegger 
Signed-off-by: David S. Miller

can: Unify droping of invalid tx skbs and netdev stats

2010-01-12T10:00:46+00:00

To prevent the CAN drivers to operate on invalid socketbuffers the skbs are
now checked and silently dropped at the xmit-function consistently.

Also the netdev stats are consistently using the CAN data length code (dlc)
for [rx|tx]_bytes now.

Signed-off-by: Oliver Hartkopp 
Acked-by: Wolfgang Grandegger 
Signed-off-by: David S. Miller

can: Fix data length code handling in rx path

2009-12-14T03:47:42+00:00

A valid CAN dataframe can have a data length code (DLC) of 0 .. 8 data bytes.

When reading the CAN controllers register the 4-bit value may contain values
from 0 .. 15 which may exceed the reserved space in the socket buffer!

The ISO 11898-1 Chapter 8.4.2.3 (DLC field) says that register values > 8
should be reduced to 8 without any error reporting or frame drop.

This patch introduces a new helper macro to cast a given 4-bit data length
code (dlc) to __u8 and ensure the DLC value to be max. 8 bytes.

The different handlings in the rx path of the CAN netdevice drivers are fixed.

Signed-off-by: Oliver Hartkopp 
Signed-off-by: Wolfgang Grandegger 
Signed-off-by: David S. Miller

can: provide library functions for skb allocation

2009-10-20T07:08:01+00:00

This patch makes the private functions alloc_can_skb() and
alloc_can_err_skb() of the at91_can driver public and adapts all
drivers to use these. While making the patch I realized, that
the skb's are *not* setup consistently. It's now done as shown
below:

  skb->protocol = htons(ETH_P_CAN);
  skb->pkt_type = PACKET_BROADCAST;
  skb->ip_summed = CHECKSUM_UNNECESSARY;
  *cf = (struct can_frame *)skb_put(skb, sizeof(struct can_frame));
  memset(*cf, 0, sizeof(struct can_frame));

The frame is zeroed out to avoid uninitialized data to be passed to
user space. Some drivers or library code did not set "pkt_type" or
"ip_summed". Also,  "__constant_htons()" should not be used for
runtime invocations, as pointed out by David Miller.

Signed-off-by: Wolfgang Grandegger 
Signed-off-by: David S. Miller

can: make the number of echo skb's configurable

2009-10-13T10:44:04+00:00

This patch allows the CAN controller driver to define the number of echo
skb's used for the local loopback (echo), as suggested by Kurt Van
Dijck, with the function:

  struct net_device *alloc_candev(int sizeof_priv,
                                  unsigned int echo_skb_max);

The CAN drivers have been adapted accordingly. For the ems_usb driver,
as suggested by Sebastian Haas, the number of echo skb's has been
increased to 10, which improves the transmission performance a lot.

Signed-off-by: Wolfgang Grandegger 
Signed-off-by: Kurt Van Dijck 
Signed-off-by: David S. Miller

can: add can_free_echo_skb() for upcoming drivers

2009-09-04T09:16:14+00:00

This patch adds the function can_free_echo_skb to the CAN
device interface to allow upcoming drivers to release echo
skb's in case of error.

Signed-off-by: Wolfgang Grandegger 
Signed-off-by: David S. Miller

can: CAN Network device driver and Netlink interface

2009-05-18T22:41:41+00:00

The CAN network device driver interface provides a generic interface to
setup, configure and monitor CAN network devices. It exports a set of
common data structures and functions, which all real CAN network device
drivers should use. Please have a look to the SJA1000 or MSCAN driver
to understand how to use them. The name of the module is can-dev.ko.

Furthermore, it adds a Netlink interface allowing to configure the CAN
device using the program "ip" from the iproute2 utility suite.

For further information please check "Documentation/networking/can.txt"

Signed-off-by: Wolfgang Grandegger 
Signed-off-by: Oliver Hartkopp 
Signed-off-by: David S. Miller