Files
linux/drivers/rtc
Nathan Chancellor 23599f816c rtc: omap: Use define directive for PIN_CONFIG_ACTIVE_HIGH
commit c50156526a upstream.

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

drivers/rtc/rtc-omap.c:574:21: warning: implicit conversion from
enumeration type 'enum rtc_pin_config_param' to different enumeration
type 'enum pin_config_param' [-Wenum-conversion]
        {"ti,active-high", PIN_CONFIG_ACTIVE_HIGH, 0},
        ~                  ^~~~~~~~~~~~~~~~~~~~~~
drivers/rtc/rtc-omap.c:579:12: warning: implicit conversion from
enumeration type 'enum rtc_pin_config_param' to different enumeration
type 'enum pin_config_param' [-Wenum-conversion]
        PCONFDUMP(PIN_CONFIG_ACTIVE_HIGH, "input active high", NULL, false),
        ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./include/linux/pinctrl/pinconf-generic.h:163:11: note: expanded from
macro 'PCONFDUMP'
        .param = a, .display = b, .format = c, .has_arg = d     \
                 ^
2 warnings generated.

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/144
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2020-04-17 10:48:51 +02:00
..
2018-07-26 15:08:53 +02:00
2018-05-21 22:34:38 +02:00
2018-03-27 10:45:05 +02:00
2018-05-17 22:23:14 +02:00
2018-03-17 14:20:56 +01:00
2020-02-14 16:33:24 -05:00
2018-05-03 22:08:00 +02:00
2018-05-03 22:08:00 +02:00
2018-05-03 22:08:00 +02:00
2017-09-01 01:10:11 +02:00
2016-05-20 12:33:51 +02:00
2018-03-17 14:20:50 +01:00
2018-05-03 22:08:00 +02:00
2018-05-18 09:38:22 +02:00
2018-03-17 14:20:56 +01:00
2018-05-03 22:08:00 +02:00
2018-05-22 09:47:17 +02:00
2018-05-03 22:08:00 +02:00
2017-08-22 12:05:21 +02:00
2018-06-07 20:11:08 +02:00
2016-05-20 12:33:51 +02:00
2017-09-05 09:55:02 +02:00
2018-05-17 22:43:22 +02:00
2013-04-19 13:51:25 +02:00
2018-05-23 09:26:19 +02:00
2018-05-03 22:08:00 +02:00
2018-07-12 20:16:10 +02:00
2018-05-17 22:37:11 +02:00
2018-05-17 22:54:21 +02:00
2016-05-20 12:33:51 +02:00
2018-05-03 22:08:00 +02:00