On 7/23/20 8:01 AM, Roy Im wrote: > diff --git a/drivers/input/misc/Kconfig b/drivers/input/misc/Kconfig > index 362e8a0..06dc5a3 100644 > --- a/drivers/input/misc/Kconfig > +++ b/drivers/input/misc/Kconfig > @@ -869,4 +869,17 @@ config INPUT_STPMIC1_ONKEY > To compile this driver as a module, choose M here: the > module will be called stpmic1_onkey. > > +config INPUT_DA7280_HAPTICS > + tristate "Dialog Semiconductor DA7280 haptics support" > + depends on INPUT && I2C > + select INPUT_FF_MEMLESS > + select REGMAP_I2C > + help > + Say Y to enable support for the Dialog DA7280 haptics driver. > + The haptics can be controlled by I2C communication, > + or by PWM input, or by GPI. Is that GPIO. ? Can the haptics be controlled only by PWM or only by GPI(O)? Just curious: why is I2C required to build the driver if a user is only controlling the device by PWM or GPI? > + > + To compile this driver as a module, choose M here: the > + module will be called da7280. > + > endif thanks. -- ~Randy
