From: AnilKumar Ch <anilkumar@ti.com>
To: wg@grandegger.com, mkl@pengutronix.de, linux-can@vger.kernel.org
Cc: devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
anantgole@ti.com, nsekhar@ti.com, AnilKumar Ch <anilkumar@ti.com>
Subject: [PATCH v3 0/3] Add DT support to C_CAN/D_CAN controller
Date: Thu, 2 Aug 2012 16:32:16 +0530 [thread overview]
Message-ID: <1343905339-4642-1-git-send-email-anilkumar@ti.com> (raw)
This patch series adds the device tree support and Runtime PM support
to C_CAN/D_CAN controller.
These patches have been tested on AM335x EVM using some additional
patches to add device tree data to EVM dts files and to initialize
D_CAN RAM. D_CAN raminit is controlled from control module register.
This patch will be submitted once control module MFD driver support
is added.
These patches are based on linx-can-next tree.
Due to lack of hardware I am not able to test c_can functionality.
I appreciate if anyone can test c_can functionality with this patch
series.
Changes from v2:
- Incorporated Marcs on v2
* Fix compilation errors in pci due to device name changes
in v2 by adding new patch.
Changes from v1:
- Separated 4 patches into CAN driver specific and device
tree data addition specific.
- Incorporated Marc's comments on v1
* Modified c_can_dev_id enum to handle both devtype and
platform device id index.
* Removed "legacy bosch,c_can_platform" from DT bindings
AnilKumar Ch (3):
can: c_can: Add device tree support to Bosch C_CAN/D_CAN controller
can: c_can: Modify c_can device names in c_can_pci driver
can: c_can: Add runtime PM support to Bosch C_CAN/D_CAN controller
.../devicetree/bindings/net/can/c_can.txt | 37 +++++++++++
drivers/net/can/c_can/c_can.h | 5 +-
drivers/net/can/c_can/c_can_pci.c | 6 +-
drivers/net/can/c_can/c_can_platform.c | 65 +++++++++++++++-----
4 files changed, 91 insertions(+), 22 deletions(-)
create mode 100644 Documentation/devicetree/bindings/net/can/c_can.txt
--
1.7.9.5
next reply other threads:[~2012-08-02 11:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 11:02 AnilKumar Ch [this message]
2012-08-02 11:02 ` [PATCH v3 1/3] can: c_can: Add device tree support to Bosch C_CAN/D_CAN controller AnilKumar Ch
2012-08-02 11:33 ` Arnd Bergmann
2012-08-02 12:01 ` AnilKumar, Chimata
[not found] ` <1343905339-4642-1-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org>
2012-08-02 11:02 ` [PATCH v3 2/3] can: c_can: Modify c_can device names in c_can_pci driver AnilKumar Ch
2012-08-02 11:02 ` [PATCH v3 3/3] can: c_can: Add runtime PM support to Bosch C_CAN/D_CAN controller AnilKumar Ch
2012-08-02 11:13 ` [PATCH v3 0/3] Add DT support to " Marc Kleine-Budde
[not found] ` <501A60C0.1040504-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-08-02 11:21 ` AnilKumar, Chimata
2012-08-02 11:23 ` Marc Kleine-Budde
[not found] ` <501A633A.5000100-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-08-02 11:39 ` AnilKumar, Chimata
[not found] ` <331ABD5ECB02734CA317220B2BBEABC13EA081FB-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-08-02 11:45 ` Marc Kleine-Budde
-- strict thread matches above, loose matches on Subject: below --
2012-08-02 13:13 AnilKumar Ch
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=1343905339-4642-1-git-send-email-anilkumar@ti.com \
--to=anilkumar@ti.com \
--cc=anantgole@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=nsekhar@ti.com \
--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.