devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Hogan <james.hogan@imgtec.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Grant Likely <grant.likely@linaro.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Rob Landley <rob@landley.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH v3 1/4] pinctrl-tz1090: add TZ1090 pinctrl driver
Date: Mon, 24 Jun 2013 16:38:57 +0100	[thread overview]
Message-ID: <51C86811.2010400@imgtec.com> (raw)
In-Reply-To: <CACRpkdbMfWLf17Aty-a80_+gETTvLgO3wEWVFsnhuLypy61VBw@mail.gmail.com>

On 24/06/13 16:04, Linus Walleij wrote:
> On Thu, Jun 20, 2013 at 11:26 AM, James Hogan <james.hogan@imgtec.com> wrote:
> 
>> Add a pin control driver for the main pins on the TZ1090 SoC. This
>> doesn't include the low-power pins as they're controlled separately via
>> the Powerdown Controller (PDC) registers.
>>
>> Signed-off-by: James Hogan <james.hogan@imgtec.com>
>> Cc: Grant Likely <grant.likely@linaro.org>
>> Cc: Rob Herring <rob.herring@calxeda.com>
>> Cc: Rob Landley <rob@landley.net>
>> Cc: Linus Walleij <linus.walleij@linaro.org>
>> Cc: linux-doc@vger.kernel.org
>> Cc: devicetree-discuss@lists.ozlabs.org
>> ---
>> Changes in v3:
>>  - separated from irq-imgpdc and removed arch/metag changes to allow
>>    these patches to go upstream separately via the pinctrl[/gpio] trees
>>    (particularly the pinctrl drivers depend on the new pinconf DT
>>    bindings).
>>  - some s/unsigned/unsigned int/.
>>  - some s/unsigned int/bool/ and use of BIT().
>>  - pinctrl-tz1090*: switch to generic pinconfig DT bindings and
>>    pinconf_generic_dump_config.
>>  - pinctrl-tz1090*: use tz1090, prefix for pins and function in DT
>>    bindings.
>>  - pinctrl-tz1090*: make internal functions static.
>>  - pinctrl-tz1090*: move initcall from postcore to arch.
> 
> Thanks James, patch applied.
> 
> Also thanks for helping out in getting the generic pinconf
> in place for some three different drivers for this merge window,
> this was very good for pinctrl at large.

Thanks Linus, and no problem!

Cheers
James


  reply	other threads:[~2013-06-24 15:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20  9:26 [PATCH v3 0/4] Add TZ1090 pinctrl/gpio drivers James Hogan
     [not found] ` <1371720391-21825-1-git-send-email-james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2013-06-20  9:26   ` [PATCH v3 1/4] pinctrl-tz1090: add TZ1090 pinctrl driver James Hogan
2013-06-24 15:04     ` Linus Walleij
2013-06-24 15:38       ` James Hogan [this message]
2013-06-20  9:26 ` [PATCH v3 2/4] gpio-tz1090: add TZ1090 gpio driver James Hogan
2013-06-24 13:34   ` Grant Likely
2013-06-24 14:48     ` James Hogan
2013-06-24 15:36       ` James Hogan
2013-06-20  9:26 ` [PATCH v3 3/4] pinctrl-tz1090-pdc: add TZ1090 PDC pinctrl driver James Hogan
2013-06-24 15:08   ` Linus Walleij
2013-06-20  9:26 ` [PATCH v3 4/4] gpio-tz1090-pdc: add TZ1090 PDC gpio driver James Hogan
2013-06-24 15:11   ` Linus Walleij

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=51C86811.2010400@imgtec.com \
    --to=james.hogan@imgtec.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    /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).