From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-serial <linux-serial@vger.kernel.org>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 2/3] serial: 8250_em: Update RZ/V2M port type as PORT_16750
Date: Fri, 10 Feb 2023 17:58:00 +0200 (EET) [thread overview]
Message-ID: <e1db071-963e-926-9119-9b405a1812cf@linux.intel.com> (raw)
In-Reply-To: <20230210154140.338352-3-biju.das.jz@bp.renesas.com>
On Fri, 10 Feb 2023, Biju Das wrote:
> The UART IP found on RZ/V2M SoC is Register-compatible with the
> general-purpose 16750 UART chip. This patch updates RZ/V2M
> port type from 16550A->16750 and also enables 64-bytes fifo support.
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> v2:
> * New patch
> ---
> drivers/tty/serial/8250/8250_em.c | 27 +++++++++++++++++++++++----
> 1 file changed, 23 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/tty/serial/8250/8250_em.c b/drivers/tty/serial/8250/8250_em.c
> index b78c74755735..628a6846bfdc 100644
> --- a/drivers/tty/serial/8250/8250_em.c
> +++ b/drivers/tty/serial/8250/8250_em.c
> @@ -9,6 +9,7 @@
> #include <linux/io.h>
> #include <linux/module.h>
> #include <linux/mod_devicetable.h>
> +#include <linux/of_device.h>
> #include <linux/serial_8250.h>
> #include <linux/serial_reg.h>
> #include <linux/platform_device.h>
> @@ -19,9 +20,15 @@
> #define UART_DLL_EM 9
> #define UART_DLM_EM 10
>
> +struct serial8250_em_hw_info {
> + unsigned int type;
> + upf_t flags;
> +};
> +
> struct serial8250_em_priv {
> struct clk *sclk;
> int line;
> + const struct serial8250_em_hw_info *info;
> };
>
> static void serial8250_em_serial_out(struct uart_port *p, int offset, int value)
> @@ -95,6 +102,7 @@ static int serial8250_em_probe(struct platform_device *pdev)
> if (!priv)
> return -ENOMEM;
>
> + priv->info = of_device_get_match_data(dev);
On second thought, do you even need to store the info beyond .probe()?
--
i.
next prev parent reply other threads:[~2023-02-10 15:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 15:41 [PATCH v2 0/3] pdate Renesas RZ/V2M UART Port type Biju Das
2023-02-10 15:41 ` [PATCH v2 1/3] serial: 8250_em: Use dev_err_probe() Biju Das
2023-02-10 16:48 ` Andy Shevchenko
2023-02-10 18:39 ` Geert Uytterhoeven
2023-02-10 19:18 ` Biju Das
2023-02-10 15:41 ` [PATCH v2 2/3] serial: 8250_em: Update RZ/V2M port type as PORT_16750 Biju Das
2023-02-10 15:54 ` Ilpo Järvinen
2023-02-10 15:58 ` Ilpo Järvinen [this message]
2023-02-10 16:02 ` Biju Das
2023-02-10 16:49 ` Andy Shevchenko
2023-02-10 19:20 ` Biju Das
2023-02-10 15:41 ` [PATCH v2 3/3] serial: 8250_em: Add serial_out() to struct serial8250_em_hw_info Biju Das
2023-02-10 15:52 ` Ilpo Järvinen
2023-02-10 16:01 ` Biju Das
2023-02-10 17:09 ` Ilpo Järvinen
2023-02-10 18:43 ` Geert Uytterhoeven
2023-02-10 19:15 ` Biju Das
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=e1db071-963e-926-9119-9b405a1812cf@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.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