From: anilkumar@ti.com (AnilKumar Ch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/3] arm/dts: Add device tree data for AM33XX devices
Date: Wed, 5 Sep 2012 17:10:57 +0530 [thread overview]
Message-ID: <1346845260-10978-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 third one
adds dcan DT data.
Reason behind combining these patches is to apply cleanly on
linux-omap tree, because these are sequential patches.
These patches were tested on AM335x-Bone, AM335x-EVM and based
on linux-omap:master with this patch
http://www.mail-archive.com/linux-omap at vger.kernel.org/msg74393.html
Changes from v5:
- Incorporated Koen's comments on v5 series, user leds
trigger modifications.
- Dropped 4th and 5th patches, submitted v2 versions of
those in their corresponding mailing lists.
d_can:
Changes from v4:
- Incorporated Tony's comments on v4
* Converted all hex numbers to lower-case.
- Updated C_CAN bindings documentation according to recent
changes.
Changes from v3:
- Removed d_can1 node from am335x-evm.dts file. Instance
one of CAN (d_can1) is available on AM335x-EVM only under
a specific CPLD mode selection. am335x-evm.dts does not
support this mode so remove the d_can1 node.
- Dropped d_can pinmux settings patch, above comment
applies here as well.
Changes from v2:
- Incorporated Vaibhav H's comments on v2
* Added dcan0 instances to am33xx.dtsi file
Changes from v1:
- These two patches separated from c_can DT support
patch series.
pinctrl:
Changes from v4:
- Incorporated Tony's comments on v4
* Converted all hex numbers to lower-case.
- Added pinctrl api to leds-gpio driver to configure led
pins to GPIO mode.
Changes from v3:
- Updated the reg length based on latest AM335x TRM.
Changes from v2:
- user led pinmux comments updated according to Tony's
comment.
Changes from v1:
- Rebased the patches based on latest pinctrl-single driver
AnilKumar Ch (3):
arm/dts: AM33XX: Add basic pinctrl device tree data
arm/dts: AM33XX: Configure pinmuxs for user leds control on Bone
arm/dts: AM33XX: Add D_CAN device tree data
arch/arm/boot/dts/am335x-bone.dts | 43 +++++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/am33xx.dtsi | 27 +++++++++++++++++++++++
2 files changed, 70 insertions(+)
--
1.7.9.5
next reply other threads:[~2012-09-05 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 11:40 AnilKumar Ch [this message]
2012-09-05 11:40 ` [PATCH RESEND v5 1/3] arm/dts: AM33XX: Add basic pinctrl device tree data AnilKumar Ch
2012-09-05 23:35 ` Tony Lindgren
2012-09-05 11:40 ` [PATCH v6 2/3] arm/dts: AM33XX: Configure pinmuxs for user leds control on Bone AnilKumar Ch
2012-09-06 20:58 ` Tony Lindgren
2012-09-07 3:23 ` AnilKumar, Chimata
2012-09-05 11:41 ` [PATCH RESEND v5 3/3] arm/dts: AM33XX: Add D_CAN device tree data AnilKumar Ch
2012-09-05 13:46 ` Marc Kleine-Budde
2012-09-06 8:09 ` AnilKumar, Chimata
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=1346845260-10978-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).