From: Linus Walleij <linus.walleij@linaro.org>
To: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>
Cc: Mika Westerberg <mika.westerberg@intel.com>,
Alexandre Courbot <gnurou@gmail.com>,
GPIO Subsystem Mailing List <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Denis Turischev <denis.turischev@compulab.co.il>
Subject: Re: [PATCHv5 2/2] gpio: sch: Add support for Intel Quark X1000 SoC
Date: Mon, 12 Jan 2015 00:57:42 +0100 [thread overview]
Message-ID: <CACRpkdaWBuMkLkO_Mh5-a+hCSSnpYj1nW2EL8bFD1_jPF=gL6A@mail.gmail.com> (raw)
In-Reply-To: <1418031490-17716-3-git-send-email-rebecca.swee.fun.chang@intel.com>
On Mon, Dec 8, 2014 at 10:38 AM, Chang Rebecca Swee Fun
<rebecca.swee.fun.chang@intel.com> wrote:
> Intel Quark X1000 provides a total of 16 GPIOs. The GPIOs are split between
> the legacy I/O bridge and the GPIO controller.
>
> GPIO-SCH is the GPIO pins on legacy bridge for Intel Quark SoC.
> Intel Quark X1000 has 2 GPIOs powered by the core power well and 6 from
> the suspend power well.
>
> This piece of work is derived from Dan O'Donovan's initial work for Quark
> X1000 enabling.
>
> Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>
> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
Patch applied.
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-01-11 23:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 9:38 [PATCHv5 0/2] Enable Quark X1000 support in gpio-sch Chang Rebecca Swee Fun
2014-12-08 9:38 ` [PATCHv5 1/2] gpio: sch: Consolidate similar algorithms Chang Rebecca Swee Fun
2015-01-11 23:56 ` Linus Walleij
2015-01-15 9:49 ` Linus Walleij
2015-01-15 10:11 ` Alexandre Courbot
2014-12-08 9:38 ` [PATCHv5 2/2] gpio: sch: Add support for Intel Quark X1000 SoC Chang Rebecca Swee Fun
2015-01-11 23:57 ` Linus Walleij [this message]
2014-12-10 9:01 ` [PATCHv5 0/2] Enable Quark X1000 support in gpio-sch Alexandre Courbot
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='CACRpkdaWBuMkLkO_Mh5-a+hCSSnpYj1nW2EL8bFD1_jPF=gL6A@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=denis.turischev@compulab.co.il \
--cc=gnurou@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@intel.com \
--cc=rebecca.swee.fun.chang@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;
as well as URLs for NNTP newsgroup(s).