From: Roland Stigge <stigge@antcom.de>
To: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
w.sang@pengutronix.de, srinivas.bakki@nxp.com,
kevin.wells@nxp.com, gregkh@linuxfoundation.org,
netdev@vger.kernel.org, rtc-linux@googlegroups.com,
a.zummo@towertech.it, linux-watchdog@vger.kernel.org,
wim@iguana.be, jonsmirl@gmail.com
Cc: Roland Stigge <stigge@antcom.de>
Subject: [PATCH RESEND v3 0/8] arm: lpc32xx: Device tree support
Date: Sat, 14 Apr 2012 00:49:57 +0200 [thread overview]
Message-ID: <1334357397-21296-1-git-send-email-stigge@antcom.de> (raw)
This is the first series of patches to introduce device tree support for the
LPC32xx SoC. This series includes patches for the various subsystems to support
device tree to be used later by the machine's initialization.
The patches apply to various subsystems:
* staging/iio/adc (1)
* rtc (1)
* net (1) - to be merged via arm-soc, acked by davem
* wdt (1)
* i2c (4)
* arm-soc (i2c related in the former, to be merged via i2c, as suggested by
Arnd Bergmann)
Applies to v3.4-rc2
You can also pull from
git://git.antcom.de/linux-2.6 lpc32xx/dt
I'm CC'ing the various subsystem maintainers and lists who can each see what's
going on and please pick their respective subsystem's changes. - Thanks!
Changes since patch v2:
* net: Use of_property_read_bool()
* net: Fixed breakage with non-DT board (iram and mii options)
Signed-off-by: Roland Stigge <stigge@antcom.de>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
--
Roland Stigge (8):
iio: Add device tree support to LPC32xx ADC
rtc: Add device tree support for LPC32xx
net: Add device tree support to LPC32xx
wdt: Device tree support for pnx4008-wdt
i2c-pnx.c: Fix suspend
i2c-pnx.c: Use resources in platforms
i2c-pnx.c: Remove duplicated i2c.h
i2c: Add device tree support to i2c-pnx.c
Documentation/devicetree/bindings/i2c/pnx.txt | 40 ++
Documentation/devicetree/bindings/net/lpc-eth.txt | 24 +
Documentation/devicetree/bindings/rtc/lpc32xx-rtc.txt | 15
Documentation/devicetree/bindings/staging/iio/adc/lpc32xx-adc.txt | 16
Documentation/devicetree/bindings/watchdog/pnx4008-wdt.txt | 13
arch/arm/mach-lpc32xx/common.c | 75 ++--
arch/arm/mach-lpc32xx/include/mach/i2c.h | 63 ---
arch/arm/mach-pnx4008/i2c.c | 64 ++-
arch/arm/mach-pnx4008/include/mach/i2c.h | 64 ---
drivers/i2c/busses/i2c-pnx.c | 164 +++++++---
drivers/net/ethernet/nxp/lpc_eth.c | 73 ++--
drivers/rtc/rtc-lpc32xx.c | 12
drivers/staging/iio/adc/lpc32xx_adc.c | 10
drivers/watchdog/pnx4008_wdt.c | 10
include/linux/i2c-pnx.h | 10
15 files changed, 512 insertions(+), 268 deletions(-)
reply other threads:[~2012-04-13 22:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1334357397-21296-1-git-send-email-stigge@antcom.de \
--to=stigge@antcom.de \
--cc=a.zummo@towertech.it \
--cc=arm@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonsmirl@gmail.com \
--cc=kevin.wells@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=srinivas.bakki@nxp.com \
--cc=w.sang@pengutronix.de \
--cc=wim@iguana.be \
/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).