linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Hyunki Koo" <hyunki00.koo@samsung.com>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>
Cc: linux-samsung-soc@vger.kernel.org, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, 'Kukjin Kim' <kgene@kernel.org>,
	linux-serial@vger.kernel.org, 'Jiri Slaby' <jslaby@suse.com>,
	linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH v3] tty: samsung_tty: 32-bit access for TX/RX hold registers
Date: Fri, 3 Apr 2020 20:12:55 +0900	[thread overview]
Message-ID: <005601d609a8$d3243710$796ca530$@samsung.com> (raw)
In-Reply-To: <20200403104744.GA29385@kozik-lap>

On Thu, Apr 02, 2020 at 7:48:38PM +0900, Krzysztof Kozlowski
> On Fri, Apr 03, 2020 at 07:20:41PM +0900, Hyunki Koo wrote:
> > Support 32-bit access for the TX/RX hold registers UTXH and URXH.
> >
> > This is required for some newer SoCs.
> >
> > Signed-off-by: Hyunki Koo <hyunki00.koo@samsung.com>
> > ---
> > v3: change rd_regl to rd_reg in line 954 for backward compatibility.
> 
> I cannot find this change against v2.
Okay, I will add all changes.
> 
> > ---
> >
> >  drivers/tty/serial/samsung_tty.c | 76
> > +++++++++++++++++++++++++++++++++-------
> >  1 file changed, 64 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/tty/serial/samsung_tty.c
> > b/drivers/tty/serial/samsung_tty.c
> > index 73f951d65b93..a674a80163ed 100644
> > --- a/drivers/tty/serial/samsung_tty.c
> > +++ b/drivers/tty/serial/samsung_tty.c
> > @@ -154,12 +154,47 @@ struct s3c24xx_uart_port {  #define
> > portaddrl(port, reg) \
> >  	((unsigned long *)(unsigned long)((port)->membase + (reg)))
> >
> > -#define rd_regb(port, reg) (readb_relaxed(portaddr(port, reg)))
> > +static unsigned int rd_reg(struct uart_port *port, int reg)
> 
> You should return here u32 to be consistent with readl_relaxed.
> 
> > +{
> > +	switch (port->iotype) {
> > +	case UPIO_MEM:
> > +		return readb_relaxed(portaddr(port, reg));
> > +	case UPIO_MEM32:
> > +		return readl_relaxed(portaddr(port, reg));
> > +	default:
> > +		return 0;
> > +	}
> > +	return 0;
> > +}
> > +
> >  #define rd_regl(port, reg) (readl_relaxed(portaddr(port, reg)))
> >
> > -#define wr_regb(port, reg, val) writeb_relaxed(val, portaddr(port,
> > reg))
> > +static void wr_reg(struct uart_port *port, int reg, int val)
> 
> val should be u32.
Okay, I will apply it.
> 
> > +{
> > +	switch (port->iotype) {
> > +	case UPIO_MEM:
> > +		writeb_relaxed(val, portaddr(port, reg));
> > +		break;
> > +	case UPIO_MEM32:
> > +		writel_relaxed(val, portaddr(port, reg));
> > +		break;
> > +	}
> > +}
> > +
> >  #define wr_regl(port, reg, val) writel_relaxed(val, portaddr(port,
> > reg))
> >
> > +static void write_buf(struct uart_port *port, int reg, int val)
> 
> buf is misleading, you do not write here any buffer. Maybe
> "wr_reg_barrier()" or "wr_reg_order()"?
Okay, wr_reg_barrier  would be good, I will apply it.
> 
> Best regards,
> Krzysztof




_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-04-03 11:13 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200401082749epcas2p2a774da515805bc3f761b6b5a8dc9e3d2@epcas2p2.samsung.com>
2020-04-01  8:27 ` [PATCH] tty: samsung_tty: 32-bit access for TX/RX hold registers Hyunki Koo
2020-04-01  8:55   ` Greg Kroah-Hartman
2020-04-01  9:19     ` Krzysztof Kozlowski
2020-04-02  9:44       ` Hyunki Koo
2020-04-02  9:48         ` 'Krzysztof Kozlowski'
2020-04-02 11:04   ` [PATCH v2] " Hyunki Koo
2020-04-02 12:18     ` Greg KH
2020-04-02 13:59     ` Krzysztof Kozlowski
2020-04-03  7:30       ` Hyunki Koo
2020-04-03  7:51         ` 'Krzysztof Kozlowski'
2020-04-03 10:19           ` Hyunki Koo
2020-04-03 10:20   ` [PATCH v3] " Hyunki Koo
2020-04-03 10:47     ` Krzysztof Kozlowski
2020-04-03 11:12       ` Hyunki Koo [this message]
2020-04-03 11:39         ` 'Krzysztof Kozlowski'
2020-04-03 11:15   ` [PATCH v4] " Hyunki Koo
2020-04-03 11:42     ` Greg KH
2020-04-03 11:53       ` Krzysztof Kozlowski
2020-04-03 11:57         ` Greg KH
2020-04-03 12:08           ` Krzysztof Kozlowski
2020-04-03 11:59     ` Krzysztof Kozlowski
2020-04-05 21:35       ` Hyunki Koo
2020-04-06  9:54         ` 'Krzysztof Kozlowski'
2020-04-03 13:34     ` Krzysztof Kozlowski
2020-04-05 21:41       ` Hyunki Koo
2020-04-06  9:53         ` 'Krzysztof Kozlowski'
2020-04-06 10:31   ` [PATCH v5 2/2] " Hyunki Koo
2020-04-06 10:34     ` Krzysztof Kozlowski
2020-04-06 23:08   ` [PATCH v6 " Hyunki Koo
2020-04-07  4:49     ` Jiri Slaby
2020-04-07  6:02       ` Hyunki Koo
2020-04-07  6:24       ` Krzysztof Kozlowski
2020-04-07  6:32         ` Jiri Slaby
2020-04-07  7:22           ` Krzysztof Kozlowski
2020-04-07  6:26     ` Krzysztof Kozlowski
2020-04-07  6:28       ` Jiri Slaby
2020-04-07  6:37         ` Jiri Slaby
2020-04-07  6:54       ` Hyunki Koo

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='005601d609a8$d3243710$796ca530$@samsung.com' \
    --to=hyunki00.koo@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=kgene@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-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;
as well as URLs for NNTP newsgroup(s).