Commit 7c9ab035 authored by srinivas pandruvada's avatar srinivas pandruvada Committed by Jonathan Cameron

iio: core: Add hysteresis in channel spec

Added hysteresis to the list of channel info enumeration, shared
/separate bit defines and to postfix channel info strings.
Signed-off-by: default avatarsrinivas pandruvada <srinivas.pandruvada@intel.com>
Signed-off-by: default avatarJonathan Cameron <jic23@kernel.org>
parent 107f04bb
...@@ -99,6 +99,7 @@ static const char * const iio_chan_info_postfix[] = { ...@@ -99,6 +99,7 @@ static const char * const iio_chan_info_postfix[] = {
[IIO_CHAN_INFO_FREQUENCY] = "frequency", [IIO_CHAN_INFO_FREQUENCY] = "frequency",
[IIO_CHAN_INFO_PHASE] = "phase", [IIO_CHAN_INFO_PHASE] = "phase",
[IIO_CHAN_INFO_HARDWAREGAIN] = "hardwaregain", [IIO_CHAN_INFO_HARDWAREGAIN] = "hardwaregain",
[IIO_CHAN_INFO_HYSTERESIS] = "hysteresis",
}; };
const struct iio_chan_spec const struct iio_chan_spec
......
...@@ -35,6 +35,7 @@ enum iio_chan_info_enum { ...@@ -35,6 +35,7 @@ enum iio_chan_info_enum {
IIO_CHAN_INFO_FREQUENCY, IIO_CHAN_INFO_FREQUENCY,
IIO_CHAN_INFO_PHASE, IIO_CHAN_INFO_PHASE,
IIO_CHAN_INFO_HARDWAREGAIN, IIO_CHAN_INFO_HARDWAREGAIN,
IIO_CHAN_INFO_HYSTERESIS,
}; };
#define IIO_CHAN_INFO_SHARED_BIT(type) BIT(type*2) #define IIO_CHAN_INFO_SHARED_BIT(type) BIT(type*2)
...@@ -100,6 +101,10 @@ enum iio_chan_info_enum { ...@@ -100,6 +101,10 @@ enum iio_chan_info_enum {
IIO_CHAN_INFO_SEPARATE_BIT(IIO_CHAN_INFO_HARDWAREGAIN) IIO_CHAN_INFO_SEPARATE_BIT(IIO_CHAN_INFO_HARDWAREGAIN)
#define IIO_CHAN_INFO_HARDWAREGAIN_SHARED_BIT \ #define IIO_CHAN_INFO_HARDWAREGAIN_SHARED_BIT \
IIO_CHAN_INFO_SHARED_BIT(IIO_CHAN_INFO_HARDWAREGAIN) IIO_CHAN_INFO_SHARED_BIT(IIO_CHAN_INFO_HARDWAREGAIN)
#define IIO_CHAN_INFO_HYSTERESIS_SEPARATE_BIT \
IIO_CHAN_INFO_SEPARATE_BIT(IIO_CHAN_INFO_HYSTERESIS)
#define IIO_CHAN_INFO_HYSTERESIS_SHARED_BIT \
IIO_CHAN_INFO_SHARED_BIT(IIO_CHAN_INFO_HYSTERESIS)
enum iio_endian { enum iio_endian {
IIO_CPU, IIO_CPU,
......
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