[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vd6OJ68BbaYt21hPpOpDbvT9pow6PSDhedGULjikGhoNg@mail.gmail.com>
Date: Wed, 28 Sep 2022 14:10:44 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc: Jiri Slaby <jirislaby@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-serial <linux-serial@...r.kernel.org>,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/4] Documentation: rs485: Mention uart_get_rs485_mode()
On Wed, Sep 28, 2022 at 2:05 PM Ilpo Järvinen
<ilpo.jarvinen@...ux.intel.com> wrote:
>
> Add to rs485 documentation that serial core prepares the struct
> serial_rs485 when uart_get_rs485_mode() is called. Remove the wrong
> claim that driver must fill it by itself.
the driver
...
> The device tree can also provide RS485 boot time parameters
> - [#DT-bindings]_. The driver is in charge of filling this data structure
> - from the values given by the device tree.
> + [#DT-bindings]_. The serial core fills the struct serial_rs485 from the
> + values given by the device tree when driver calls uart_get_rs485_mode().
the driver
Feels like this should be before the previous patch and actually have
a Fixes tag.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists