From: Dan Murphy <dmurphy@ti.com>
To: <wg@grandegger.com>, <mkl@pengutronix.de>, <davem@davemloft.net>
Cc: <linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Dan Murphy <dmurphy@ti.com>
Subject: [[RFC] PATCH v2 0/4] M_CAN framework patches
Date: Wed, 5 Dec 2018 13:28:21 -0600 [thread overview]
Message-ID: <20181205192825.11555-1-dmurphy@ti.com> (raw)
All
This patch series contains no code modifications. Based on Wolfgangs advice
I moved the files to different names and committe them independently so they
can be reviewed easier.
The first patch create the framework code abstracted from the main m_can.c.
The second patch adapts the m_can.c to use the framework code
The final patches add the TCAN device to the use the m_can framework.
Again these patches are RFC and no code modifications were made in v2.
I will be updating the code based on this version.
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 | 34 ++
drivers/net/can/m_can/Kconfig | 18 +
drivers/net/can/m_can/Makefile | 4 +-
drivers/net/can/m_can/m_can.c | 479 +++++++++---------
drivers/net/can/m_can/m_can_platform.c | 168 ++++++
drivers/net/can/m_can/m_can_platform.h | 100 ++++
drivers/net/can/m_can/tcan4x5x.c | 321 ++++++++++++
7 files changed, 870 insertions(+), 254 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.0.rc2.7.g965798d1f2
next reply other threads:[~2018-12-05 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 19:28 Dan Murphy [this message]
2018-12-05 19:28 ` [[RFC] PATCH v2 1/4] can: m_can: Create a m_can platform framework Dan Murphy
2018-12-05 19:28 ` [[RFC] PATCH v2 2/4] can: m_can: Migrate the m_can code to use the framework Dan Murphy
2018-12-05 19:28 ` [[RFC] PATCH v2 3/4] dt-bindings: can: tcan4x5x: Add DT bindings for TCAN4x5X driver Dan Murphy
2018-12-05 19:28 ` [[RFC] PATCH v2 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=20181205192825.11555-1-dmurphy@ti.com \
--to=dmurphy@ti.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).