From: Anssi Hannula <anssi.hannula@bitwise.fi>
To: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Michal Simek <michal.simek@xilinx.com>,
linux-can@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: [PATCH 0/3] can: xilinx_can: CAN FD core support
Date: Wed, 27 Jun 2018 17:34:11 +0300 [thread overview]
Message-ID: <20180627143414.7114-1-anssi.hannula@bitwise.fi> (raw)
Hi all,
This patchset adds support for the Xilinx CAN FD core to the
xilinx_can driver.
This is on top of my previous patches:
- 2018-01-26 "[PATCH 0/5 resend] can: various fixes to xilinx_can driver"
- 2018-01-29 "[PATCH] can: xilinx_can: use can_change_state()"
- 2018-05-18 "[PATCH 0/4] can: fixes to xilinx_can".
All the changes are also here, rebased on top of linux-can master
(trivial rebase as there have been no other changes to the driver
recently):
https://github.com/anssih/linux/commits/e7a8b6dcf4b6ee2b69c8f2f8f1fd43f97d008b95
Let me know if you want me to post them again.
Anssi Hannula (3):
dt-bindings: can: xilinx_can: add Xilinx CAN FD bindings
can: xilinx_can: refactor code in preparation for CAN FD support
can: xilinx_can: add support for Xilinx CAN FD core
Documentation/devicetree/bindings/net/can/xilinx_can.txt | 36 -
drivers/net/can/xilinx_can.c | 480 +++++++++++----
2 files changed, 399 insertions(+), 117 deletions(-)
--
Anssi Hannula / Bitwise Oy
next reply other threads:[~2018-06-27 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 14:34 Anssi Hannula [this message]
2018-06-27 14:34 ` [PATCH 1/3] dt-bindings: can: xilinx_can: add Xilinx CAN FD bindings Anssi Hannula
2018-07-03 22:51 ` Rob Herring
2018-07-04 7:20 ` Anssi Hannula
2018-06-27 14:34 ` [PATCH 2/3] can: xilinx_can: refactor code in preparation for CAN FD support Anssi Hannula
2018-06-27 14:34 ` [PATCH 3/3] can: xilinx_can: add support for Xilinx CAN FD core Anssi Hannula
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=20180627143414.7114-1-anssi.hannula@bitwise.fi \
--to=anssi.hannula@bitwise.fi \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=mkl@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=wg@grandegger.com \
/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;
as well as URLs for NNTP newsgroup(s).