On 2018-03-20 06:23, Christoph Hellwig wrote:
This is a basically unmaintained driver for historic hardware, and not
the
right place for micro-optimizations.
Sure, I can drop this on the next version.
This is a basically unmaintained driver for historic hardware, and not the
right place for micro-optimizations.
Code includes barrier() followed by writel(). writel() already has a
barrier
on some architectures like arm64.
This ends up CPU observing two barriers back to back before executing the
register write.
Since code already has an explicit barrier call, changing writel() to
writel_relaxed().
Signed-
3 matches
Mail list logo
