[GIT PULL] LPC18xx DTS changes for v4.7

[Olof Johansson]

On Mon, Apr 04, 2016 at 10:53:05PM +0200, Joachim Eastwood wrote:
> Hi arm-soc team,
> 
> Please consider pulling these DTS changes for the NXP LPC18xx
> platform into arm-soc/dt for Linux 4.7.
> 
> These patches add support for the RTC and analog peripherals (ADC/DAC)
> found on LPC18xx SoCs. It also adds a CREG clock controller which is
> needed to enable the 1 kHz clock for the RTC. Note that the IIO drivers
> and dt doc hasn't yet hit next but they are queued in the Greg's tree
> and should hit next anytime now.
> 
> There are also a few board updates to enable the analog peripherals
> on the two LPC435x development boards.
> 
> A big part of DT changes is fixes for the warnings generated by the
> new dtc. These fixes also touches a file shared with other Cortex-M
> platforms and carries the a ack from the author.
> 
> 
> The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
> 
>   Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/manabian/linux-lpc.git tags/lpc18xx_dts_for_4.7
> 
> for you to fetch changes up to 1db7f6201dfce1740e41f87c81389cc2e9c73e99:
> 
>   dt-bindings: phy-lpc18xx-usb-otg: remove unit address from binding (2016-04-04 16:13:32 +0200)
> 
> ----------------------------------------------------------------
> Device Tree additions for LPC18xx platform
>  - CREG clock controller
>  - Real Time Clock (RTC)
>  - Analog peripherals (ADC/DAC)
>  - Warning fixes for the new dtc compiler
> 
> With the CREG clock controller in place it is now possible
> to enable the internal RTC on LPC18xx/43xx platforms. The
> analog peripherals (ADC/DAC) has also been added here and
> enabled on both the EA4357 dev kit and Hitex eval board.
> 
> In addition to the new entries there are a fixes for the
> DT warnings generated by the new dtc.

Merged, but I noticed that you lack signatures on your PGP key. Where are
you located geographically? Any chance you can get some local developers to
sign it, or get it signed if you've got a chance to visit a conference at
some point?


Thanks,

-Olof