From: anilkumar@ti.com (AnilKumar Ch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Add device tree data for AM33XX devices
Date: Thu, 16 Aug 2012 17:50:06 +0530 [thread overview]
Message-ID: <1345119610-5247-1-git-send-email-anilkumar@ti.com> (raw)
Add pinctrl and d_can device tree data to AM33XX family of devices.
First two patches add support for pinctrl DT data and rest adds
dcan DT data.
Reason behind combining these patches is to apply cleanly on
linux-omap devel-dt tree because these are sequential patches.
These patches were tested on AM335x-Bone and AM335x-EVM apply
on linux-omap:devel-dt tree with this patch
http://lkml.org/lkml/2012/8/15/106
AnilKumar Ch (4):
arm/dts: AM33XX: Add basic pinctrl device tree data
arm/dts: AM33XX: Configure pinmuxs for user leds control on Bone
arm/dts: AM33XX: Configure pinmuxs for D_CAN1 on AM335x-EVM
arm/dts: AM33XX: Add D_CAN device tree data
arch/arm/boot/dts/am335x-bone.dts | 14 ++++++++++++++
arch/arm/boot/dts/am335x-evm.dts | 16 ++++++++++++++++
arch/arm/boot/dts/am33xx.dtsi | 27 +++++++++++++++++++++++++++
3 files changed, 57 insertions(+)
--
1.7.9.5
next reply other threads:[~2012-08-16 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 12:20 AnilKumar Ch [this message]
2012-08-16 12:20 ` [PATCH v4 1/4] arm/dts: AM33XX: Add basic pinctrl device tree data AnilKumar Ch
2012-08-16 12:20 ` [PATCH v4 2/4] arm/dts: AM33XX: Configure pinmuxs for user leds control on Bone AnilKumar Ch
2012-08-16 12:20 ` [PATCH v3 3/4] arm/dts: AM33XX: Configure pinmuxs for D_CAN1 on AM335x-EVM AnilKumar Ch
2012-08-24 20:14 ` Tony Lindgren
2012-08-28 6:21 ` Vaibhav Hiremath
2012-08-16 12:20 ` [PATCH v3 4/4] arm/dts: AM33XX: Add D_CAN device tree data 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=1345119610-5247-1-git-send-email-anilkumar@ti.com \
--to=anilkumar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).