From: antoine.tenart@free-electrons.com (Antoine Tenart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 03/10] reset: berlin: convert to a platform driver
Date: Tue, 12 May 2015 16:43:13 +0200 [thread overview]
Message-ID: <20150512144313.GD32171@kwain> (raw)
In-Reply-To: <20150310095713.GD23469@kwain>
On Tue, Mar 10, 2015 at 10:57:13AM +0100, Antoine Tenart wrote:
> On Mon, Mar 09, 2015 at 11:16:26AM +0100, Philipp Zabel wrote:
> >
> > Am Freitag, den 06.03.2015, 16:05 +0100 schrieb Antoine Tenart:
> > > The Berlin reset controller was introduced without being a platform
> > > driver because of a needed DT rework: the node describing the reset
> > > controller also describes the pinctrl and clk controllers...
> > >
> > > The DT issue being solved thanks to the addition of the Berlin
> > > controller mfd driver, it is now possible to convert the Berlin reset
> > > driver to a plaftorm driver.
> > >
> > > Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com>
> >
> > Looks good to me. Do you want to merge this together with the rest of
> > the series, or should I queue the reset patch?
>
> I think we better wait for the simple-mfd patch to make it to ARM SoC
> first.
simple-mfd just got pulled into next/drivers.
> Once this is done, you can queue the reset patch (unless Sebastian wants
> to take it alongside the series).
Antoine
--
Antoine T?nart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-12 14:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 15:05 [PATCH v2 00/10] ARM: berlin: refactor chip and system controllers Antoine Tenart
2015-03-06 15:05 ` [PATCH v2 01/10] Documentation: bindings: update the Berlin controllers documentation Antoine Tenart
2015-03-06 15:05 ` [PATCH v2 02/10] ARM: berlin: select MFD_SYSCON by default Antoine Tenart
2015-03-06 15:05 ` [PATCH v2 03/10] reset: berlin: convert to a platform driver Antoine Tenart
2015-03-09 10:16 ` Philipp Zabel
2015-03-10 9:57 ` Antoine Tenart
2015-03-25 8:26 ` Linus Walleij
2015-05-12 14:43 ` Antoine Tenart [this message]
2015-05-13 8:38 ` Philipp Zabel
2015-05-15 9:14 ` Sebastian Hesselbarth
2015-03-06 15:05 ` [PATCH v2 04/10] Documentation: bindings: move the Berlin reset documentation Antoine Tenart
2015-03-09 10:16 ` Philipp Zabel
2015-03-06 15:05 ` [PATCH v2 05/10] pinctrl: berlin: use the regmap provided by syscon Antoine Tenart
2015-04-28 11:30 ` Sebastian Hesselbarth
2015-05-06 14:28 ` Linus Walleij
2015-03-06 15:05 ` [PATCH v2 06/10] pinctrl: berlin: use proper compatibles Antoine Tenart
2015-06-10 7:13 ` Linus Walleij
2015-06-12 9:05 ` Antoine Tenart
2015-06-12 9:24 ` Sebastian Hesselbarth
2015-03-06 15:05 ` [PATCH v2 07/10] Documentation: bindings: move the Berlin pinctrl documentation Antoine Tenart
2015-06-10 7:14 ` Linus Walleij
2015-03-06 15:05 ` [PATCH v2 08/10] ARM: berlin: rework chip and system controller nodes for BG2 Antoine Tenart
2015-03-06 15:05 ` [PATCH v2 09/10] ARM: berlin: rework chip and system controller nodes for BG2CD Antoine Tenart
2015-03-06 15:05 ` [PATCH v2 10/10] ARM: berlin: rework chip and system controller nodes for BG2Q Antoine Tenart
2015-03-09 17:13 ` [PATCH v2 00/10] ARM: berlin: refactor chip and system controllers Linus Walleij
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=20150512144313.GD32171@kwain \
--to=antoine.tenart@free-electrons.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;
as well as URLs for NNTP newsgroup(s).