public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Linus Walleij <linus.walleij@stericsson.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Cc: Philippe LANGLAIS <philippe.langlais@stericsson.com>,
	Rabin Vincent <rabin.vincent@stericsson.com>,
	Jonas Aberg <jonas.aberg@stericsson.com>,
	Lee Jones <lee.jones@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 0/9] ux500/Nomadik GPIO and pins update
Date: Thu, 17 May 2012 17:38:32 -0600	[thread overview]
Message-ID: <20120517233832.E67E43E062C@localhost> (raw)
In-Reply-To: <1335172440-27470-1-git-send-email-linus.walleij@stericsson.com>

On Mon, 23 Apr 2012 11:14:00 +0200, Linus Walleij <linus.walleij@stericsson.com> wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
> 
> This is basically an update and sync of Nomadik and ux500 GPIO
> development.
> 
> If you wonder why I introduce a deviant pin configuration path
> not using the pin config subsystem it is because I want to build
> atop of this work which I know works. It will be switched over
> to pinctrl in later patch sets on top of this.
> 
> This is *almost* orthogonal to other ux500 development, but
> there *might* be conflicts with Lee Jones' Device Tree work,
> so I will try to create a separate orthogonal ux500 GPIO branch
> for this stuff.
> 
> Linus Walleij (4):
>   gpio/nomadik: use typesafe __io_address()
>   plat-nomadik: new sleep mode pincfg macros
>   ARM: ux500: remove a bunch of internal pull-ups
>   ARM: ux500: update pin handling
> 
> Rabin Vincent (5):
>   gpio/nomadik: don't set SLPM to 1 for non-wakeup pins
>   gpio/nomadik: cache [rf]w?imsc
>   gpio/nomadik: fix spurious interrupts with SKE
>   gpio/nomadik: support low EMI mode
>   ARM: ux500: implement pin API

for the whole series:

Acked-by: Grant Likely <grant.likely@secretlab.ca>

g.

> 
>  arch/arm/mach-ux500/Makefile                      |    2 +-
>  arch/arm/mach-ux500/board-mop500-pins.c           |  394 ++++++++++++++++-----
>  arch/arm/mach-ux500/board-mop500.h                |    4 +
>  arch/arm/mach-ux500/pins-db8500.h                 |   72 ++--
>  arch/arm/mach-ux500/pins.c                        |   88 +++++
>  arch/arm/mach-ux500/pins.h                        |   46 +++
>  arch/arm/plat-nomadik/include/plat/gpio-nomadik.h |    1 +
>  arch/arm/plat-nomadik/include/plat/pincfg.h       |   19 +
>  drivers/gpio/gpio-nomadik.c                       |  129 +++++--
>  9 files changed, 591 insertions(+), 164 deletions(-)
>  create mode 100644 arch/arm/mach-ux500/pins.c
>  create mode 100644 arch/arm/mach-ux500/pins.h
> 
> -- 
> 1.7.9.2
> 

-- 
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.

      reply	other threads:[~2012-05-17 23:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23  9:14 [PATCH 0/9] ux500/Nomadik GPIO and pins update Linus Walleij
2012-05-17 23:38 ` Grant Likely [this message]

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=20120517233832.E67E43E062C@localhost \
    --to=grant.likely@secretlab.ca \
    --cc=jonas.aberg@stericsson.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philippe.langlais@stericsson.com \
    --cc=rabin.vincent@stericsson.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