public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macqel.be>
To: gerg@snapgear.com
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
	Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH v2 01/22] m68knommu: introduce macros to simplify ColdFire GPIO table initialization
Date: Thu, 26 Apr 2012 16:39:29 +0200	[thread overview]
Message-ID: <20120426143929.GA13126@frolo.macqel> (raw)
In-Reply-To: <1335446091-11177-1-git-send-email-gerg@snapgear.com>

Hello Greg,

On Thu, Apr 26, 2012 at 11:14:51PM +1000, gerg@snapgear.com wrote:
> From: Greg Ungerer <gerg@uclinux.org>
> 
...
>  
> +/*
> + *	Define macros to ease the pain of setting up the GPIO tables. There
> + *	is two cases we need to deal with here, they cover all currently
> + *	available ColdFire GPIO hardware. There is of course minor differences
> + *	in the layout and number of bits in each ColdFire part, but the macros
> + *	take all that in.
> + *
> + *	Firstly is the conventional GPIO registers where we toggle individual
> + *	bits in a register, preserving the other bits in the register. For
> + *	lack of a better term I have called this the slow method.
> + */
> +#define	MCFGPS(mlabel, mbase, mngpio, mpddr, mpodr, mppdr)		    \
...
> +/*
> + *	Secondly is the faster case, where we have set and clear registers
> + *	that allow us to set or clear a bit with a single write, not having
> + *	to worry about preserving other bits.
> + */
> +#define	MCFGPF(mlabel, mbase, mngpio)					    \

That's perfectly clear.

Thanks

Philippe

-- 
Philippe De Muyter +32 2 6101532 Macq SA rue de l'Aeronef 2 B-1140 Bruxelles

      parent reply	other threads:[~2012-04-26 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 13:14 [PATCH v2 01/22] m68knommu: introduce macros to simplify ColdFire GPIO table initialization gerg
2012-04-26 13:29 ` Ezequiel García
2012-04-26 13:48   ` Greg Ungerer
2012-04-26 14:39 ` Philippe De Muyter [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=20120426143929.GA13126@frolo.macqel \
    --to=phdm@macqel.be \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox