Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
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>,
	Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v3 3/3] serial: 8250_em: Add serial_out() to struct serial8250_em_hw_info
Date: Sun, 12 Feb 2023 13:09:56 +0200	[thread overview]
Message-ID: <Y+jJBER9x4wMS5U1@smile.fi.intel.com> (raw)
In-Reply-To: <20230210203439.174913-4-biju.das.jz@bp.renesas.com>

On Fri, Feb 10, 2023 at 08:34:39PM +0000, Biju Das wrote:
> As per HW manual section 40.6.1, we need to perform FIFO reset + SW
> reset before updating the below registers.
> 
> FCR[7:5], FCR[3:0], LCR[7][5:0], MCR[6:4], DLL[7:0], DLM[7:0] and
> HCR0[6:5][3:2].
> 
> This patch adds serial_out() to struct serial8250_em_hw_info to
> handle this difference between emma mobile and rz/v2m.
> 
> DLL/DLM register can be updated only by setting LCR[7]. So the
> updation of LCR[7] will perform reset for DLL/DLM register changes.

...

>  #define UART_DLL_EM 9
>  #define UART_DLM_EM 10
> +#define UART_HCR0 11

Can we continue using _EM suffix?

...

> +	/*
> +	 * The value of UART_IIR and UART_FCR are 2, but corresponding
> +	 * RZ/V2M address offset are different(0x08 and 0x0c). So we need to
> +	 * use readl() here.
> +	 */
> +	fcr = readl(p->membase + ((UART_FCR + 1) << 2));

So, what does prevent you to define above

#define UART_IIR_EM	3 // or whatever name it should have

and use again same helper here?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-02-12 11:10 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 20:34 [PATCH v3 0/3] Update Renesas RZ/V2M UART Port type Biju Das
2023-02-10 20:34 ` [PATCH v3 1/3] serial: 8250_em: Use dev_err_probe() Biju Das
2023-02-13  6:23   ` Jiri Slaby
2023-02-14 11:07     ` Biju Das
2023-02-10 20:34 ` [PATCH v3 2/3] serial: 8250_em: Update RZ/V2M port type as PORT_16750 Biju Das
2023-02-12 11:02   ` Andy Shevchenko
2023-02-13  6:26   ` Jiri Slaby
2023-02-13 16:02     ` Biju Das
2023-02-10 20:34 ` [PATCH v3 3/3] serial: 8250_em: Add serial_out() to struct serial8250_em_hw_info Biju Das
2023-02-12 11:09   ` Andy Shevchenko [this message]
2023-02-13  8:42   ` Ilpo Järvinen
2023-02-13  8:53     ` Biju Das
2023-02-13  9:10       ` Jiri Slaby
2023-02-13  9:12         ` Jiri Slaby
2023-02-13  9:14           ` Jiri Slaby
2023-02-13  9:31             ` Biju Das
2023-02-13  9:32               ` Jiri Slaby
2023-02-13 11:12                 ` Biju Das
2023-02-13 11:31                   ` Ilpo Järvinen
2023-02-13 11:40                     ` Biju Das
2023-02-13 12:05                       ` Ilpo Järvinen
2023-02-13 12:18                         ` Biju Das
2023-02-13 16:06                           ` Biju Das
2023-02-13  9:57               ` Niklas Söderlund
2023-02-13 10:06                 ` Biju Das
2023-02-13 10:29                   ` Niklas Söderlund
2023-02-13 13:01                     ` Biju Das
2023-02-13 14:09                       ` Niklas Söderlund
2023-02-13 14:26                         ` Biju Das
2023-02-13  9:22           ` Ilpo Järvinen
2023-02-13  9:28             ` Jiri Slaby
2023-02-13  9:40               ` Ilpo Järvinen
2023-02-13  9:53                 ` Jiri Slaby
2023-02-13  9:12       ` Ilpo Järvinen
2023-02-13  8:37 ` [PATCH v3 0/3] Update Renesas RZ/V2M UART Port type Ilpo Järvinen

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+jJBER9x4wMS5U1@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 \
    /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