Commit 1f60652d authored by Nathan Chancellor's avatar Nathan Chancellor Committed by Linus Walleij

pinctrl: max77620: Use define directive for max77620_pinconf_param values

Clang warns when one enumerated type is implicitly converted to another:

drivers/pinctrl/pinctrl-max77620.c:56:12: warning: implicit conversion
from enumeration type 'enum max77620_pinconf_param' to different
enumeration type 'enum pin_config_param' [-Wenum-conversion]
                .param = MAX77620_ACTIVE_FPS_SOURCE,
                         ^~~~~~~~~~~~~~~~~~~~~~~~~~

It is expected that pinctrl drivers can extend pin_config_param because
of the gap between PIN_CONFIG_END and PIN_CONFIG_MAX so this conversion
isn't an issue. Most drivers that take advantage of this define the
PIN_CONFIG variables as constants, rather than enumerated values. Do the
same thing here so that Clang no longer warns.

Link: https://github.com/ClangBuiltLinux/linux/issues/139Signed-off-by: default avatarNathan Chancellor <natechancellor@gmail.com>
Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
parent 149a9604
...@@ -34,14 +34,12 @@ enum max77620_pin_ppdrv { ...@@ -34,14 +34,12 @@ enum max77620_pin_ppdrv {
MAX77620_PIN_PP_DRV, MAX77620_PIN_PP_DRV,
}; };
enum max77620_pinconf_param { #define MAX77620_ACTIVE_FPS_SOURCE (PIN_CONFIG_END + 1)
MAX77620_ACTIVE_FPS_SOURCE = PIN_CONFIG_END + 1, #define MAX77620_ACTIVE_FPS_POWER_ON_SLOTS (PIN_CONFIG_END + 2)
MAX77620_ACTIVE_FPS_POWER_ON_SLOTS, #define MAX77620_ACTIVE_FPS_POWER_DOWN_SLOTS (PIN_CONFIG_END + 3)
MAX77620_ACTIVE_FPS_POWER_DOWN_SLOTS, #define MAX77620_SUSPEND_FPS_SOURCE (PIN_CONFIG_END + 4)
MAX77620_SUSPEND_FPS_SOURCE, #define MAX77620_SUSPEND_FPS_POWER_ON_SLOTS (PIN_CONFIG_END + 5)
MAX77620_SUSPEND_FPS_POWER_ON_SLOTS, #define MAX77620_SUSPEND_FPS_POWER_DOWN_SLOTS (PIN_CONFIG_END + 6)
MAX77620_SUSPEND_FPS_POWER_DOWN_SLOTS,
};
struct max77620_pin_function { struct max77620_pin_function {
const char *name; const char *name;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment