public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: "Andrew F. Davis" <afd@ti.com>
Cc: 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>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 3/3] gpio: tps65086: Add GPO driver for the TPS65086 PMIC
Date: Wed, 27 Jan 2016 07:29:55 +0000	[thread overview]
Message-ID: <20160127072955.GH3368@x1> (raw)
In-Reply-To: <56A784CC.4090902@ti.com>

On Tue, 26 Jan 2016, Andrew F. Davis wrote:

> On 01/26/2016 08:03 AM, Lee Jones wrote:
> >On Mon, 25 Jan 2016, Andrew F. Davis wrote:
> >
> >>Add support for the TPS65086 PMIC GPOs.
> >>
> >>TPS65086 has four configurable GPOs that can be used for several
> >>purposes. These are output only.
> >>
> >>Signed-off-by: Andrew F. Davis <afd@ti.com>
> >>---
> >>  drivers/gpio/Kconfig         |   6 ++
> >>  drivers/gpio/Makefile        |   1 +
> >>  drivers/gpio/gpio-tps65086.c | 144 +++++++++++++++++++++++++++++++++++++++++++
> >>  3 files changed, 151 insertions(+)
> >>  create mode 100644 drivers/gpio/gpio-tps65086.c
> >
> >Is this patch orthogonal to the other two in the set, or do they all
> >need to go in together?
> 
> These can all go in separately, in fact Mark has already taken the regulator
> component from a previous push of this series. It is only the TPS65912
> driver I'm pushing that will need to go all at once due to conflicts with
> the driver it is replacing.

Very well.  MFD patches taken.

Linus should take this through his tree.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2016-01-27  7:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 15:50 [PATCH v6 0/3] Add support for the TI TPS65086 PMIC Andrew F. Davis
2016-01-25 15:50 ` [PATCH v6 1/3] Documentation: tps65086: Add DT bindings for the " Andrew F. Davis
2016-01-26 14:02   ` Lee Jones
2016-01-27  7:28   ` Lee Jones
2016-01-25 15:50 ` [PATCH v6 2/3] mfd: tps65086: Add driver " Andrew F. Davis
2016-01-27  7:29   ` Lee Jones
2016-01-25 15:50 ` [PATCH v6 3/3] gpio: tps65086: Add GPO " Andrew F. Davis
2016-01-26 14:03   ` Lee Jones
2016-01-26 14:38     ` Andrew F. Davis
2016-01-27  7:29       ` Lee Jones [this message]
2016-02-05 14:43   ` Linus Walleij
2016-02-06 16:11     ` Andrew F. Davis

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=20160127072955.GH3368@x1 \
    --to=lee.jones@linaro.org \
    --cc=afd@ti.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gnurou@gmail.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sameo@linux.intel.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