linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Amit Kucheria <amit.kucheria@linaro.org>,
	darren.tsao@bitmain.com,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	haitao.suo@bitmain.com
Subject: Re: [PATCH 1/2] arm64: dts: bitmain: Add GPIO support for BM1880 SoC
Date: Tue, 5 Mar 2019 08:55:02 +0100	[thread overview]
Message-ID: <CACRpkdbzhAZUjJYLPnaoOsWzHNXzPGvxYHz0b3fZGd38e_i-dw@mail.gmail.com> (raw)
In-Reply-To: <20190226115022.19022-1-manivannan.sadhasivam@linaro.org>

On Tue, Feb 26, 2019 at 12:50 PM Manivannan Sadhasivam
<manivannan.sadhasivam@linaro.org> wrote:

> Add GPIO support for Bitmain BM1880 SoC based on Designware APB GPIO
> controller IP. IP exposes 3 GPIO controllers with a total of 72 pins.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>

Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij

  parent reply	other threads:[~2019-03-05  7:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 11:50 [PATCH 1/2] arm64: dts: bitmain: Add GPIO support for BM1880 SoC Manivannan Sadhasivam
2019-02-26 11:50 ` [PATCH 2/2] arm64: dts: bitmain: Add GPIO Line names for Sophon Edge board Manivannan Sadhasivam
2019-03-05  7:55   ` Linus Walleij
2019-03-07 17:25   ` Manivannan Sadhasivam
2019-03-05  7:55 ` Linus Walleij [this message]
2019-03-07 17:24 ` [PATCH 1/2] arm64: dts: bitmain: Add GPIO support for BM1880 SoC Manivannan Sadhasivam

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=CACRpkdbzhAZUjJYLPnaoOsWzHNXzPGvxYHz0b3fZGd38e_i-dw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=amit.kucheria@linaro.org \
    --cc=darren.tsao@bitmain.com \
    --cc=devicetree@vger.kernel.org \
    --cc=haitao.suo@bitmain.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.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).