From: Lee Jones <lee.jones@linaro.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
Samuel Ortiz <sameo@linux.intel.com>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-pwm@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v8 1/2] mfd: add atmel-hlcdc driver
Date: Tue, 7 Oct 2014 10:59:32 +0100 [thread overview]
Message-ID: <20141007095932.GY25331@lee--X1> (raw)
In-Reply-To: <20141007094727.GA12631@ulmo>
On Tue, 07 Oct 2014, Thierry Reding wrote:
> On Tue, Oct 07, 2014 at 10:44:27AM +0100, Lee Jones wrote:
> > On Mon, 06 Oct 2014, Boris Brezillon wrote:
> >
> > > The HLCDC IP available on some Atmel SoCs (i.e. at91sam9n12, at91sam9x5
> > > family or sama5d3 family) exposes 2 subdevices:
> > > - a display controller (controlled by a DRM driver)
> > > - a PWM chip
> > >
> > > The MFD device provides a regmap and several clocks (those connected
> > > to this hardware block) to its subdevices.
> > >
> > > This way concurrent accesses to the iomem range are handled by the regmap
> > > framework, and each subdevice can safely access HLCDC registers.
> > >
> > > Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> > > Acked-by: Lee Jones <lee.jones@linaro.org>
> > > Tested-by: Anthony Harivel <anthony.harivel@emtrion.de>
> > > Tested-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> > > ---
> > > drivers/mfd/Kconfig | 6 ++
> > > drivers/mfd/Makefile | 1 +
> > > drivers/mfd/atmel-hlcdc.c | 122 ++++++++++++++++++++++++++++++++++++++++
> > > include/linux/mfd/atmel-hlcdc.h | 85 ++++++++++++++++++++++++++++
> > > 4 files changed, 214 insertions(+)
> > > create mode 100644 drivers/mfd/atmel-hlcdc.c
> > > create mode 100644 include/linux/mfd/atmel-hlcdc.h
> >
> > Applied for v3.19.
>
> Will you provide a stable branch that I can pull into the PWM tree?
I hadn't planned on it. What do you need that for?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-10-07 9:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 13:48 [PATCH v8 0/2] mfd: add atmel-hlcdc driver Boris Brezillon
2014-10-06 13:48 ` [PATCH v8 1/2] " Boris Brezillon
2014-10-07 9:44 ` Lee Jones
2014-10-07 9:47 ` Thierry Reding
2014-10-07 9:59 ` Lee Jones [this message]
2014-10-07 10:06 ` Thierry Reding
2014-10-07 10:17 ` Lee Jones
2014-10-07 11:13 ` Thierry Reding
2014-10-07 11:38 ` Lee Jones
2014-10-07 11:41 ` Boris Brezillon
2014-10-07 11:55 ` Thierry Reding
2014-10-07 12:22 ` Lee Jones
2014-10-07 13:16 ` Nicolas Ferre
2014-10-07 13:28 ` Lee Jones
2014-10-07 11:59 ` Lee Jones
2014-10-07 12:00 ` Lee Jones
2014-10-06 13:48 ` [PATCH v8 2/2] mfd: add documentation for atmel-hlcdc DT bindings Boris Brezillon
2014-10-07 9:44 ` Lee Jones
2014-10-06 16:23 ` [PATCH v8 0/2] mfd: add atmel-hlcdc driver Lee Jones
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=20141007095932.GY25331@lee--X1 \
--to=lee.jones@linaro.org \
--cc=airlied@linux.ie \
--cc=boris.brezillon@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.com \
--cc=thierry.reding@gmail.com \
/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).