From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org, geert@linux-m68k.org,
gregkh@linuxfoundation.org, wsa@the-dreams.de,
linux-serial@vger.kernel.org, magnus.damm@gmail.com,
sergei.shtylyov@cogentembedded.com
Subject: Re: [PATCH v4 3/4] serial: sh-sci: make RX FIFO parameters tunable via sysfs
Date: Sun, 12 Feb 2017 18:04:52 +0200 [thread overview]
Message-ID: <1794065.DucaPDu9pY@avalon> (raw)
In-Reply-To: <1486118300-12633-4-git-send-email-ulrich.hecht+renesas@gmail.com>
Hi Ulrich,
Thank you for the patch.
On Friday 03 Feb 2017 11:38:19 Ulrich Hecht wrote:
> Allows tuning of the RX FIFO fill threshold and timeout. (The latter is
> only applicable to SCIFA and SCIFB).
>
> Signed-off-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/tty/serial/sh-sci.c | 87 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 87 insertions(+)
>
> diff --git a/drivers/tty/serial/sh-sci.c b/drivers/tty/serial/sh-sci.c
> index 4a165ed..f95a56c 100644
> --- a/drivers/tty/serial/sh-sci.c
> +++ b/drivers/tty/serial/sh-sci.c
> @@ -1055,6 +1055,66 @@ static void rx_fifo_timer_fn(unsigned long arg)
> scif_set_rtrg(port, 1);
> }
>
> +static ssize_t rx_trigger_show(struct device *dev,
> + struct device_attribute *attr,
> + char *buf)
> +{
> + struct uart_port *port = dev_get_drvdata(dev);
> + struct sci_port *sci = to_sci_port(port);
> +
> + return sprintf(buf, "%d\n", sci->rx_trigger);
> +}
> +
> +static ssize_t rx_trigger_store(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf,
> + size_t count)
> +{
> + struct uart_port *port = dev_get_drvdata(dev);
> + struct sci_port *sci = to_sci_port(port);
> + long r;
> +
> + if (kstrtol(buf, 0, &r) == -EINVAL)
> + return -EINVAL;
> + sci->rx_trigger = scif_set_rtrg(port, r);
> + scif_set_rtrg(port, 1);
> + return count;
> +}
> +
> +static DEVICE_ATTR(rx_fifo_trigger, 0644, rx_trigger_show,
> rx_trigger_store); +
> +static ssize_t rx_fifo_timeout_show(struct device *dev,
> + struct device_attribute *attr,
> + char *buf)
> +{
> + struct uart_port *port = dev_get_drvdata(dev);
> + struct sci_port *sci = to_sci_port(port);
> +
> + return sprintf(buf, "%d\n", sci->rx_fifo_timeout);
> +}
> +
> +static ssize_t rx_fifo_timeout_store(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf,
> + size_t count)
> +{
> + struct uart_port *port = dev_get_drvdata(dev);
> + struct sci_port *sci = to_sci_port(port);
> + long r;
> +
> + if (kstrtol(buf, 0, &r) == -EINVAL)
> + return -EINVAL;
> + sci->rx_fifo_timeout = r;
> + scif_set_rtrg(port, 1);
> + if (r > 0)
> + setup_timer(&sci->rx_fifo_timer, rx_fifo_timer_fn,
> + (unsigned long)sci);
Where's the locking ?
> + return count;
> +}
> +
> +static DEVICE_ATTR(rx_fifo_timeout, 0644, rx_fifo_timeout_show,
> rx_fifo_timeout_store); +
> +
> #ifdef CONFIG_SERIAL_SH_SCI_DMA
> static void sci_dma_tx_complete(void *arg)
> {
> @@ -2886,6 +2946,15 @@ static int sci_remove(struct platform_device *dev)
>
> sci_cleanup_single(port);
>
> + if (port->port.fifosize > 1) {
> + sysfs_remove_file(&dev->dev.kobj,
> + &dev_attr_rx_fifo_trigger.attr);
> + }
> + if (port->port.type == PORT_SCIFA || port->port.type == PORT_SCIFB) {
> + sysfs_remove_file(&dev->dev.kobj,
> + &dev_attr_rx_fifo_timeout.attr);
> + }
No need for curly braces.
> +
> return 0;
> }
>
> @@ -3051,6 +3120,24 @@ static int sci_probe(struct platform_device *dev)
> if (ret)
> return ret;
>
> + if (sp->port.fifosize > 1) {
> + ret = sysfs_create_file(&dev->dev.kobj,
> + &dev_attr_rx_fifo_trigger.attr);
You should use device_create_file for device attributes. Even better would be
to create an attribute group if possible.
> + if (ret)
> + return ret;
> + }
> + if (sp->port.type == PORT_SCIFA || sp->port.type == PORT_SCIFB) {
> + ret = sysfs_create_file(&dev->dev.kobj,
> + &dev_attr_rx_fifo_timeout.attr);
> + if (ret) {
> + if (sp->port.fifosize > 1) {
> + sysfs_remove_file(&dev->dev.kobj,
> + &dev_attr_rx_fifo_trigger.attr);
> + }
> + return ret;
> + }
> + }
> +
> #ifdef CONFIG_SH_STANDARD_BIOS
> sh_bios_gdb_detach();
> #endif
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-02-12 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 10:38 [PATCH v4 0/4] Renesas *SCIF* RX FIFO support Ulrich Hecht
2017-02-03 10:38 ` [PATCH v4 1/4] serial: sh-sci: increase RX FIFO trigger defaults for (H)SCIF Ulrich Hecht
2017-02-07 14:40 ` Geert Uytterhoeven
2017-02-03 10:38 ` [PATCH v4 2/4] serial: sh-sci: SCIFA/B RX FIFO software timeout Ulrich Hecht
2017-02-03 10:38 ` [PATCH v4 3/4] serial: sh-sci: make RX FIFO parameters tunable via sysfs Ulrich Hecht
2017-02-07 14:40 ` Geert Uytterhoeven
2017-02-08 10:04 ` Ulrich Hecht
2017-02-08 10:38 ` Geert Uytterhoeven
2017-02-12 16:04 ` Laurent Pinchart [this message]
2017-02-03 10:38 ` [PATCH v4 4/4] arm64: dts: r8a7796: salvator-x: add SCIF1 (DEBUG1) Ulrich Hecht
2017-02-08 10:54 ` Simon Horman
2017-02-08 11:19 ` Ulrich Hecht
2017-02-13 13:05 ` Simon Horman
2017-02-13 13:10 ` Geert Uytterhoeven
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=1794065.DucaPDu9pY@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=ulrich.hecht+renesas@gmail.com \
--cc=wsa@the-dreams.de \
/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