From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 References: <20180725143850.32985-1-chris.brandt@renesas.com> <20180725143850.32985-2-chris.brandt@renesas.com> In-Reply-To: <20180725143850.32985-2-chris.brandt@renesas.com> From: Geert Uytterhoeven Date: Thu, 26 Jul 2018 13:31:27 +0200 Message-ID: Subject: Re: [PATCH v2 1/3] serial: sh-sci: Allow for compressed SCIF address space Content-Type: text/plain; charset="UTF-8" To: Chris Brandt Cc: Greg KH , Rob Herring , Mark Rutland , Geert Uytterhoeven , "open list:SERIAL DRIVERS" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux-Renesas , Simon Horman List-ID: Hi Chris, On Wed, Jul 25, 2018 at 4:39 PM Chris Brandt wrote: > Some devices with SCIx_SH4_SCIF_REGTYPE have no space between registers. > Use the register area size to determine the spacing between register. > > Signed-off-by: Chris Brandt Reviewed-by: Geert Uytterhoeven > --- a/drivers/tty/serial/sh-sci.c > +++ b/drivers/tty/serial/sh-sci.c > @@ -2869,6 +2869,10 @@ static int sci_init_single(struct platform_device *dev, > port->regshift = 1; > } > > + if (p->regtype == SCIx_SH4_SCIF_REGTYPE) > + if (sci_port->reg_size >= 0x20) > + port->regshift = 1; > + So you have to be careful not to round up the reg size in DT to the next power of two (0x20), like you did for RZ/A1 (64 is used there). Note that while no SH board file uses SCIx_SH4_SCIF_REGTYPE, it is the default reg type for PORT_SCIF, so some board files may be affected. However, they all set reg_size to 0x100, so this change should be OK. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds