[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1467821977-11777-1-git-send-email-jakub.kicinski@netronome.com>
Date: Wed, 6 Jul 2016 17:19:35 +0100
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: kvalo@...eaurora.org, linux-wireless@...r.kernel.org
Cc: netdev@...r.kernel.org, hannes@...essinduktion.org, nbd@....name,
linux-kernel@...r.kernel.org,
Jakub Kicinski <jakub.kicinski@...ronome.com>
Subject: [PATCHv5 wl-drv-next 0/2] register-field manipulation macros
Hi!
I've added few lines about the compilation problems in
the commit message of patch 1. I would prefer the mass
rename of macros in mt7601u not to be part of this series
so patch 2 is left as it was and I'll follow up once this
is accepted.
== v4 blurb
This set moves to a global header file macros which I find
very useful and worth popularising. The basic problem is
that since C bitfields are not very dependable accessing
subfields of registers becomes slightly inconvenient.
It is nice to have the necessary mask and shift operations
wrapped in a macro. It is also nice to have that macro
compute the shift amount based on the mask automatically.
My implementation follows what Felix Fietkau has done in
mt76. Hannes Frederic Sowa suggested more use of standard
Linux/GCC functions. Since the RFC I've also added a
compile-time check to validate that the value passed to
setters fits in the mask.
I attempted the use of static inlines instead of macros
but it makes GCC < 6.0 barf at the BUILD_BUG_ON()s.
I also noticed that forcing arguments to be u32 for inlines
makes the compiler use 32bit arithmetic where it could
get away with 64bit before (on 64bit machines, obviously).
That's a potential performance concern but probably not
a very practical one today. Apart from looking "cleaner"
static inlines would have the advantage that we could #undef
the auxiliary macros at the end of the header.
v3:
Build bot caught a build failure with -Os set. AFAICT gcc
did not handle temporary variable I put in the macro
expression too well. I work around that by defining
__BUILD_BUG_ON_NOT_POWER_OF_2 and using it instead of
BUILD_BUG_ON(!tmp || is_power_of_2(tmp)).
Please review and advise on improvements.
If accepted I think would be best to push this through
Kalle's tree, since the only existing user is in
drivers/net/wireless/.
v4:
- add documentation in the header.
v3:
- don't use variables in statement expressions;
- use __BUILD_BUG_ON_NOT_POWER_OF_2.
v2:
- change Felix's email address.
Jakub Kicinski (2):
add basic register-field manipulation macros
mt7601u: use linux/bitfield.h
drivers/net/wireless/mediatek/mt7601u/dma.h | 2 -
drivers/net/wireless/mediatek/mt7601u/mt7601u.h | 5 +-
drivers/net/wireless/mediatek/mt7601u/util.h | 77 -----------------
include/linux/bitfield.h | 109 ++++++++++++++++++++++++
include/linux/bug.h | 3 +
5 files changed, 116 insertions(+), 80 deletions(-)
delete mode 100644 drivers/net/wireless/mediatek/mt7601u/util.h
create mode 100644 include/linux/bitfield.h
--
1.9.1
Powered by blists - more mailing lists