> Am 23.08.2017 02:29 schrieb Harinath Nampally:
> If rising: use transient OR ff_mt device-dependent like before. But now save
> it in a simple flag,
> whether transient registers are available.
> Ok, is it good idea to add the flag to struct mma_chip_info like below?
> * @mma_scales:
Am 23.08.2017 02:29 schrieb Harinath Nampally:
If rising: use transient OR ff_mt device-dependent like before. But
now save it in a simple flag,
whether transient registers are available.
Ok, is it good idea to add the flag to struct mma_chip_info like below?
* @mma_scales:
If rising: use transient OR ff_mt device-dependent like before. But
now save it in a simple flag,
whether transient registers are available.
Ok, is it good idea to add the flag to struct mma_chip_info like below?
* @mma_scales:scale factors for converting
register v
Thanks. I may have missed something, but I'm concerned about only one
thing:
devices without transient event registers. See my comments below.
Am 20.08.2017 18:06 schrieb Harinath Nampally:
This driver supports multiple devices like mma8653,
mma8652, mma8452, mma8453 and fxls8471. Almost al
This driver supports multiple devices like mma8653,
mma8652, mma8452, mma8453 and fxls8471. Almost all
these devices have more than one event.
Current driver design hardcodes the event specific
information, so only one event can be supported by this
driver at any given time
5 matches
Mail list logo