Re: [RFT PATCH v3 12/27] of/address: Add infrastructure to declare MMIO as non-posted

From
Linus Walleij <hidden>
Date
2021-03-09 15:41:00
Also in
linux-arch, linux-arm-kernel, linux-devicetree, linux-samsung-soc, linux-serial, lkml
Reply to
Arnd Bergmann, 2021-03-09
On Tue, Mar 9, 2021 at 1:41 PM Arnd Bergmann [off-list ref] wrote:
quoted hunk ↗ jump to hunk
- A driver writer may want to choose between posted and
  nonposted mmio based on performance considerations:
  if writes are never serialized, posted writes should always
  be faster. However, if the driver uses a spinlock to serialize
  writes, then a nonposted write is likely faster than a posted
  write followed by a read that serializes the spin_unlock.
  In this case we want the driver to explicitly pick one over
  the other, and not have rely on bus specific magic.
OK then I am all for having drivers explicitly choose access
method. Openness to speed optimization is a well established
Linux kernel design principle.

Yours,
Linus Walleij
Thread (134 messages) 134 messages, 10 authors, last reply 2021-04-01
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help