From: cyrille.pitchen@atmel•com (Cyrille Pitchen)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 2/4] tty/serial: at91: fix some macro definitions to fit coding style
Date: Thu, 2 Jul 2015 15:36:49 +0200 [thread overview]
Message-ID: <55953E71.4070109@atmel.com> (raw)
In-Reply-To: <11308515.NsBzDiA1lH@wuerfel>
Hi Arnd,
I've just sent a new series of patches to remove all those macros.
By the way, the patch dedicated to this update was created using coccinelle.
Based on Alexandre comment, I leave __raw_writel() and __raw_readl() for now.
Best Regards,
Cyrille
Le 30/06/2015 22:28, Arnd Bergmann a ?crit :
> 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.
>
> Arnd
>
next prev parent reply other threads:[~2015-07-02 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 14:05 [PATCH v3 0/4] tty/serial: at91: add support to FIFOs Cyrille Pitchen
2015-06-30 14:05 ` [PATCH v3 1/4] ARM: at91/dt: add a new DT property to support FIFOs on Atmel USARTs Cyrille Pitchen
2015-06-30 14:05 ` [PATCH v3 2/4] tty/serial: at91: fix some macro definitions to fit coding style Cyrille Pitchen
2015-06-30 20:28 ` Arnd Bergmann
2015-06-30 21:53 ` Alexandre Belloni
2015-07-02 13:36 ` Cyrille Pitchen [this message]
2015-06-30 14:05 ` [PATCH v3 3/4] tty/serial: at91: add support to FIFOs Cyrille Pitchen
2015-06-30 14:05 ` [PATCH v3 4/4] tty/serial: at91: use 32bit writes into TX FIFO when DMA is enabled Cyrille Pitchen
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=55953E71.4070109@atmel.com \
--to=cyrille.pitchen@atmel$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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