From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
linus.walleij@linaro.org
Cc: linux-gpio@vger.kernel.org,
"<gregkh@linuxfoundation.org> KH" <gregkh@linuxfoundation.org>,
Alex Courbot <acourbot@nvidia.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM/serial: at91: specify RTS in DT using gpio
Date: Tue, 5 Nov 2013 17:57:05 +0100 [thread overview]
Message-ID: <52792361.6030803@atmel.com> (raw)
In-Reply-To: <A7887CC8-A1F9-4A05-B7F5-4F69FD942F22@jcrosoft.com>
On 05/11/2013 16:59, Jean-Christophe PLAGNIOL-VILLARD :
>
> On Nov 5, 2013, at 11:29 PM, Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>> ---
>> Documentation/devicetree/bindings/serial/atmel-usart.txt | 3 +++
>> drivers/tty/serial/atmel_serial.c | 13 ++++++++++---
>> 2 files changed, 13 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/serial/atmel-usart.txt b/Documentation/devicetree/bindings/serial/atmel-usart.txt
>> index 2191dcb..3adc61c 100644
>> --- a/Documentation/devicetree/bindings/serial/atmel-usart.txt
>> +++ b/Documentation/devicetree/bindings/serial/atmel-usart.txt
>> @@ -10,6 +10,8 @@ Required properties:
>> Optional properties:
>> - atmel,use-dma-rx: use of PDC or DMA for receiving data
>> - atmel,use-dma-tx: use of PDC or DMA for transmitting data
>> +- rts-gpios: specify a GPIO for RTS line. It will use specified PIO instead of the peripheral
>> + function pin for the USART RTS feature. If unsure, don't specify this property.
>> - add dma bindings for dma transfer:
>> - dmas: DMA specifier, consisting of a phandle to DMA controller node,
>> memory peripheral interface and USART DMA channel ID, FIFO configuration.
>> @@ -28,6 +30,7 @@ Example:
>> interrupts = <7>;
>> atmel,use-dma-rx;
>> atmel,use-dma-tx;
>> + rts-gpios = <&pioD 15 0>;
>> };
>
> gpios means 2 gpio
>
> I’ll rts-gpio as we can only use one anyway
Cf. Andrew's comment.
>> - use DMA:
>> diff --git a/drivers/tty/serial/atmel_serial.c b/drivers/tty/serial/atmel_serial.c
>> index b4e0794..71f8ea9 100644
>> --- a/drivers/tty/serial/atmel_serial.c
>> +++ b/drivers/tty/serial/atmel_serial.c
>> @@ -35,6 +35,7 @@
>> #include <linux/platform_device.h>
>> #include <linux/of.h>
>> #include <linux/of_device.h>
>> +#include <linux/of_gpio.h>
>> #include <linux/dma-mapping.h>
>> #include <linux/atmel_pdc.h>
>> #include <linux/atmel_serial.h>
>> @@ -2327,6 +2328,7 @@ static int atmel_serial_probe(struct platform_device *pdev)
>> struct device_node *np = pdev->dev.of_node;
>> struct atmel_uart_data *pdata = dev_get_platdata(&pdev->dev);
>> void *data;
>> + int rts_pin = -EINVAL;
>> int ret = -ENODEV;
>>
>> BUILD_BUG_ON(ATMEL_SERIAL_RINGSIZE & (ATMEL_SERIAL_RINGSIZE - 1));
>> @@ -2364,13 +2366,18 @@ static int atmel_serial_probe(struct platform_device *pdev)
>> * structs to indicate "no RTS GPIO" instead of open-coding some
>> * invalid value everywhere.
>> */
>> - if (pdata->rts_gpio > 0) {
>> - ret = devm_gpio_request(&pdev->dev, pdata->rts_gpio, "RTS");
>> + if (pdata && pdata->rts_gpio > 0)
>> + rts_pin = pdata->rts_gpio;
>> + else if (np)
>> + rts_pin = of_get_named_gpio(np, "rts-gpios", 0);
>> +
>
> use directly port->rts_gpio so we can drop the assign after
>
> if the gpio is invalid the port->rts_gpio need to be < 0 too
Yes this is definitively an option. I cook a v2 right now.
>
> Best Regards,
> J.
>
>> + if (gpio_is_valid(rts_pin)) {
>> + ret = devm_gpio_request(&pdev->dev, rts_pin, "RTS");
>> if (ret) {
>> dev_err(&pdev->dev, "error requesting RTS GPIO\n");
>> goto err;
>> }
>> - port->rts_gpio = pdata->rts_gpio;
>> + port->rts_gpio = rts_pin;
>> ret = gpio_direction_output(port->rts_gpio, 0);
>> if (ret) {
>> dev_err(&pdev->dev, "error setting up RTS GPIO\n");
>> --
>> 1.8.2.2
>>
>
>
>
--
Nicolas Ferre
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM/serial: at91: specify RTS in DT using gpio
Date: Tue, 5 Nov 2013 17:57:05 +0100 [thread overview]
Message-ID: <52792361.6030803@atmel.com> (raw)
In-Reply-To: <A7887CC8-A1F9-4A05-B7F5-4F69FD942F22@jcrosoft.com>
On 05/11/2013 16:59, Jean-Christophe PLAGNIOL-VILLARD :
>
> On Nov 5, 2013, at 11:29 PM, Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>> ---
>> Documentation/devicetree/bindings/serial/atmel-usart.txt | 3 +++
>> drivers/tty/serial/atmel_serial.c | 13 ++++++++++---
>> 2 files changed, 13 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/serial/atmel-usart.txt b/Documentation/devicetree/bindings/serial/atmel-usart.txt
>> index 2191dcb..3adc61c 100644
>> --- a/Documentation/devicetree/bindings/serial/atmel-usart.txt
>> +++ b/Documentation/devicetree/bindings/serial/atmel-usart.txt
>> @@ -10,6 +10,8 @@ Required properties:
>> Optional properties:
>> - atmel,use-dma-rx: use of PDC or DMA for receiving data
>> - atmel,use-dma-tx: use of PDC or DMA for transmitting data
>> +- rts-gpios: specify a GPIO for RTS line. It will use specified PIO instead of the peripheral
>> + function pin for the USART RTS feature. If unsure, don't specify this property.
>> - add dma bindings for dma transfer:
>> - dmas: DMA specifier, consisting of a phandle to DMA controller node,
>> memory peripheral interface and USART DMA channel ID, FIFO configuration.
>> @@ -28,6 +30,7 @@ Example:
>> interrupts = <7>;
>> atmel,use-dma-rx;
>> atmel,use-dma-tx;
>> + rts-gpios = <&pioD 15 0>;
>> };
>
> gpios means 2 gpio
>
> I?ll rts-gpio as we can only use one anyway
Cf. Andrew's comment.
>> - use DMA:
>> diff --git a/drivers/tty/serial/atmel_serial.c b/drivers/tty/serial/atmel_serial.c
>> index b4e0794..71f8ea9 100644
>> --- a/drivers/tty/serial/atmel_serial.c
>> +++ b/drivers/tty/serial/atmel_serial.c
>> @@ -35,6 +35,7 @@
>> #include <linux/platform_device.h>
>> #include <linux/of.h>
>> #include <linux/of_device.h>
>> +#include <linux/of_gpio.h>
>> #include <linux/dma-mapping.h>
>> #include <linux/atmel_pdc.h>
>> #include <linux/atmel_serial.h>
>> @@ -2327,6 +2328,7 @@ static int atmel_serial_probe(struct platform_device *pdev)
>> struct device_node *np = pdev->dev.of_node;
>> struct atmel_uart_data *pdata = dev_get_platdata(&pdev->dev);
>> void *data;
>> + int rts_pin = -EINVAL;
>> int ret = -ENODEV;
>>
>> BUILD_BUG_ON(ATMEL_SERIAL_RINGSIZE & (ATMEL_SERIAL_RINGSIZE - 1));
>> @@ -2364,13 +2366,18 @@ static int atmel_serial_probe(struct platform_device *pdev)
>> * structs to indicate "no RTS GPIO" instead of open-coding some
>> * invalid value everywhere.
>> */
>> - if (pdata->rts_gpio > 0) {
>> - ret = devm_gpio_request(&pdev->dev, pdata->rts_gpio, "RTS");
>> + if (pdata && pdata->rts_gpio > 0)
>> + rts_pin = pdata->rts_gpio;
>> + else if (np)
>> + rts_pin = of_get_named_gpio(np, "rts-gpios", 0);
>> +
>
> use directly port->rts_gpio so we can drop the assign after
>
> if the gpio is invalid the port->rts_gpio need to be < 0 too
Yes this is definitively an option. I cook a v2 right now.
>
> Best Regards,
> J.
>
>> + if (gpio_is_valid(rts_pin)) {
>> + ret = devm_gpio_request(&pdev->dev, rts_pin, "RTS");
>> if (ret) {
>> dev_err(&pdev->dev, "error requesting RTS GPIO\n");
>> goto err;
>> }
>> - port->rts_gpio = pdata->rts_gpio;
>> + port->rts_gpio = rts_pin;
>> ret = gpio_direction_output(port->rts_gpio, 0);
>> if (ret) {
>> dev_err(&pdev->dev, "error setting up RTS GPIO\n");
>> --
>> 1.8.2.2
>>
>
>
>
--
Nicolas Ferre
next prev parent reply other threads:[~2013-11-05 16:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 12:35 [PATCH] ARM/serial: at91: switch atmel serial to use gpiolib Linus Walleij
2013-11-05 12:35 ` Linus Walleij
2013-11-05 15:27 ` Nicolas Ferre
2013-11-05 15:27 ` Nicolas Ferre
2013-11-05 15:29 ` [PATCH] ARM/serial: at91: specify RTS in DT using gpio Nicolas Ferre
2013-11-05 15:29 ` Nicolas Ferre
2013-11-05 15:59 ` Jean-Christophe PLAGNIOL-VILLARD
2013-11-05 15:59 ` Jean-Christophe PLAGNIOL-VILLARD
2013-11-05 16:18 ` Andrew Lunn
2013-11-05 16:18 ` Andrew Lunn
2013-11-05 16:57 ` Nicolas Ferre [this message]
2013-11-05 16:57 ` Nicolas Ferre
2013-11-05 17:29 ` [PATCH v2] " Nicolas Ferre
2013-11-05 17:29 ` Nicolas Ferre
2013-11-05 16:28 ` [PATCH] ARM/serial: at91: switch atmel serial to use gpiolib Jean-Christophe PLAGNIOL-VILLARD
2013-11-05 16:28 ` Jean-Christophe PLAGNIOL-VILLARD
2013-11-05 16:52 ` Nicolas Ferre
2013-11-05 16:52 ` Nicolas Ferre
2013-11-06 9:16 ` Linus Walleij
2013-11-06 9:16 ` Linus Walleij
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=52792361.6030803@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=acourbot@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.