From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 0/3] ARM: dts: add openpandora device support
Date: Mon, 16 Mar 2015 15:04:29 -0700 [thread overview]
Message-ID: <20150316220429.GM12397@atomide.com> (raw)
In-Reply-To: <1425072399-23152-1-git-send-email-marek@goldelico.com>
* Marek Belisko <marek@goldelico•com> [150227 13:30]:
> changes from v2:
> - fix missing PIN_INPUT for penirq node
> - added Reviewed-by and Tested-by
>
> changes from v1:
> - add new boards to makefile in patch 2,3 (don't add them
> in separate commit together), fix gpmc issues (reported by Tony Lindgren)
>
> - fix various issues reported by Grazvydas Ignotas
> (drop internal pullups from pinmux as external are in place,
> fix gpio buttons active state ...)
>
> This series of patches adds initial device tree support for the
> OpenPandora. The most important parts are working (display, keyboard,
> touch, charging, fuel gauge, musb port, sd/mmc ports, leds, buttons).
> Not yet supported are: usb host port, nubs, wifi, bluetooth, audio.
>
> First patch add common dtsi file which is then used in 600mhz and 1ghz
> variants of openpandora which support is added in patches 2 and 3.
>
> H. Nikolaus Schaller (3):
> ARM: dts: omap3-pandora: add common device tree
> ARM: dts: omap3-pandora: add OMAP3530 600 MHz version
> ARM: dts: omap3-pandora: add DM3730 1 GHz version
Thanks everybody for doing this, applying into omap-for-v4.1/dt.
Regards,
Tony
prev parent reply other threads:[~2015-03-16 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 21:26 [PATCH v3 0/3] ARM: dts: add openpandora device support Marek Belisko
2015-02-27 21:26 ` [PATCH v3 1/3] ARM: dts: omap3-pandora: add common device tree Marek Belisko
2015-02-27 21:26 ` [PATCH v3 2/3] ARM: dts: omap3-pandora: add OMAP3530 600 MHz version Marek Belisko
2015-02-27 21:26 ` [PATCH v3 3/3] ARM: dts: omap3-pandora: add DM3730 1 GHz version Marek Belisko
2015-03-16 22:04 ` Tony Lindgren [this message]
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=20150316220429.GM12397@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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