All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: sfking@fdwdc.com
Cc: linux-kernel@vger.kernel.org, uclinux-dev@uclinux.org,
	linux-m68k@vger.kernel.org
Subject: Re: [PATCH 00/13] revised Coldfire generic GPIO (mk68nommu)
Date: Wed, 24 Jun 2009 15:57:35 +1000	[thread overview]
Message-ID: <4A41C04F.6050909@snapgear.com> (raw)
In-Reply-To: <1245460272-4329-1-git-send-email-sfking@fdwdc.com>

Hi Steven,

sfking@fdwdc.com wrote:
> Revised implementation of generic gpio for the Freescale Coldfire family of
> processors (m68knommu).   It uses gpiolib and provides both fast inline
> operations when the gpio is a compile time constant and slower outline
> operations dispatched via gpiolib when the gpio is a variable. 
> 
> There are also hooks for implementing pin multiplexing but that part isn't
> finished yet.
> 
> 
> The major difference with the previous version is the move to a per-platform
> setup code as suggested by Greg Ungerer <gerg@snapgear.com>.
> 
> Additionally, it fixes the definition of the TIMER gpio pins in the 5271
> (thanks to Richard Retanubun <RichardRetanubun@ruggedcom.com>).

This looks pretty good to me.
Do you want me to apply the the m68knommu git tree?
(Ideally I'll push it to Linus in the 2.6.32 merge window).

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

  parent reply	other threads:[~2009-06-24  5:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20  1:10 [PATCH 00/13] revised Coldfire generic GPIO (mk68nommu) sfking
2009-06-20  1:10 ` sfking
2009-06-20  1:11 ` [PATCH 01/13] core generic GPIO support for Freescale Coldfire processors sfking
2009-06-20  1:11   ` sfking
2009-06-20  1:11   ` [PATCH 02/13] generic GPIO support for the Freescale Coldfire 5206 sfking
2009-06-20  1:11     ` sfking
2009-06-20  1:11     ` [PATCH 03/13] generic GPIO support for the Freescale Coldire 5206e sfking
2009-06-20  1:11       ` sfking
2009-06-20  1:11       ` [PATCH 04/13] generic GPIO support for the Freescale Coldfire 520x sfking
2009-06-20  1:11         ` sfking
2009-06-20  1:11         ` [PATCH 05/13] generic GPIO support for the Freescale Coldfire 523x sfking
2009-06-20  1:11           ` sfking
2009-06-20  1:11           ` [PATCH 06/13] generic GPIO support for the Freescale Coldfire 5249 sfking
2009-06-20  1:11             ` sfking
2009-06-20  1:11             ` [PATCH 07/13] generic GPIO support for the Freescale Coldfire 527x sfking
2009-06-20  1:11               ` sfking
2009-06-20  1:11               ` [PATCH 08/13] generic GPIO support for the Freescale Coldfire 5272 sfking
2009-06-20  1:11                 ` sfking
2009-06-20  1:11                 ` [PATCH 09/13] generic GPIO support for the Freescale Coldfire 528x sfking
2009-06-20  1:11                   ` sfking
2009-06-20  1:11                   ` [PATCH 10/13] generic GPIO support for the Freescale Coldfire 5307 sfking
2009-06-20  1:11                     ` sfking
2009-06-20  1:11                     ` [PATCH 11/13] generic GPIO support for the Freescale Coldfire 532x sfking
2009-06-20  1:11                       ` sfking
2009-06-20  1:11                       ` [PATCH 12/13] generic GPIO support for the Freescale Coldfire 5407 sfking
2009-06-20  1:11                         ` sfking
2009-06-20  1:11                         ` [PATCH 13/13] generic GPIO support misc files sfking
2009-06-20  1:11                           ` sfking
2009-06-24  5:57 ` Greg Ungerer [this message]
2009-06-24 19:09   ` [PATCH 00/13] revised Coldfire generic GPIO (mk68nommu) Steven King
2009-07-02  4:36     ` Greg Ungerer

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=4A41C04F.6050909@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=sfking@fdwdc.com \
    --cc=uclinux-dev@uclinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.