From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] regulator: max8998: Add support for Device Tree
Date: Thu, 27 Jun 2013 10:01:39 +0200 [thread overview]
Message-ID: <20130627080138.GC4576@zurbaran> (raw)
In-Reply-To: <1372077594-17052-1-git-send-email-t.figa@samsung.com>
Hi Tomasz,
On Mon, Jun 24, 2013 at 02:39:51PM +0200, Tomasz Figa wrote:
> This series adds Device Tree support to max8998 MFD driver.
>
> First patch reworks max8998-irq driver to use IRQ domains. Second patch
> prepares platform data structure to ease generating it at runtime from
> data parsed from device tree. Third patch implements Device Tree
> binding and adds necessary documentation.
>
> Tested on Universal C210 board.
>
> Changes since v2:
> - switched to simple domains to retain compatibility with platforms
> that do not support Device Tree
> - removed clocks from DT regulator bindings (will be moved to common
> clock framework in further patch)
> - beautified the code a bit
> Changes since v1:
> - rebased to current for-next of regulator tree
>
> Tomasz Figa (3):
> mfd: Add irq domain support for max8998 interrupts
> regulator: max8998: Use arrays for specifying voltages in platform
> data
> mfd: max8998: Add support for Device Tree
>
> Documentation/devicetree/bindings/mfd/max8998.txt | 108 ++++++++++
> arch/arm/mach-exynos/mach-universal_c210.c | 8 +-
> arch/arm/mach-s5pv210/mach-aquila.c | 8 +-
> arch/arm/mach-s5pv210/mach-goni.c | 8 +-
> drivers/mfd/Kconfig | 1 +
> drivers/mfd/max8998-irq.c | 65 +++---
> drivers/mfd/max8998.c | 75 ++++++-
> drivers/regulator/max8998.c | 239 +++++++++++++++-------
> drivers/rtc/rtc-max8998.c | 14 +-
> include/linux/mfd/max8998-private.h | 7 +-
> include/linux/mfd/max8998.h | 20 +-
> 11 files changed, 421 insertions(+), 132 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mfd/max8998.txt
All 3 patches applied, thanks.
Mark, I added your ACK to patch #2.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2013-06-27 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 12:39 [PATCH v3 0/3] regulator: max8998: Add support for Device Tree Tomasz Figa
2013-06-24 12:39 ` [PATCH v3 1/3] mfd: Add irq domain support for max8998 interrupts Tomasz Figa
2013-06-24 12:39 ` [PATCH v3 2/3] regulator: max8998: Use arrays for specifying voltages in platform data Tomasz Figa
2013-06-24 14:54 ` Mark Brown
2013-06-24 12:39 ` [PATCH v3 3/3] mfd: max8998: Add support for Device Tree Tomasz Figa
2013-06-24 14:54 ` Sachin Kamat
2013-06-25 13:46 ` [PATCH v4 " Tomasz Figa
2013-06-25 14:07 ` Tomasz Figa
2013-06-25 14:08 ` [PATCH RESEND " Tomasz Figa
2013-06-24 15:04 ` [PATCH v3 " Mark Brown
2013-06-27 8:01 ` Samuel Ortiz [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=20130627080138.GC4576@zurbaran \
--to=sameo@linux.intel.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