Skip to contentSkip to conversation

gpio: ts4900: Do not set DAT and OE together

PATCH Applied Kris Bahnsen 3 participants 10 messages Mar 10, 2022 – Mar 11, 2022 GPIO

lore
Share & tools
lore
#0 lore raw

v3 cover gpio: ts4900: Do not set DAT and OE together

Work around hardware race condition when setting DAT and OE in same transaction. Also clean up license boilerplate and use SPDX.

I was not sure if it was preferred to make it a series or individual patches. I went with series because "gpio: ts4900: Use SPDX header" cannot cleanly apply by itself due to copyright year changes in the fix commit. If this is not preferred, please let me know.

V3:
- Move addition of SPDX identifier to separate commit
- Remove license boilerplate in file

V2:
- Add Fixes tag

Kris Bahnsen (1):
gpio: ts4900: Use SPDX header

Mark Featherston (1):
gpio: ts4900: Do not set DAT and OE together

 drivers/gpio/gpio-ts4900.c | 34 ++++++++++++++++++++--------------
 1 file changed, 20 insertions(+), 14 deletions(-)
Signature · 1 line
2.11.0
#1 lore raw

PATCH v3 1/2 gpio: ts4900: Do not set DAT and OE together

From: Mark Featherston <[email protected]>

This works around an issue with the hardware where both OE and DAT are exposed in the same register. If both are updated simultaneously, the harware makes no guarantees that OE or DAT will actually change in any given order and may result in a glitch of a few ns on a GPIO pin when changing direction and value in a single write.

Setting direction to input now only affects OE bit. Setting direction to output updates DAT first, then OE.

Fixes 9c6686322d74 ("gpio: add Technologic I2C-FPGA gpio support")
---
 drivers/gpio/gpio-ts4900.c | 24 +++++++++++++++++++-----
 1 file changed, 19 insertions(+), 5 deletions(-)
drivers/gpio/gpio-ts4900.c +19 -5
index d885032cf814..d918d2df4de2 100644
@@ -1,7 +1,7 @@
 /*
  * Digital I/O driver for Technologic Systems I2C FPGA Core
  *
- * Copyright (C) 2015 Technologic Systems
+ * Copyright (C) 2015, 2018 Technologic Systems
  * Copyright (C) 2016 Savoir-Faire Linux
  *
  * This program is free software; you can redistribute it and/or
@@ -55,19 +55,33 @@ static int ts4900_gpio_direction_input(struct gpio_chip *chip,
 {
 	struct ts4900_gpio_priv *priv = gpiochip_get_data(chip);
 
-	/*
-	 * This will clear the output enable bit, the other bits are
-	 * dontcare when this is cleared
+	/* Only clear the OE bit here, requires a RMW. Prevents potential issue
+	 * with OE and data getting to the physical pin at different times.
 	 */
-	return regmap_write(priv->regmap, offset, 0);
+	return regmap_update_bits(priv->regmap, offset, TS4900_GPIO_OE, 0);
 }
 
 static int ts4900_gpio_direction_output(struct gpio_chip *chip,
 					unsigned int offset, int value)
 {
 	struct ts4900_gpio_priv *priv = gpiochip_get_data(chip);
+	unsigned int reg;
 	int ret;
 
+	/* If changing from an input to an output, we need to first set the
+	 * proper data bit to what is requested and then set OE bit. This
+	 * prevents a glitch that can occur on the IO line
+	 */
+	regmap_read(priv->regmap, offset, &reg);
+	if (!(reg & TS4900_GPIO_OE)) {
+		if (value)
+			reg = TS4900_GPIO_OUT;
+		else
+			reg &= ~TS4900_GPIO_OUT;
+
+		regmap_write(priv->regmap, offset, reg);
+	}
+
 	if (value)
 		ret = regmap_write(priv->regmap, offset, TS4900_GPIO_OE |
 							 TS4900_GPIO_OUT);
Signature · 1 line
2.11.0
#2 lore raw
Quoted 73 lines · Kris Bahnsen

From: Mark Featherston <[email protected]>

This works around an issue with the hardware where both OE and DAT are exposed in the same register. If both are updated simultaneously, the harware makes no guarantees that OE or DAT will actually change in any given order and may result in a glitch of a few ns on a GPIO pin when changing direction and value in a single write.

Setting direction to input now only affects OE bit. Setting direction to output updates DAT first, then OE.

Fixes 9c6686322d74 ("gpio: add Technologic I2C-FPGA gpio support")
---
 drivers/gpio/gpio-ts4900.c | 24 +++++++++++++++++++-----
 1 file changed, 19 insertions(+), 5 deletions(-)
drivers/gpio/gpio-ts4900.c +19 -6
index d885032cf814..d918d2df4de2 100644
@@ -1,7 +1,7 @@
 /*
  * Digital I/O driver for Technologic Systems I2C FPGA Core
  *
- * Copyright (C) 2015 Technologic Systems
+ * Copyright (C) 2015, 2018 Technologic Systems
  * Copyright (C) 2016 Savoir-Faire Linux
  *
  * This program is free software; you can redistribute it and/or
@@ -55,19 +55,33 @@ static int ts4900_gpio_direction_input(struct gpio_chip *chip,
 {
        struct ts4900_gpio_priv *priv = gpiochip_get_data(chip);
 
-       /*
-        * This will clear the output enable bit, the other bits are
-        * dontcare when this is cleared
+       /* Only clear the OE bit here, requires a RMW. Prevents potential issue
+        * with OE and data getting to the physical pin at different times.
         */
-       return regmap_write(priv->regmap, offset, 0);
+       return regmap_update_bits(priv->regmap, offset, TS4900_GPIO_OE, 0);
 }
 
 static int ts4900_gpio_direction_output(struct gpio_chip *chip,
                                        unsigned int offset, int value)
 {
        struct ts4900_gpio_priv *priv = gpiochip_get_data(chip);
+       unsigned int reg;
        int ret;
 
+       /* If changing from an input to an output, we need to first set the
+        * proper data bit to what is requested and then set OE bit. This
+        * prevents a glitch that can occur on the IO line
+        */
+       regmap_read(priv->regmap, offset, &reg);
+       if (!(reg & TS4900_GPIO_OE)) {
+               if (value)
+                       reg = TS4900_GPIO_OUT;
+               else
+                       reg &= ~TS4900_GPIO_OUT;
+
+               regmap_write(priv->regmap, offset, reg);
+       }
+
        if (value)
                ret = regmap_write(priv->regmap, offset, TS4900_GPIO_OE |
                                                         TS4900_GPIO_OUT);
--
Quoted 2 lines

2.11.0

Applied for fixes, thanks!

Bart

#4 lore raw
Quoted 6 lines · Andy Shevchenko
Quoted 2 lines · Kris Bahnsen

From: Mark Featherston <[email protected]>

Same comments as per v2.

Thanks, I'll get a v4 put together shortly to clean that up.

#5 lore raw
Quoted 10 lines · Kris Bahnsen
Quoted 6 lines · Andy Shevchenko
Quoted 2 lines · Kris Bahnsen

From: Mark Featherston <[email protected]>

Same comments as per v2.

Thanks, I'll get a v4 put together shortly to clean that up.

Hey Kris,

I already sent it out to Linus, please create a follow-up patch for that.

Bart

#6 lore raw
Quoted 10 lines · Bartosz Golaszewski
Quoted 9 lines · Kris Bahnsen
Quoted 6 lines · Andy Shevchenko
Quoted 2 lines · Kris Bahnsen

From: Mark Featherston <[email protected]>

Same comments as per v2.

Quoted 7 lines
Quoted 1 line

Thanks, I'll get a v4 put together shortly to clean that up.

Hey Kris,

I already sent it out to Linus, please create a follow-up patch for that.

Bart

Can you please clarify what that entails since Andy had requested changes to the commit message. Should I just create a new patch on top of the commit already on master to address the comment changes? How would I address commit message changes, or is that not my responsibility at this point?

Thanks for all the help on learning this process thus far!

Kris

#7 lore raw
Quoted 2 lines · Kris Bahnsen
Quoted 1 line · Bartosz Golaszewski

On Thu, Mar 10, 2022 at 6:36 PM Kris Bahnsen <[email protected]> wrote:

...

Quoted 7 lines
Quoted 3 lines

Hey Kris,

I already sent it out to Linus, please create a follow-up patch for that.

Can you please clarify what that entails since Andy had requested changes to the commit message. Should I just create a new patch on top of the commit already on master to address the comment changes?

Address the comments.

Quoted 2 lines

How would I address commit message changes,
or is that not my responsibility at this point?

It's impossible.

Signature · 2 lines
With Best Regards,
Andy Shevchenko
#8 lore raw

PATCH v3 2/2 gpio: ts4900: Use SPDX header

In reply to Kris Bahnsen

Remove boilerplate, use the SPDX license identifier.

---
 drivers/gpio/gpio-ts4900.c | 10 +---------
 1 file changed, 1 insertion(+), 9 deletions(-)
drivers/gpio/gpio-ts4900.c +1 -9
index d918d2df4de2..69854fd2382a 100644
@@ -1,17 +1,9 @@
+// SPDX-License-Identifier: GPL-2.0
 /*
  * Digital I/O driver for Technologic Systems I2C FPGA Core
  *
  * Copyright (C) 2015, 2018 Technologic Systems
  * Copyright (C) 2016 Savoir-Faire Linux
- *
- * This program is free software; you can redistribute it and/or
- * modify it under the terms of the GNU General Public License version 2 as
- * published by the Free Software Foundation.
- *
- * This program is distributed "as is" WITHOUT ANY WARRANTY of any
- * kind, whether expressed or implied; without even the implied warranty
- * of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- * GNU General Public License version 2 for more details.
  */
 
 #include <linux/gpio/driver.h>
Signature · 1 line
2.11.0
#9 lore raw

Re: [PATCH v3 2/2] gpio: ts4900: Use SPDX header

Quoted 32 lines · Kris Bahnsen

Remove boilerplate, use the SPDX license identifier.

---
 drivers/gpio/gpio-ts4900.c | 10 +---------
 1 file changed, 1 insertion(+), 9 deletions(-)
drivers/gpio/gpio-ts4900.c +1 -10
index d918d2df4de2..69854fd2382a 100644
@@ -1,17 +1,9 @@
+// SPDX-License-Identifier: GPL-2.0
 /*
  * Digital I/O driver for Technologic Systems I2C FPGA Core
  *
  * Copyright (C) 2015, 2018 Technologic Systems
  * Copyright (C) 2016 Savoir-Faire Linux
- *
- * This program is free software; you can redistribute it and/or
- * modify it under the terms of the GNU General Public License version 2 as
- * published by the Free Software Foundation.
- *
- * This program is distributed "as is" WITHOUT ANY WARRANTY of any
- * kind, whether expressed or implied; without even the implied warranty
- * of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- * GNU General Public License version 2 for more details.
  */
 
 #include <linux/gpio/driver.h>
--
Quoted 2 lines

2.11.0

Applied, thanks!

Bart