From: AnilKumar Ch <anilkumar@ti.com>
To: linux-omap@vger.kernel.org
Cc: tony@atomide.com, wg@grandegger.com, mkl@pengutronix.de,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
AnilKumar Ch <anilkumar@ti.com>
Subject: [PATCH v2 0/2] Add D_CAN device tree data to AM335x-EVM
Date: Wed, 25 Jul 2012 17:53:30 +0530 [thread overview]
Message-ID: <1343219012-19472-1-git-send-email-anilkumar@ti.com> (raw)
Thid patch series adds device tree data to AM335x-EVM file and
adds pinmux settings required to configure two of the AM335x EVM
pins to D_CAN TX/RX pins.
Changes from v1:
- These two patches separated from c_can DT support
patch series.
AnilKumar Ch (2):
arm/dts: AM33XX: Add D_CAN device tree data
arm/dts: AM33XX: Configure pinmuxs for D_CAN1 on AM335x-EVM
arch/arm/boot/dts/am335x-evm.dts | 13 +++++++++++++
arch/arm/boot/dts/am33xx.dtsi | 5 +++++
2 files changed, 18 insertions(+)
--
1.7.9.5
next reply other threads:[~2012-07-25 12:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 12:23 AnilKumar Ch [this message]
2012-07-25 12:23 ` [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data AnilKumar Ch
2012-07-25 12:43 ` Sergei Shtylyov
2012-07-26 8:36 ` Daniel Mack
2012-07-26 13:04 ` Sergei Shtylyov
[not found] ` <50114069.7070605-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
2012-08-03 9:14 ` Vaibhav Hiremath
2012-07-26 8:46 ` Koen Kooi
[not found] ` <9D2B44C8-820E-4E96-A480-7A650583BC92-QLwJDigV5abLmq1fohREcCpxlwaOVQ5f@public.gmane.org>
2012-07-26 9:03 ` AnilKumar, Chimata
[not found] ` <331ABD5ECB02734CA317220B2BBEABC13EA04433-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-07-26 9:14 ` Marc Kleine-Budde
2012-07-26 9:35 ` Koen Kooi
2012-08-03 6:28 ` Vaibhav Hiremath
2012-08-07 11:40 ` AnilKumar, Chimata
[not found] ` <1343219012-19472-1-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org>
2012-07-25 12:23 ` [PATCH v2 2/2] arm/dts: AM33XX: Configure pinmuxs for D_CAN1 on AM335x-EVM 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=1343219012-19472-1-git-send-email-anilkumar@ti.com \
--to=anilkumar@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=tony@atomide.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 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).