linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: linuxppc-dev@ozlabs.org, Geert.Uytterhoeven@sonycom.com,
	michael@ellerman.id.au, paulus@samba.org,
	galak@kernel.crashing.org, benh@kernel.crashing.org
Cc: Timur Tabi <timur@freescale.com>
Subject: [PATCH] powerpc: add setclrbits macros
Date: Thu, 16 Aug 2007 17:43:19 -0500	[thread overview]
Message-ID: <11873041991712-git-send-email-timur@freescale.com> (raw)

This patch adds the setclrbits_xxx() macros, which are used to set and clear
multiple bits in a single read-modify-write operation.  Specify the bits
to set in the 'set' parameter and the bits to clear in the 'clear' parameter.
These macros can also be used to set a multiple-bit bit pattern using a mask,
by specifying the mask in the 'clear' parameter and the new bit pattern in the
'set' parameter.  There are big-endian and little-endian versions for 8, 16,
32, and 64 bits.

Signed-off-by: Timur Tabi <timur@freescale.com>
---

Changed the macros from setmaskedbits_xxx to setclrbits_xxx and added a comment
indicating the expanded functionality.

 include/asm-powerpc/io.h |   27 +++++++++++++++++++++++++++
 1 files changed, 27 insertions(+), 0 deletions(-)

diff --git a/include/asm-powerpc/io.h b/include/asm-powerpc/io.h
index bb8d965..58c8b96 100644
--- a/include/asm-powerpc/io.h
+++ b/include/asm-powerpc/io.h
@@ -734,6 +734,33 @@ static inline void * bus_to_virt(unsigned long address)
 #define setbits16(_addr, _v) out_be16((_addr), in_be16(_addr) |  (_v))
 #define clrbits16(_addr, _v) out_be16((_addr), in_be16(_addr) & ~(_v))
 
+/* Set and clear bits in one shot.  These macros can be used to clear and
+ * set multiple bits in a register using a single read-modify-write.  These
+ * macros can also be used to set a multiple-bit bit pattern using a mask,
+ * by specifying the mask in the 'clear' parameter and the new bit pattern
+ * in the 'set' parameter.
+ */
+
+#ifdef __powerpc64__
+#define setclrbits_be64(addr, set, clear) \
+	out_be64((addr), (in_be64(addr) & ~(clear)) | (set))
+#define setclrbits_le64(addr, set, clear) \
+	out_le64((addr), (in_le64(addr) & ~(clear)) | (set))
+#endif
+
+#define setclrbits_be32(addr, set, clear) \
+	out_be32((addr), (in_be32(addr) & ~(clear)) | (set))
+#define setclrbits_be16(addr, set, clear) \
+	out_be16((addr), (in_be16(addr) & ~(clear)) | (set))
+
+#define setclrbits_le32(addr, set, clear) \
+	out_le32((addr), (in_le32(addr) & ~(clear)) | (set))
+#define setclrbits_le16(addr, set, clear) \
+	out_le16((addr), (in_le16(addr) & ~(clear)) | (set))
+
+#define setclrbits_8(addr, set, clear) \
+	out_8((addr), (in_8(addr) & ~(clear)) | (set))
+
 #endif /* __KERNEL__ */
 
 #endif /* _ASM_POWERPC_IO_H */
-- 
1.5.2.4

             reply	other threads:[~2007-08-16 22:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 22:43 Timur Tabi [this message]
2007-08-17  6:44 ` [PATCH] powerpc: add setclrbits macros Geert Uytterhoeven
2007-08-17 16:03   ` Timur Tabi

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=11873041991712-git-send-email-timur@freescale.com \
    --to=timur@freescale.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=benh@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).