[PATCH 1/6] iio: sysfs-bus-iio typo

[PATCH 1/6] iio: sysfs-bus-iio typo

[Peter Meerwald]

Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>

---
 Documentation/ABI/testing/sysfs-bus-iio |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
index 05449c6..a3774a7 100644
--- a/Documentation/ABI/testing/sysfs-bus-iio
+++ b/Documentation/ABI/testing/sysfs-bus-iio
@@ -122,7 +122,7 @@ Description:
 		If an axis is specified it generally means that the temperature
 		sensor is associated with one part of a compound device (e.g.
 		a gyroscope axis). Units after application of scale and offset
-		are milli degrees Celsuis.
+		are milli degrees Celsius.
 
 What:		/sys/bus/iio/devices/iio:deviceX/in_tempX_input
 KernelVersion:	2.6.38
-- 
1.7.9.5

[PATCH 2/6] iio: cleanup sysfs-bus-iio-light-lm3533-als

[Peter Meerwald]

Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>

---
 .../ABI/testing/sysfs-bus-iio-light-lm3533-als     |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als b/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als
index 694a52c..22c5ea6 100644
--- a/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als
+++ b/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als
@@ -14,7 +14,6 @@ KernelVersion:	3.5
 Contact:	Johan Hovold <jhovold@gmail.com>
 Description:
 		Get the hysteresis for thresholds Y, that is,
-
 		threshY_hysteresis = threshY_raising - threshY_falling
 
 What:		/sys/.../events/illuminance_threshY_falling_value
@@ -31,7 +30,7 @@ Description:
 		threshY_raising.
 
 		These thresholds correspond to the eight zone-boundary
-		registers (boundaryY_{low,high}) and defines the five light
+		registers (boundaryY_{low,high}) and define the five light
 		zones.
 
 What:		/sys/bus/iio/devices/iio:deviceX/in_illuminance0_zone
-- 
1.7.9.5

[PATCH 3/6] iio: iio/machine.h typo

[Peter Meerwald]

Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>

---
 include/linux/iio/machine.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/iio/machine.h b/include/linux/iio/machine.h
index 0b1f19b..400a453 100644
--- a/include/linux/iio/machine.h
+++ b/include/linux/iio/machine.h
@@ -14,7 +14,7 @@
  *			This is matched against the datasheet_name element
  *			of struct iio_chan_spec.
  * @consumer_dev_name:	Name to uniquely identify the consumer device.
- * @consumer_channel:	Unique name used to idenitify the channel on the
+ * @consumer_channel:	Unique name used to identify the channel on the
  *			consumer side.
  */
 struct iio_map {
-- 
1.7.9.5

[PATCH 4/6] iio: add IIO_ALTVOLTAGE to iio_event_monitor example

[Peter Meerwald]

Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>

---
 .../staging/iio/Documentation/iio_event_monitor.c  |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/staging/iio/Documentation/iio_event_monitor.c b/drivers/staging/iio/Documentation/iio_event_monitor.c
index 2227584..4326e9e 100644
--- a/drivers/staging/iio/Documentation/iio_event_monitor.c
+++ b/drivers/staging/iio/Documentation/iio_event_monitor.c
@@ -45,6 +45,7 @@ static const char * const iio_chan_type_name_spec[] = {
 	[IIO_ANGL] = "angl",
 	[IIO_TIMESTAMP] = "timestamp",
 	[IIO_CAPACITANCE] = "capacitance",
+	[IIO_ALTVOLTAGE] = "altvoltage",
 };
 
 static const char * const iio_ev_type_text[] = {
@@ -92,6 +93,7 @@ static bool event_is_known(struct iio_event_data *event)
 	case IIO_ANGL:
 	case IIO_TIMESTAMP:
 	case IIO_CAPACITANCE:
+	case IIO_ALTVOLTAGE:
 		break;
 	default:
 		return false;
-- 
1.7.9.5

[PATCH 5/6] iio staging: typos

[Peter Meerwald]

typos in comments, fix ring_sw module description

Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>

---
 drivers/staging/iio/Documentation/device.txt   |   10 +++++-----
 drivers/staging/iio/Documentation/overview.txt |    2 +-
 drivers/staging/iio/Documentation/ring.txt     |    4 ++--
 drivers/staging/iio/ring_sw.c                  |    4 ++--
 4 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/drivers/staging/iio/Documentation/device.txt b/drivers/staging/iio/Documentation/device.txt
index f03fbd3..ea08d62 100644
--- a/drivers/staging/iio/Documentation/device.txt
+++ b/drivers/staging/iio/Documentation/device.txt
@@ -12,7 +12,7 @@ struct iio_dev *indio_dev = iio_device_alloc(sizeof(struct chip_state));
 where chip_state is a structure of local state data for this instance of
 the chip.
 
-That data can be accessed using iio_priv(struct iio_dev *)
+That data can be accessed using iio_priv(struct iio_dev *).
 
 Then fill in the following:
 
@@ -39,7 +39,7 @@ Then fill in the following:
 		and for associate parameters such as offsets and scales.
 	* info->write_raw:
 		Raw value writing function. Used for writable device values such
-		as DAC values and caliboffset.
+		as DAC values and calibbias.
 	* info->read_event_config:
 		Typically only set if there are some interrupt lines.  This
 		is used to read if an on sensor event detector is enabled.
@@ -62,8 +62,8 @@ Then fill in the following:
 	Poll function related elements. This controls what occurs when a trigger
 	to which this device is attached sends an event.
 - indio_dev->channels:
-	Specification of device channels. Most attributes etc are built
-	form this spec.
+	Specification of device channels. Most attributes etc. are built
+	from this spec.
 - indio_dev->num_channels:
 	How many channels are there?
 
@@ -76,4 +76,4 @@ be registered afterwards (otherwise the whole parentage of devices
 gets confused)
 
 On remove, iio_device_unregister(indio_dev) will remove the device from
-the core, and iio_device_free will clean up.
+the core, and iio_device_free(indio_dev) will clean up.
diff --git a/drivers/staging/iio/Documentation/overview.txt b/drivers/staging/iio/Documentation/overview.txt
index afc39ec..43f92b0 100644
--- a/drivers/staging/iio/Documentation/overview.txt
+++ b/drivers/staging/iio/Documentation/overview.txt
@@ -8,7 +8,7 @@ actual devices combine some ADCs with digital to analog converters
 The aim is to fill the gap between the somewhat similar hwmon and
 input subsystems.  Hwmon is very much directed at low sample rate
 sensors used in applications such as fan speed control and temperature
-measurement.  Input is, as it's name suggests focused on input
+measurement.  Input is, as its name suggests focused on input
 devices. In some cases there is considerable overlap between these and
 IIO.
 
diff --git a/drivers/staging/iio/Documentation/ring.txt b/drivers/staging/iio/Documentation/ring.txt
index e338077..e1da433 100644
--- a/drivers/staging/iio/Documentation/ring.txt
+++ b/drivers/staging/iio/Documentation/ring.txt
@@ -15,8 +15,8 @@ struct iio_ring_buffer contains a struct iio_ring_setup_ops *setup_ops
 which in turn contains the 4 function pointers
 (preenable, postenable, predisable and postdisable).
 These are used to perform device specific steps on either side
-of the core changing it's current mode to indicate that the buffer
-is enabled or disabled (along with enabling triggering etc as appropriate).
+of the core changing its current mode to indicate that the buffer
+is enabled or disabled (along with enabling triggering etc. as appropriate).
 
 Also in struct iio_ring_buffer is a struct iio_ring_access_funcs.
 The function pointers within here are used to allow the core to handle
diff --git a/drivers/staging/iio/ring_sw.c b/drivers/staging/iio/ring_sw.c
index 9358c6c..f61c8fd 100644
--- a/drivers/staging/iio/ring_sw.c
+++ b/drivers/staging/iio/ring_sw.c
@@ -24,7 +24,7 @@
  * @read_p:		read pointer (oldest available)
  * @write_p:		write pointer
  * @half_p:		half buffer length behind write_p (event generation)
- * @update_needed:	flag to indicated change in size requested
+ * @update_needed:	flag to indicate change in size requested
  *
  * Note that the first element of all ring buffers must be a
  * struct iio_buffer.
@@ -363,5 +363,5 @@ void iio_sw_rb_free(struct iio_buffer *r)
 }
 EXPORT_SYMBOL(iio_sw_rb_free);
 
-MODULE_DESCRIPTION("Industrialio I/O software ring buffer");
+MODULE_DESCRIPTION("Industrial I/O software ring buffer");
 MODULE_LICENSE("GPL");
-- 
1.7.9.5

[PATCH 6/6] iio: iio/events.h typos

[Peter Meerwald]

---
 include/linux/iio/events.h |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/include/linux/iio/events.h b/include/linux/iio/events.h
index b5acbf9..13ce220 100644
--- a/include/linux/iio/events.h
+++ b/include/linux/iio/events.h
@@ -46,7 +46,7 @@ enum iio_event_direction {
  * @diff:	Whether the event is for an differential channel or not.
  * @modifier:	Modifier for the channel. Should be one of enum iio_modifier.
  * @direction:	Direction of the event. One of enum iio_event_direction.
- * @type:	Type of the event. Should be one enum iio_event_type.
+ * @type:	Type of the event. Should be one of enum iio_event_type.
  * @chan:	Channel number for non-differential channels.
  * @chan1:	First channel number for differential channels.
  * @chan2:	Second channel number for differential channels.
@@ -69,7 +69,7 @@ enum iio_event_direction {
  * @chan_type:	Type of the channel. Should be one of enum iio_chan_type.
  * @number:	Channel number.
  * @modifier:	Modifier for the channel. Should be one of enum iio_modifier.
- * @type:	Type of the event. Should be one enum iio_event_type.
+ * @type:	Type of the event. Should be one of enum iio_event_type.
  * @direction:	Direction of the event. One of enum iio_event_direction.
  */
 
@@ -81,7 +81,7 @@ enum iio_event_direction {
  * IIO_UNMOD_EVENT_CODE() - create event identifier for unmodified channels
  * @chan_type:	Type of the channel. Should be one of enum iio_chan_type.
  * @number:	Channel number.
- * @type:	Type of the event. Should be one enum iio_event_type.
+ * @type:	Type of the event. Should be one of enum iio_event_type.
  * @direction:	Direction of the event. One of enum iio_event_direction.
  */
 
-- 
1.7.9.5

Re: [PATCH 6/6] iio: iio/events.h typos

[Jonathan Cameron]

You haven't signed off on this...

Other than the fact that typo's is rather generous for whole
missing words I'm happy with this ;)

Thanks,

Acked-by: Jonathan Cameron <jic23@kernel.org>
> ---
>   include/linux/iio/events.h |    6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/iio/events.h b/include/linux/iio/events.h
> index b5acbf9..13ce220 100644
> --- a/include/linux/iio/events.h
> +++ b/include/linux/iio/events.h
> @@ -46,7 +46,7 @@ enum iio_event_direction {
>    * @diff:	Whether the event is for an differential channel or not.
>    * @modifier:	Modifier for the channel. Should be one of enum iio_modifier.
>    * @direction:	Direction of the event. One of enum iio_event_direction.
> - * @type:	Type of the event. Should be one enum iio_event_type.
> + * @type:	Type of the event. Should be one of enum iio_event_type.
>    * @chan:	Channel number for non-differential channels.
>    * @chan1:	First channel number for differential channels.
>    * @chan2:	Second channel number for differential channels.
> @@ -69,7 +69,7 @@ enum iio_event_direction {
>    * @chan_type:	Type of the channel. Should be one of enum iio_chan_type.
>    * @number:	Channel number.
>    * @modifier:	Modifier for the channel. Should be one of enum iio_modifier.
> - * @type:	Type of the event. Should be one enum iio_event_type.
> + * @type:	Type of the event. Should be one of enum iio_event_type.
>    * @direction:	Direction of the event. One of enum iio_event_direction.
>    */
>
> @@ -81,7 +81,7 @@ enum iio_event_direction {
>    * IIO_UNMOD_EVENT_CODE() - create event identifier for unmodified channels
>    * @chan_type:	Type of the channel. Should be one of enum iio_chan_type.
>    * @number:	Channel number.
> - * @type:	Type of the event. Should be one enum iio_event_type.
> + * @type:	Type of the event. Should be one of enum iio_event_type.
>    * @direction:	Direction of the event. One of enum iio_event_direction.
>    */
>

Re: [PATCH 5/6] iio staging: typos

[Jonathan Cameron]

On 6/14/2012 11:50 PM, Peter Meerwald wrote:
> typos in comments, fix ring_sw module description
>
> Signed-off-by: Peter Meerwald<pmeerw@pmeerw.net>
Acked-by: Jonathan Cameron <jic23@kernel.org>
>
> ---
>   drivers/staging/iio/Documentation/device.txt   |   10 +++++-----
>   drivers/staging/iio/Documentation/overview.txt |    2 +-
>   drivers/staging/iio/Documentation/ring.txt     |    4 ++--
>   drivers/staging/iio/ring_sw.c                  |    4 ++--
>   4 files changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/staging/iio/Documentation/device.txt b/drivers/staging/iio/Documentation/device.txt
> index f03fbd3..ea08d62 100644
> --- a/drivers/staging/iio/Documentation/device.txt
> +++ b/drivers/staging/iio/Documentation/device.txt
> @@ -12,7 +12,7 @@ struct iio_dev *indio_dev = iio_device_alloc(sizeof(struct chip_state));
>   where chip_state is a structure of local state data for this instance of
>   the chip.
>
> -That data can be accessed using iio_priv(struct iio_dev *)
> +That data can be accessed using iio_priv(struct iio_dev *).
>
>   Then fill in the following:
>
> @@ -39,7 +39,7 @@ Then fill in the following:
>   		and for associate parameters such as offsets and scales.
>   	* info->write_raw:
>   		Raw value writing function. Used for writable device values such
> -		as DAC values and caliboffset.
> +		as DAC values and calibbias.
>   	* info->read_event_config:
>   		Typically only set if there are some interrupt lines.  This
>   		is used to read if an on sensor event detector is enabled.
> @@ -62,8 +62,8 @@ Then fill in the following:
>   	Poll function related elements. This controls what occurs when a trigger
>   	to which this device is attached sends an event.
>   - indio_dev->channels:
> -	Specification of device channels. Most attributes etc are built
> -	form this spec.
> +	Specification of device channels. Most attributes etc. are built
> +	from this spec.
>   - indio_dev->num_channels:
>   	How many channels are there?
>
> @@ -76,4 +76,4 @@ be registered afterwards (otherwise the whole parentage of devices
>   gets confused)
>
>   On remove, iio_device_unregister(indio_dev) will remove the device from
> -the core, and iio_device_free will clean up.
> +the core, and iio_device_free(indio_dev) will clean up.
> diff --git a/drivers/staging/iio/Documentation/overview.txt b/drivers/staging/iio/Documentation/overview.txt
> index afc39ec..43f92b0 100644
> --- a/drivers/staging/iio/Documentation/overview.txt
> +++ b/drivers/staging/iio/Documentation/overview.txt
> @@ -8,7 +8,7 @@ actual devices combine some ADCs with digital to analog converters
>   The aim is to fill the gap between the somewhat similar hwmon and
>   input subsystems.  Hwmon is very much directed at low sample rate
>   sensors used in applications such as fan speed control and temperature
> -measurement.  Input is, as it's name suggests focused on input
> +measurement.  Input is, as its name suggests focused on input
>   devices. In some cases there is considerable overlap between these and
>   IIO.
>
> diff --git a/drivers/staging/iio/Documentation/ring.txt b/drivers/staging/iio/Documentation/ring.txt
> index e338077..e1da433 100644
> --- a/drivers/staging/iio/Documentation/ring.txt
> +++ b/drivers/staging/iio/Documentation/ring.txt
> @@ -15,8 +15,8 @@ struct iio_ring_buffer contains a struct iio_ring_setup_ops *setup_ops
>   which in turn contains the 4 function pointers
>   (preenable, postenable, predisable and postdisable).
>   These are used to perform device specific steps on either side
> -of the core changing it's current mode to indicate that the buffer
> -is enabled or disabled (along with enabling triggering etc as appropriate).
> +of the core changing its current mode to indicate that the buffer
> +is enabled or disabled (along with enabling triggering etc. as appropriate).
>
>   Also in struct iio_ring_buffer is a struct iio_ring_access_funcs.
>   The function pointers within here are used to allow the core to handle
> diff --git a/drivers/staging/iio/ring_sw.c b/drivers/staging/iio/ring_sw.c
> index 9358c6c..f61c8fd 100644
> --- a/drivers/staging/iio/ring_sw.c
> +++ b/drivers/staging/iio/ring_sw.c
> @@ -24,7 +24,7 @@
>    * @read_p:		read pointer (oldest available)
>    * @write_p:		write pointer
>    * @half_p:		half buffer length behind write_p (event generation)
> - * @update_needed:	flag to indicated change in size requested
> + * @update_needed:	flag to indicate change in size requested
>    *
>    * Note that the first element of all ring buffers must be a
>    * struct iio_buffer.
> @@ -363,5 +363,5 @@ void iio_sw_rb_free(struct iio_buffer *r)
>   }
>   EXPORT_SYMBOL(iio_sw_rb_free);
>
> -MODULE_DESCRIPTION("Industrialio I/O software ring buffer");
> +MODULE_DESCRIPTION("Industrial I/O software ring buffer");
>   MODULE_LICENSE("GPL");

Re: [PATCH 4/6] iio: add IIO_ALTVOLTAGE to iio_event_monitor example

[Jonathan Cameron]

Fair enough though would be good to have a comment that says
what driver actually sends altvoltage events...
On 6/14/2012 11:50 PM, Peter Meerwald wrote:
> Signed-off-by: Peter Meerwald<pmeerw@pmeerw.net>
Acked-by: Jonathan Cameron <jic23@kernel.org>
>
> ---
>   .../staging/iio/Documentation/iio_event_monitor.c  |    2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/drivers/staging/iio/Documentation/iio_event_monitor.c b/drivers/staging/iio/Documentation/iio_event_monitor.c
> index 2227584..4326e9e 100644
> --- a/drivers/staging/iio/Documentation/iio_event_monitor.c
> +++ b/drivers/staging/iio/Documentation/iio_event_monitor.c
> @@ -45,6 +45,7 @@ static const char * const iio_chan_type_name_spec[] = {
>   	[IIO_ANGL] = "angl",
>   	[IIO_TIMESTAMP] = "timestamp",
>   	[IIO_CAPACITANCE] = "capacitance",
> +	[IIO_ALTVOLTAGE] = "altvoltage",
>   };
>
>   static const char * const iio_ev_type_text[] = {
> @@ -92,6 +93,7 @@ static bool event_is_known(struct iio_event_data *event)
>   	case IIO_ANGL:
>   	case IIO_TIMESTAMP:
>   	case IIO_CAPACITANCE:
> +	case IIO_ALTVOLTAGE:
>   		break;
>   	default:
>   		return false;

Re: [PATCH 3/6] iio: iio/machine.h typo

[Jonathan Cameron]

There I go inventing more words ;)
> Signed-off-by: Peter Meerwald<pmeerw@pmeerw.net>
Acked-by: Jonathan Cameron <jic23@kernel.org>
>
> ---
>   include/linux/iio/machine.h |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/iio/machine.h b/include/linux/iio/machine.h
> index 0b1f19b..400a453 100644
> --- a/include/linux/iio/machine.h
> +++ b/include/linux/iio/machine.h
> @@ -14,7 +14,7 @@
>    *			This is matched against the datasheet_name element
>    *			of struct iio_chan_spec.
>    * @consumer_dev_name:	Name to uniquely identify the consumer device.
> - * @consumer_channel:	Unique name used to idenitify the channel on the
> + * @consumer_channel:	Unique name used to identify the channel on the
>    *			consumer side.
>    */
>   struct iio_map {

Re: [PATCH 2/6] iio: cleanup sysfs-bus-iio-light-lm3533-als

[Jonathan Cameron]

On 6/14/2012 11:50 PM, Peter Meerwald wrote:
> Signed-off-by: Peter Meerwald<pmeerw@pmeerw.net>
should cc the author.  They might be particularly
attached to that blank line :)

Acked-by: Jonathan Cameron <jic23@kernel.org>
>
> ---
>   .../ABI/testing/sysfs-bus-iio-light-lm3533-als     |    3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als b/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als
> index 694a52c..22c5ea6 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als
> +++ b/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als
> @@ -14,7 +14,6 @@ KernelVersion:	3.5
>   Contact:	Johan Hovold<jhovold@gmail.com>
>   Description:
>   		Get the hysteresis for thresholds Y, that is,
> -
>   		threshY_hysteresis = threshY_raising - threshY_falling
>
>   What:		/sys/.../events/illuminance_threshY_falling_value
> @@ -31,7 +30,7 @@ Description:
>   		threshY_raising.
>
>   		These thresholds correspond to the eight zone-boundary
> -		registers (boundaryY_{low,high}) and defines the five light
> +		registers (boundaryY_{low,high}) and define the five light
>   		zones.
>
>   What:		/sys/bus/iio/devices/iio:deviceX/in_illuminance0_zone

Re: [PATCH 1/6] iio: sysfs-bus-iio typo

[Jonathan Cameron]

On 6/14/2012 11:50 PM, Peter Meerwald wrote:
> Signed-off-by: Peter Meerwald<pmeerw@pmeerw.net>
Acked-by: Jonathan Cameron <jic23@kernel.org>
>
> ---
>   Documentation/ABI/testing/sysfs-bus-iio |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index 05449c6..a3774a7 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -122,7 +122,7 @@ Description:
>   		If an axis is specified it generally means that the temperature
>   		sensor is associated with one part of a compound device (e.g.
>   		a gyroscope axis). Units after application of scale and offset
> -		are milli degrees Celsuis.
> +		are milli degrees Celsius.
>
>   What:		/sys/bus/iio/devices/iio:deviceX/in_tempX_input
>   KernelVersion:	2.6.38

[PATCH 3/6] iio: iio/machine.h typo

[Peter Meerwald]

Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
Acked-by: Jonathan Cameron <jic23@kernel.org>

---
 include/linux/iio/machine.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/iio/machine.h b/include/linux/iio/machine.h
index 0b1f19b..400a453 100644
--- a/include/linux/iio/machine.h
+++ b/include/linux/iio/machine.h
@@ -14,7 +14,7 @@
  *			This is matched against the datasheet_name element
  *			of struct iio_chan_spec.
  * @consumer_dev_name:	Name to uniquely identify the consumer device.
- * @consumer_channel:	Unique name used to idenitify the channel on the
+ * @consumer_channel:	Unique name used to identify the channel on the
  *			consumer side.
  */
 struct iio_map {
-- 
1.7.9.5