mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <ahmad@a3f.at>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] include: <io.h>: define (read|write)[bwlq]_relaxed
Date: Fri, 11 Jun 2021 13:30:28 +0200	[thread overview]
Message-ID: <20210611113028.GC20470@pengutronix.de> (raw)
In-Reply-To: <20210611080155.3555976-1-ahmad@a3f.at>

On Fri, Jun 11, 2021 at 10:01:55AM +0200, Ahmad Fatoum wrote:
> For Linux, It's always correct to substitute any of the read or
> write _relaxed functions with their non relaxed counterpart.
> Define functions that do this.
> 
> Unlike with Linux, they doesn't per se affect performance: barebox
> writel doesn't imply memory barriers, instead it depends on
> the architecture support to map IO memory regions as non-bufferable.
> 
> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
> ---
>  drivers/clk/rockchip/clk.h        |  3 ---
>  drivers/gpio/gpio-davinci.c       |  3 ---
>  drivers/regulator/stm32-vrefbuf.c |  4 +---
>  drivers/spi/atmel-quadspi.c       |  3 ---
>  include/io.h                      | 32 +++++++++++++++++++++++++++++++
>  5 files changed, 33 insertions(+), 12 deletions(-)

Applied, thanks

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


      reply	other threads:[~2021-06-11 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11  8:01 Ahmad Fatoum
2021-06-11 11:30 ` Sascha Hauer [this message]

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=20210611113028.GC20470@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=ahmad@a3f.at \
    --cc=barebox@lists.infradead.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