From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
linux-serial@vger.kernel.org,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Fabrizio Castro" <fabrizio.castro.jz@renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v4 4/6] serial: 8250_em: Update port type as PORT_16750
Date: Fri, 17 Feb 2023 16:06:38 +0200 [thread overview]
Message-ID: <Y++J7u5SY5Z5Z857@smile.fi.intel.com> (raw)
In-Reply-To: <20230217114255.226517-5-biju.das.jz@bp.renesas.com>
On Fri, Feb 17, 2023 at 11:42:53AM +0000, Biju Das wrote:
> The UART IP found on {RZ/V2M, EMMA mobile} SoC is Register-compatible
> with the general-purpose 16750 UART chip. This patch updates port type
> from 16550A->16750 and also enables 64-bytes fifo support.
...
> + up.port.flags = UPF_BOOT_AUTOCONF | UPF_FIXED_PORT | UPF_IOREMAP | UPF_FIXED_TYPE;
Do you still need UPF_BOOT_AUTOCONF?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-02-17 14:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 11:42 [PATCH v4 0/6] Update Renesas {EMMA mobile, RZ/V2M} UART Port type Biju Das
2023-02-17 11:42 ` [PATCH v4 1/6] serial: 8250_em: Use dev_err_probe() Biju Das
2023-02-17 14:03 ` Andy Shevchenko
2023-02-17 14:14 ` Biju Das
2023-02-17 11:42 ` [PATCH v4 2/6] serial: 8250_em: Drop slab.h Biju Das
2023-02-17 14:05 ` Andy Shevchenko
2023-02-17 14:30 ` Biju Das
2023-02-17 15:13 ` Andy Shevchenko
2023-02-17 15:17 ` Biju Das
2023-02-17 11:42 ` [PATCH v4 3/6] serial: 8250_em: Use devm_clk_get_enabled() Biju Das
2023-02-17 11:42 ` [PATCH v4 4/6] serial: 8250_em: Update port type as PORT_16750 Biju Das
2023-02-17 14:06 ` Andy Shevchenko [this message]
2023-02-17 14:53 ` Biju Das
2023-02-17 11:42 ` [PATCH v4 5/6] serial: 8250_em: Use pseudo offset for UART_FCR Biju Das
2023-02-17 11:46 ` Ilpo Järvinen
2023-02-17 11:56 ` Biju Das
2023-02-17 12:00 ` Ilpo Järvinen
2023-02-17 12:11 ` Biju Das
2023-02-17 12:42 ` Ilpo Järvinen
2023-02-17 12:58 ` Biju Das
2023-02-17 13:03 ` Ilpo Järvinen
2023-02-17 11:42 ` [PATCH v4 6/6] serial: 8250_em: Add serial8250_em_{reg_update(),out_helper()} Biju Das
2023-02-17 14:14 ` Andy Shevchenko
2023-02-17 14:35 ` Biju Das
2023-02-17 15:15 ` Andy Shevchenko
2023-02-17 15:24 ` 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=Y++J7u5SY5Z5Z857@smile.fi.intel.com \
--to=andriy.shevchenko@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 \
--cc=niklas.soderlund@ragnatech.se \
/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;
as well as URLs for NNTP newsgroup(s).