Commit 7bd47496 authored by Peter Rosin's avatar Peter Rosin Committed by Linus Walleij

pinctrl: sx150x: various spelling fixes and some white-space cleanup

Acked-by: default avatarNeil Armstrong <narmstrong@baylibre.com>
Signed-off-by: default avatarPeter Rosin <peda@axentia.se>
Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
parent 4ecb65fb
......@@ -880,7 +880,7 @@ static unsigned int sx150x_maybe_swizzle(struct sx150x_pinctrl *pctl,
* reg + 3 [ 3 3 2 2 1 1 0 0 ]
*
* SX1503 and SX1506 deviate from that data layout, instead storing
* thier contents as follows:
* their contents as follows:
*
* reg [ f f e e d d c c ]
* reg + 1 [ 7 7 6 6 5 5 4 4 ]
......@@ -915,9 +915,8 @@ static unsigned int sx150x_maybe_swizzle(struct sx150x_pinctrl *pctl,
*
* This way the rest of the driver code, interfacing with the chip via
* regmap API, can work assuming that each GPIO pin is represented by
* a group of bits at an offset proportioan to GPIO number within a
* a group of bits at an offset proportional to GPIO number within a
* given register.
*
*/
static int sx150x_regmap_reg_read(void *context, unsigned int reg,
unsigned int *result)
......@@ -929,7 +928,7 @@ static int sx150x_regmap_reg_read(void *context, unsigned int reg,
unsigned int idx, val;
/*
* There are four potential cases coverd by this function:
* There are four potential cases covered by this function:
*
* 1) 8-pin chip, single configuration bit register
*
......
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