From f90f5d8da8a1f1d5e83c4e587e87f157cf8f43a3 Mon Sep 17 00:00:00 2001 From: Henrik Brix Andersen Date: Mon, 4 May 2020 15:28:43 +0200 Subject: [PATCH] drivers: i2c: i2c_gpio: reformat comment Reformat comment describing the I2C GPIO bit banging pre-requisites to improve readability. Signed-off-by: Henrik Brix Andersen --- drivers/i2c/i2c_gpio.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/drivers/i2c/i2c_gpio.c b/drivers/i2c/i2c_gpio.c index 36a35d77629..8d5306feeeb 100644 --- a/drivers/i2c/i2c_gpio.c +++ b/drivers/i2c/i2c_gpio.c @@ -12,11 +12,14 @@ * @brief Driver for software driven I2C using GPIO lines * * This driver implements an I2C interface by driving two GPIO lines under - * software control. The GPIO pins used must be configured (through devicetree and pinmux) with suitable - * flags, i.e. the SDA pin as open-colector/open-drain with a pull-up resistor - * (possibly as an external component attached to the pin). When the SDA pin - * is read it must return the state of the physical hardware line, not just the - * last state written to it for output. + * software control. + * + * The GPIO pins used must be configured (through devicetree and pinmux) with + * suitable flags, i.e. the SDA pin as open-collector/open-drain with a pull-up + * resistor (possibly as an external component attached to the pin). + * + * When the SDA pin is read it must return the state of the physical hardware + * line, not just the last state written to it for output. * * The SCL pin should be configured in the same manner as SDA, or, if it is known * that the hardware attached to pin doesn't attempt clock stretching, then the