From: Fabio Baltieri <fabio.baltieri@gmail.com>
To: linux-can@vger.kernel.org
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Wolfgang Grandegger <wg@grandegger.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH can-next 0/5] can: add LED trigger support to common devices
Date: Sun, 5 Aug 2012 16:48:14 +0200 [thread overview]
Message-ID: <20120805144814.GA2804@gmail.com> (raw)
Hello,
this patch series adds support for LED triggers to CAN devices commonly
found on SoC architectures, using the support code recently merged in
Marc's can-next tree.
I actually modified only drivers who's devices may be commonly found
in embedded platforms with associated cpu-controlled LEDs, let me know
if I missed anything.
As I lack the actual hardware, these patches are *compile tested* only,
so I hope to get some test on real hardware from other developers,
through the modifications should be quite straightforward.
Also, I'll let you know that I may not have access to my email during
the next week, so if you write me, I'll try to answer as soon as
possible.
Fabio
Fabio Baltieri (5):
can: at91_can: add LED trigger support
can: ti_hecc: add LED trigger support
can: c_can: add LED trigger support
can: mcp251x: add LED trigger support
can: sja1000: add LED trigger support
at91_can.c | 10 ++++++++++
c_can/c_can.c | 17 ++++++++++++++++-
mcp251x.c | 23 +++++++++++++++++++----
sja1000/sja1000.c | 17 ++++++++++++++++-
ti_hecc.c | 10 ++++++++++
5 files changed, 71 insertions(+), 6 deletions(-)
next reply other threads:[~2012-08-05 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 14:48 Fabio Baltieri [this message]
2012-08-05 14:51 ` [PATCH can-next 1/5] can: at91_can: add LED trigger support Fabio Baltieri
2012-08-05 14:51 ` [PATCH can-next 2/5] can: ti_hecc: " Fabio Baltieri
2012-08-05 14:51 ` [PATCH can-next 3/5] can: c_can: " Fabio Baltieri
2012-08-05 14:51 ` [PATCH can-next 4/5] can: mcp251x: " Fabio Baltieri
2012-08-05 14:51 ` [PATCH can-next 5/5] can: sja1000: " Fabio Baltieri
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=20120805144814.GA2804@gmail.com \
--to=fabio.baltieri@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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 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.