linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: support.opensource@diasemi.com, lee.jones@linaro.org,
	robh+dt@kernel.org, linus.walleij@linaro.org,
	Adam.Thomson.Opensource@diasemi.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@pengutronix.de, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v4 3/3] pinctrl: da9062: add driver support
Date: Wed, 15 Jan 2020 17:29:15 +0100	[thread overview]
Message-ID: <20200115162915.ccudevxvre3v5c3d@pengutronix.de> (raw)
In-Reply-To: <20200108104746.1765-4-m.felsch@pengutronix.de>

Hi Linus,

On 20-01-08 11:47, Marco Felsch wrote:
> The DA9062 is a mfd pmic device which supports 5 GPIOs. The GPIOs can
> be used as input, output or have a special use-case.
> 
> The patch adds the support for the normal input/output use-case.
> 
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>

Is it possible to get this into 5.6?

Regards,
  Marco


  reply	other threads:[~2020-01-15 16:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 10:47 [PATCH v4 0/3] Add DA9062 GPIO support Marco Felsch
2020-01-08 10:47 ` [PATCH v4 1/3] dt-bindings: mfd: da9062: add gpio bindings Marco Felsch
2020-01-13 20:34   ` Linus Walleij
2020-01-17  9:45   ` Lee Jones
2020-01-08 10:47 ` [PATCH v4 2/3] mfd: da9062: add support for the DA9062 GPIOs in the core Marco Felsch
2020-01-17  9:45   ` Lee Jones
2020-01-08 10:47 ` [PATCH v4 3/3] pinctrl: da9062: add driver support Marco Felsch
2020-01-15 16:29   ` Marco Felsch [this message]
2020-01-17  8:16     ` Linus Walleij
2020-01-17  8:45       ` Marco Felsch
2020-01-17  9:57   ` Adam Thomson
2020-02-18 11:07     ` Marco Felsch
2020-02-19 16:17       ` Linus Walleij
2020-01-17  8:46 ` [PATCH v4 0/3] Add DA9062 GPIO support Marco Felsch

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=20200115162915.ccudevxvre3v5c3d@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=Adam.Thomson.Opensource@diasemi.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=support.opensource@diasemi.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).