aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorPaulo Miguel Almeida <[email protected]>2022-02-26 11:40:33 +1300
committerGreg Kroah-Hartman <[email protected]>2022-03-01 22:31:21 +0100
commit2d19e698e7f1c2453340b515f18adc779c42b11e (patch)
tree38a3b00b7b5e728217b30c358b2f00dad1a8f244 /tools/perf/scripts/python
parented01d1b9bca21b186aa05b5beab4df88d42cf335 (diff)
staging: pi433: remove rf69_get_flag function resolving enum conflict
The reason why rf69_get_flag() existed was to provide a high-level way to obtain values out of 1 (of 2) flags registers using bit masking. The idea was to map the possible flag values found in the data sheet like shown in page 70 of the RFM69HCW datasheet. However, due to the fact that enums values in C must be unique, there was a naming conflict on 'fifo_not_empty' which is used by the tx_start_condition enum. So the author decided to create a 'fifo_empty' one which would negate the value that comes from the flag register as the solution to that conflict (which is very confusing). this patch removes rf69_get_flag function which subsequently solves the enum redeclaration problem so kernel developers can follow the data sheet more easily. Reviewed-by: Dan Carpenter <[email protected]> Signed-off-by: Paulo Miguel Almeida <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions