From: Lech Perczak <lech.perczak@camlingroup.com>
To: Hui Wang <hui.wang@canonical.com>,
linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
gregkh@linuxfoundation.org
Cc: jirislaby@kernel.org, hvilleneuve@dimonoff.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, andy@kernel.org,
Maarten.Brock@sttls.nl
Subject: Re: [PATCH v3 2/2] serial: sc16is7xx: hardware reset chip if reset-gpios is defined in DT
Date: Wed, 12 Jun 2024 15:56:51 +0200 [thread overview]
Message-ID: <18a1beeb-e45b-4d6d-bd21-74b85c33dc2c@camlingroup.com> (raw)
In-Reply-To: <20240612131454.49671-2-hui.wang@canonical.com>
Hi,
Some comments inline.
W dniu 12.06.2024 o 15:14, Hui Wang pisze:
> Some boards connect a GPIO to the reset pin, and the reset pin needs
> to be setup correctly before accessing the chip.
>
> Add a function to handle the chip reset. If the reset-gpios is defined
> in the DT, do hardware reset through this GPIO, othwerwise do software
> reset as before.
>
> Signed-off-by: Hui Wang <hui.wang@canonical.com>
> ---
> In the v3:
> - drop Reviewed-by
> - adjust the sequence of if, else if and else
> - replace PTR_ERR(reset_gpiod) with dev_err_probe
> - change GPIOD_OUT_LOW to GPIOD_OUT_HIGH, this will assert the reset pin after requesting the GPIO
> - change the 2nd parameter struct regmap *regmap[] to struct regmap *regmap
> - address all spelling and description issues in the v2
>
> drivers/tty/serial/sc16is7xx.c | 33 +++++++++++++++++++++++++++++----
> 1 file changed, 29 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/tty/serial/sc16is7xx.c b/drivers/tty/serial/sc16is7xx.c
> index bf0065d1c8e9..8c7e0fe76049 100644
> --- a/drivers/tty/serial/sc16is7xx.c
> +++ b/drivers/tty/serial/sc16is7xx.c
> @@ -14,6 +14,7 @@
> #include <linux/delay.h>
> #include <linux/device.h>
> #include <linux/export.h>
> +#include <linux/gpio/consumer.h>
> #include <linux/gpio/driver.h>
> #include <linux/idr.h>
> #include <linux/kthread.h>
> @@ -1467,6 +1468,30 @@ static const struct serial_rs485 sc16is7xx_rs485_supported = {
> .delay_rts_after_send = 1, /* Not supported but keep returning -EINVAL */
> };
>
> +/* Reset device, purging any pending irq / data */
> +static int sc16is7xx_reset(struct device *dev, struct regmap *regmap)
> +{
> + struct gpio_desc *reset_gpio;
> +
> + /* The reset GPIO is ACTIVE_LOW, flag GPIOD_OUT_HIGH asserts the reset GPIO */
s/reset GPIO is ACTIVE_LOW /reset input is active low/ - because we're referring to the chip input here, and this is reflected in DT bindings.
Also, it isn't clear from the comment that GPIO is asserted immediately.
> + reset_gpio = devm_gpiod_get_optional(dev, "reset", GPIOD_OUT_HIGH);
> + if (IS_ERR(reset_gpio))
> + return dev_err_probe(dev, PTR_ERR(reset_gpio), "Failed to get reset GPIO\n");
> +
> + if (reset_gpio) {
> + /* The minimum reset pulse width is 3 us. */
> + udelay(5);
Prefer usleep_range() over that, since maximum reset time isn't all that critical.
> + gpiod_set_value_cansleep(reset_gpio, 0);
> + /* Deassert GPIO */
This comment should go one line above or be removed entirely.
> + } else {
> + /* Software reset */
> + regmap_write(regmap, SC16IS7XX_IOCONTROL_REG,
> + SC16IS7XX_IOCONTROL_SRESET_BIT);
> + }
> +
> + return 0;
> +}
> +
> int sc16is7xx_probe(struct device *dev, const struct sc16is7xx_devtype *devtype,
> struct regmap *regmaps[], int irq)
> {
> @@ -1527,6 +1552,10 @@ int sc16is7xx_probe(struct device *dev, const struct sc16is7xx_devtype *devtype,
> s->devtype = devtype;
> dev_set_drvdata(dev, s);
>
> + ret = sc16is7xx_reset(dev, regmaps[0]);
> + if (ret)
> + goto out_clk;
> +
> kthread_init_worker(&s->kworker);
> s->kworker_task = kthread_run(kthread_worker_fn, &s->kworker,
> "sc16is7xx");
> @@ -1536,10 +1565,6 @@ int sc16is7xx_probe(struct device *dev, const struct sc16is7xx_devtype *devtype,
> }
> sched_set_fifo(s->kworker_task);
>
> - /* reset device, purging any pending irq / data */
> - regmap_write(regmaps[0], SC16IS7XX_IOCONTROL_REG,
> - SC16IS7XX_IOCONTROL_SRESET_BIT);
> -
> /* Mark each port line and status as uninitialised. */
> for (i = 0; i < devtype->nr_uart; ++i) {
> s->p[i].port.line = SC16IS7XX_MAX_DEVS;
> --
> 2.34.1
--
Pozdrawiam/With kind regards,
Lech Perczak
Sr. Software Engineer
Camlin Technologies Poland Limited Sp. z o.o.
Strzegomska 54,
53-611 Wroclaw
Tel: (+48) 71 75 000 16
Email: lech.perczak@camlingroup.com
Website: http://www.camlingroup.com
next prev parent reply other threads:[~2024-06-12 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 13:14 [PATCH v3 1/2] dt-bindings: serial: sc16is7xx: add reset-gpios Hui Wang
2024-06-12 13:14 ` [PATCH v3 2/2] serial: sc16is7xx: hardware reset chip if reset-gpios is defined in DT Hui Wang
2024-06-12 13:50 ` Hugo Villeneuve
2024-06-12 14:46 ` Hui Wang
2024-06-12 13:56 ` Lech Perczak [this message]
2024-06-12 14:50 ` Hui Wang
2024-06-13 20:45 ` Andy Shevchenko
2024-06-12 16:37 ` [PATCH v3 1/2] dt-bindings: serial: sc16is7xx: add reset-gpios Conor Dooley
2024-06-12 16:49 ` Hugo Villeneuve
2024-06-12 16:58 ` Conor Dooley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18a1beeb-e45b-4d6d-bd21-74b85c33dc2c@camlingroup.com \
--to=lech.perczak@camlingroup.com \
--cc=Maarten.Brock@sttls.nl \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=hvilleneuve@dimonoff.com \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox