From: Wolfgang Grandegger <wg@grandegger.com>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/7] can: CAN network device driver interface and drivers
Date: Tue, 12 May 2009 11:27:57 +0200 [thread overview]
Message-ID: <20090512092757.048938233@denx.de> (raw)
Hello,
here comes v2 of the patch series posted some time ago. See
http://marc.info/?l=linux-netdev&m=123507025810612&w=4.
Changes since v1:
- The SysFS interface has been replaced by the Netlink interface as
suggested by Patrick. For further information have a look to
chapter 6.5 of "Documentation/networking/can.txt" and the header
file "include/linux/can/netdev.h". The patch for the "ip" program of
the iproute2 utility suite will be provided separately.
- The restart function is now properly protected by "dev->tx_lock"
using the "netif_tx_[lock|unlock]" functions.
- For the restart, the device driver must now handle CAN_MODE_STOP as
well, apart from CAN_MODE_START to avoid race conditions.
- The "irq_lock" member of "struct can_priv" has been removed. The CAN
controller driver may should provide its own synchronization if
necessary.
- The restart function is now protected by "dev->tx_lock" using the
"netif_tx_lock/unlock" functions.
- Cleanup timer usage for the restart function.
- The unused do_set/get_ctrlmode member of "struct can_priv" have been
removed.
- "const" has been added to "struct net_device" for some functions not
allowed to touch that structure.
- The library functions "can_set_bittiming" and "can_close_cleanup" have
been renamed to the more general names "open_candev" and
"close_candev", respectively.
- Use "del_timer_sync" instead of "del_timer" for the re-start timer.
- The macro "ND2D()" has been replaced by "dev->dev.parent" as it does
not make the code more readable.
- Fix improper BTR setting for triple-sampling for the SJA1000 as
pointed out by Oliver.
- Dont use __u8 but __u32 as before for some members of "struct
can_bittiming[_const]" to avoid alignment trouble.
- Definitions shared with user-space applications have been moved to
"include/linux/can/netlink.h".
- Various other minor correction suggested on the netdev ML.
- The MSCAN driver for the MPC5200 has been removed. It needs to be
presented on the Linuxppc-dev and Devicetree-discuss ML as well,
which will be done by a sub-sequent patch.
- Add more source code documentation, especially for the structures
and functions related to bit-timing.
The PF_CAN protocol family for the Controller Area Network is available
in the kernel since version 2.6.25 but drivers for real CAN devices are
still missing. This patch series adds a generic CAN network device
driver interface and, as a start, a few drivers. It is the result of the
on-going discussion and development of the Socket-CAN project hosted at
the BerliOS web-server (http://developer.berlios.de/projects/socketcan).
The patch series consists of the following patches:
1/8) can: Documentation for the CAN device driver interface
2/8) can: Update MAINTAINERS and CREDITS file
3/8) can: CAN Network device driver and Netlink interface
4/8) can: Driver for the SJA1000 CAN controller
5/8) can: SJA1000 generic platform bus driver
6/8) can: SJA1000 driver for EMS PCI cards
7/8) can: SJA1000 driver for Kvaser PCI cards
Please consider these patches for inclusion.
Thanks,
Wolfgang.
next reply other threads:[~2009-05-12 9:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 9:27 Wolfgang Grandegger [this message]
2009-05-12 9:27 ` [PATCH v2 1/7] [PATCH 1/8] can: Documentation for the CAN device driver interface Wolfgang Grandegger
2009-05-12 9:27 ` [PATCH v2 2/7] [PATCH 2/8] can: Update MAINTAINERS and CREDITS file Wolfgang Grandegger
2009-05-12 9:28 ` [PATCH v2 3/7] [PATCH 3/8] can: CAN Network device driver and Netlink interface Wolfgang Grandegger
2009-05-13 6:30 ` Andrew Morton
2009-05-13 6:53 ` Andrew Morton
2009-05-13 11:37 ` Wolfgang Grandegger
2009-05-13 15:57 ` Andrew Morton
2009-05-14 9:51 ` Wolfgang Grandegger
2009-05-13 10:02 ` Oliver Hartkopp
2009-05-13 11:39 ` Wolfgang Grandegger
2009-05-13 12:08 ` Oliver Hartkopp
2009-05-13 12:23 ` Wolfgang Grandegger
2009-05-15 7:15 ` Oliver Hartkopp
2009-05-15 7:46 ` Wolfgang Grandegger
2009-05-13 21:31 ` Jonathan Corbet
2009-05-14 7:55 ` Wolfgang Grandegger
2009-05-12 9:28 ` [PATCH v2 4/7] [PATCH 4/8] can: Driver for the SJA1000 CAN controller Wolfgang Grandegger
2009-05-13 21:52 ` Jonathan Corbet
2009-05-14 9:03 ` Wolfgang Grandegger
2009-05-15 20:39 ` Jonathan Corbet
2009-05-15 21:24 ` Wolfgang Grandegger
2009-05-16 6:57 ` Wolfgang Grandegger
2009-05-20 21:31 ` Jonathan Corbet
2009-05-12 9:28 ` [PATCH v2 5/7] [PATCH 5/8] can: SJA1000 generic platform bus driver Wolfgang Grandegger
2009-05-13 22:02 ` Jonathan Corbet
2009-05-15 9:33 ` Wolfgang Grandegger
2009-05-14 6:46 ` Sascha Hauer
2009-05-15 9:35 ` Wolfgang Grandegger
2009-05-15 12:07 ` Sascha Hauer
2009-05-15 13:12 ` Wolfgang Grandegger
2009-05-12 9:28 ` [PATCH v2 6/7] [PATCH 6/8] can: SJA1000 driver for EMS PCI cards Wolfgang Grandegger
2009-05-12 9:28 ` [PATCH v2 7/7] [PATCH 7/8] can: SJA1000 driver for Kvaser " Wolfgang Grandegger
2009-05-13 22:20 ` Jonathan Corbet
2009-05-15 8:54 ` Wolfgang Grandegger
2009-05-12 9:46 [PATCH v2 0/7] can: CAN network device driver interface and drivers Subrata Modak
2009-05-12 9:58 ` Wolfgang Grandegger
2009-05-12 10:46 ` Oliver Hartkopp
2009-05-12 10:59 ` Subrata Modak
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=20090512092757.048938233@denx.de \
--to=wg@grandegger.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.