[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150630215319.GM485@piout.net>
Date: Tue, 30 Jun 2015 23:53:19 +0200
From: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Cyrille Pitchen <cyrille.pitchen@...el.com>,
nicolas.ferre@...el.com, gregkh@...uxfoundation.org,
wenyou.yang@...el.com, ludovic.desroches@...el.com,
leilei.zhao@...el.com, josh.wu@...el.com,
linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
galak@...eaurora.org, ijc+devicetree@...lion.org.uk,
mark.rutland@....com, pawel.moll@....com, robh+dt@...nel.org
Subject: Re: [PATCH v3 2/4] tty/serial: at91: fix some macro definitions to
fit coding style
On 30/06/2015 at 22:28:42 +0200, Arnd Bergmann wrote :
> On Tuesday 30 June 2015 16:05:15 Cyrille Pitchen wrote:
> > +#define UART_PUT_CR(port, v) __raw_writel(v, (port)->membase + ATMEL_US_CR)
> > +#define UART_GET_MR(port) __raw_readl((port)->membase + ATMEL_US_MR)
> > +#define UART_PUT_MR(port, v) __raw_writel(v, (port)->membase + ATMEL_US_MR)
> > +#define UART_PUT_IER(port, v) __raw_writel(v, (port)->membase + ATMEL_US_IER)
> >
>
> How about removing these macros entirely? I'm not aware of other drivers
> doing it like this, and it does not seem to add any value?
>
> At the same time, you could use readl_relaxed() to make the driver
> endian-safe.
>
I think using readl_relaxed() would break avr32.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists