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>,
linux-serial <linux-serial@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH v2 3/3] serial: 8250_em: Add serial_out() to struct serial8250_em_hw_info
Date: Fri, 10 Feb 2023 19:09:02 +0200 (EET) [thread overview]
Message-ID: <4c78b3bd-ef1-5015-8269-b0c2c3c8d592@linux.intel.com> (raw)
In-Reply-To: <OS0PR01MB592222F997B7CB5976B7618186DE9@OS0PR01MB5922.jpnprd01.prod.outlook.com>
On Fri, 10 Feb 2023, Biju Das wrote:
> Hi Ilpo,
>
> Thanks for the update.
>
> > Subject: Re: [PATCH v2 3/3] serial: 8250_em: Add serial_out() to struct
> > serial8250_em_hw_info
> >
> > On Fri, 10 Feb 2023, 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.
> > >
> > > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> > > ---
> > > v1->v2:
> > > * Added serial_out to struct serial8250_em_hw_info
> >
> > Thanks, this looks much better. One additional comment below.
> >
> > > ---
> > > drivers/tty/serial/8250/8250_em.c | 59
> > > ++++++++++++++++++++++++++++++-
> > > 1 file changed, 58 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/tty/serial/8250/8250_em.c
> > > b/drivers/tty/serial/8250/8250_em.c
> > > index 628a6846bfdc..1816362a3a3a 100644
> > > --- a/drivers/tty/serial/8250/8250_em.c
> > > +++ b/drivers/tty/serial/8250/8250_em.c
> > > @@ -19,10 +19,14 @@
> > >
> > > #define UART_DLL_EM 9
> > > #define UART_DLM_EM 10
> > > +#define UART_HCR0 11
> > > +
> > > +#define UART_HCR0_SW_RESET BIT(7) /* SW Reset */
> > >
> > > struct serial8250_em_hw_info {
> > > unsigned int type;
> > > upf_t flags;
> > > + void (*serial_out)(struct uart_port *p, int off, int value);
> > > };
> > >
> > > struct serial8250_em_priv {
> > > @@ -31,6 +35,40 @@ struct serial8250_em_priv {
> > > const struct serial8250_em_hw_info *info; };
> > >
> > > +static void serial8250_rzv2m_reg_update(struct uart_port *p, int off,
> > > +int value) {
> > > + unsigned int ier, fcr, lcr, mcr, hcr0;
> > > +
> > > + ier = readl(p->membase + (UART_IER << 2));
> > > + hcr0 = readl(p->membase + (UART_HCR0 << 2));
> > > + fcr = readl(p->membase + ((UART_FCR + 1) << 2));
> > > + lcr = readl(p->membase + ((UART_LCR + 1) << 2));
> > > + mcr = readl(p->membase + ((UART_MCR + 1) << 2));
> > > +
> > > + writel(fcr | UART_FCR_CLEAR_RCVR | UART_FCR_CLEAR_XMIT,
> > > + p->membase + ((UART_FCR + 1) << 2));
> > > + writel(hcr0 | UART_HCR0_SW_RESET, p->membase + (UART_HCR0 << 2));
> > > + writel(hcr0 & ~UART_HCR0_SW_RESET, p->membase + (UART_HCR0 << 2));
> > > +
> > > + switch (off) {
> > > + case UART_FCR:
> > > + fcr = value;
> > > + break;
> > > + case UART_LCR:
> > > + lcr = value;
> > > + break;
> > > + case UART_MCR:
> > > + mcr = value;
> > > + break;
> > > + }
> > > +
> > > + writel(ier, p->membase + (UART_IER << 2));
> > > + writel(fcr, p->membase + ((UART_FCR + 1) << 2));
> > > + writel(mcr, p->membase + ((UART_MCR + 1) << 2));
> > > + writel(lcr, p->membase + ((UART_LCR + 1) << 2));
> > > + writel(hcr0, p->membase + (UART_HCR0 << 2));
> >
> > Perhaps it would make sense to instead of using readl/writel() directly to
> > call serial8250_em_serial_in/out() so all the offset trickery wouldn't need
> > to be duplicated inside this function?
>
> HCR0 register is not available for emma mobile. Is it ok if I just do readl/writel for
> that register and rest will use serial8250_em_serial_in/out()??
Yes, it's fine.
--
i.
next prev parent reply other threads:[~2023-02-10 17:13 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
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 [this message]
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=4c78b3bd-ef1-5015-8269-b0c2c3c8d592@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