From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] tty/serial_core: Introduce lock mechanism for RS485
Date: Mon, 13 Oct 2014 23:48:05 +0200 [thread overview]
Message-ID: <543C4895.4000902@atmel.com> (raw)
In-Reply-To: <CAPybu_1kwSRfe33H9cFO_DgstP8VW=z_AcqZhhs0iQX89Mmbag@mail.gmail.com>
On 13/10/2014 21:03, Ricardo Ribalda Delgado :
> Hello Nicolas
>
>>
>> I have the feeling that moving the code chunk that uses this new
>> variable (rs485_enabled) here ...
>>
>>> ret = uart_add_one_port(&atmel_uart, &port->uart);
>>> if (ret)
>>> goto err_add_port;
>>> @@ -2574,7 +2572,7 @@ static int atmel_serial_probe(struct platform_device *pdev)
>>> device_init_wakeup(&pdev->dev, 1);
>>> platform_set_drvdata(pdev, port);
>>>
>>> - if (port->uart.rs485.flags & SER_RS485_ENABLED) {
>>> + if (rs485_enabled) {
>>> UART_PUT_MR(&port->uart, ATMEL_US_USMODE_NORMAL);
>>> UART_PUT_CR(&port->uart, ATMEL_US_RTSEN);
>>> }
>>
>> ... (this one ^^^) up where you can test the SER_RS485_ENABLED, can be
>> even simpler.
>>
>> otherwise, it seems good so you can add my:
>>
>> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>>
>> Thanks.
>
> I supposed that the code needs to be initialized with rs485 disabled
> and then enable it. Also I did not want to change the behaviour a
> driver in a patch that involves 3 other drivers. If you don't mind I
> prefer that this is added to a separated patch.
Fair enough, I can do it later on.
Thanks, bye,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
<linux-serial@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
"One Thousand Gnomes" <gnomes@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] tty/serial_core: Introduce lock mechanism for RS485
Date: Mon, 13 Oct 2014 23:48:05 +0200 [thread overview]
Message-ID: <543C4895.4000902@atmel.com> (raw)
In-Reply-To: <CAPybu_1kwSRfe33H9cFO_DgstP8VW=z_AcqZhhs0iQX89Mmbag@mail.gmail.com>
On 13/10/2014 21:03, Ricardo Ribalda Delgado :
> Hello Nicolas
>
>>
>> I have the feeling that moving the code chunk that uses this new
>> variable (rs485_enabled) here ...
>>
>>> ret = uart_add_one_port(&atmel_uart, &port->uart);
>>> if (ret)
>>> goto err_add_port;
>>> @@ -2574,7 +2572,7 @@ static int atmel_serial_probe(struct platform_device *pdev)
>>> device_init_wakeup(&pdev->dev, 1);
>>> platform_set_drvdata(pdev, port);
>>>
>>> - if (port->uart.rs485.flags & SER_RS485_ENABLED) {
>>> + if (rs485_enabled) {
>>> UART_PUT_MR(&port->uart, ATMEL_US_USMODE_NORMAL);
>>> UART_PUT_CR(&port->uart, ATMEL_US_RTSEN);
>>> }
>>
>> ... (this one ^^^) up where you can test the SER_RS485_ENABLED, can be
>> even simpler.
>>
>> otherwise, it seems good so you can add my:
>>
>> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>>
>> Thanks.
>
> I supposed that the code needs to be initialized with rs485 disabled
> and then enable it. Also I did not want to change the behaviour a
> driver in a patch that involves 3 other drivers. If you don't mind I
> prefer that this is added to a separated patch.
Fair enough, I can do it later on.
Thanks, bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2014-10-13 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 13:38 [PATCH] tty/serial_core: Introduce lock mechanism for RS485 Ricardo Ribalda Delgado
2014-10-12 5:23 ` Nicolas Ferre
2014-10-12 5:23 ` Nicolas Ferre
2014-10-13 19:03 ` Ricardo Ribalda Delgado
2014-10-13 21:48 ` Nicolas Ferre [this message]
2014-10-13 21:48 ` Nicolas Ferre
2014-10-13 13:52 ` One Thousand Gnomes
2014-10-13 19:02 ` Ricardo Ribalda Delgado
-- strict thread matches above, loose matches on Subject: below --
2014-10-16 9:04 Ricardo Ribalda Delgado
2014-10-16 9:06 ` Ricardo Ribalda Delgado
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=543C4895.4000902@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=ricardo.ribalda@gmail.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.