Input: docs - use PROPERTY_ENTRY_U32() directly
authorAndy Shevchenko <andriy.shevchenko@linux.intel.com>
Mon, 22 Jan 2018 17:27:22 +0000 (09:27 -0800)
committerDmitry Torokhov <dmitry.torokhov@gmail.com>
Tue, 23 Jan 2018 00:27:58 +0000 (16:27 -0800)
Instead of using PROPERTY_ENTRY_INTEGER() with explicitly supplied type,
use PROPERTY_ENTRY_U32() dedicated macro.

It will help modify internals of built-in device properties API.

No functional change intended.

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Documentation/input/devices/rotary-encoder.rst

index b07b20a295ac5c220a55f0ba6def574d6c9ea5af..810ae02bdaa0deda0da2ef20f715c697a06d1e41 100644 (file)
@@ -108,9 +108,9 @@ example below:
        };
 
        static const struct property_entry rotary_encoder_properties[] __initconst = {
-               PROPERTY_ENTRY_INTEGER("rotary-encoder,steps-per-period", u32, 24),
-               PROPERTY_ENTRY_INTEGER("linux,axis",                      u32, ABS_X),
-               PROPERTY_ENTRY_INTEGER("rotary-encoder,relative_axis",    u32, 0),
+               PROPERTY_ENTRY_U32("rotary-encoder,steps-per-period", 24),
+               PROPERTY_ENTRY_U32("linux,axis",                      ABS_X),
+               PROPERTY_ENTRY_U32("rotary-encoder,relative_axis",    0),
                { },
        };