From: Dan Murphy <dmurphy@ti.com>
To: <wg@grandegger.com>, <mkl@pengutronix.de>, <davem@davemloft.net>,
<b29396@freescale.com>
Cc: <linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Dan Murphy <dmurphy@ti.com>
Subject: [PATCH v3 0/4] M_CAN Framework
Date: Fri, 11 Jan 2019 11:32:32 -0600 [thread overview]
Message-ID: <20190111173236.14329-1-dmurphy@ti.com> (raw)
All
Well it has taken me a while to get this working and ported to a provide a
m_can framework that manages the Bosch m_can stack and abstracts away devices
to use that framework.
The m_can.c is the framework that devices register to.
The device abstractions can provide read/write capability as well as bit timings
and also provide any other initializations that are device specific.
The m_can platform code will need to be updated as I have not tested this code.
The tcan code is working.
Dan
Dan Murphy (4):
can: m_can: Create a m_can platform framework
can: m_can: Migrate the m_can code to use the framework
dt-bindings: can: tcan4x5x: Add DT bindings for TCAN4x5X driver
can: tcan4x5x: Add tcan4x5x driver to the kernel
.../devicetree/bindings/net/can/tcan4x5x.txt | 37 +
drivers/net/can/m_can/Kconfig | 18 +
drivers/net/can/m_can/Makefile | 4 +-
drivers/net/can/m_can/m_can.c | 765 +++++++++---------
drivers/net/can/m_can/m_can_platform.c | 212 +++++
drivers/net/can/m_can/m_can_platform.h | 163 ++++
drivers/net/can/m_can/tcan4x5x.c | 458 +++++++++++
7 files changed, 1253 insertions(+), 404 deletions(-)
create mode 100644 Documentation/devicetree/bindings/net/can/tcan4x5x.txt
create mode 100644 drivers/net/can/m_can/m_can_platform.c
create mode 100644 drivers/net/can/m_can/m_can_platform.h
create mode 100644 drivers/net/can/m_can/tcan4x5x.c
--
2.20.1.98.gecbdaf0899
next reply other threads:[~2019-01-11 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 17:32 Dan Murphy [this message]
2019-01-11 17:32 ` [PATCH v3 1/4] can: m_can: Create a m_can platform framework Dan Murphy
2019-01-11 17:32 ` [PATCH v3 2/4] can: m_can: Migrate the m_can code to use the framework Dan Murphy
2019-01-11 17:32 ` [PATCH v3 3/4] dt-bindings: can: tcan4x5x: Add DT bindings for TCAN4x5X driver Dan Murphy
2019-01-11 17:32 ` [PATCH v3 4/4] can: tcan4x5x: Add tcan4x5x driver to the kernel Dan Murphy
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=20190111173236.14329-1-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=b29396@freescale.com \
--cc=davem@davemloft.net \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.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).