Hi, On Tue, Nov 17, 2020 at 4:07 PM Robin Murphy <robin.murphy@xxxxxxx> wrote: > > On 2020-11-16 18:54, Rob Herring wrote: > > On Thu, Oct 22, 2020 at 1:18 AM Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx> wrote: > >> ... > > IMO if this is like PL330 where you just stick some raw AXI attributes > in a register and that's what goes out on transactions then it's not > really part of the platform description anyway, it's just driver policy. > If folks want to tweak the driver's behaviour for secret SoC-specific > performance optimisation, then give them some module parameters or a > sysfs interface. I'm assuming this has to be purely a performance thing, > because I can't see how two different integrations could reasonably > depend on different baseline attributes for correctness, and even if > they did then you'd be able to determine that from the compatible > strings, because they would be different, because those integrations > would be fundamentally *not* compatible with each other. > So, I checked internally where we get this requirement and it seems you are right. I'm dropping the Dt bindings and in fact the ability to customize those attributes beyond the basic coherent/non coherent configuration which we already support and will just update the setting to what we think is best. Thanks for clearing this up. Gilad -- Gilad Ben-Yossef Chief Coffee Drinker values of β will give rise to dom!
