On Wed, Jan 3, 2018 at 5:24 PM, Mark Brown <broonie@xxxxxxxxxx> wrote: > On Wed, Jan 03, 2018 at 12:17:07AM +0100, Linus Walleij wrote: > >> I'd be surprised if either performance or object code size is affected >> in a bad way though. I don't have any high-speed SPI devices I can test >> really, and loopback would require some special hardware set-up I >> don't have. > > You could just do something like spin on register reads on some device > or something? Something like dumping a regmap via debugfs would do the > trick probably. OK I tried this on my new Ilitek ILI9322 panel driver: A script like this dumping the regmap 10000 times (it has no caching obviously) on an otherwise idle system in two iterations before and after the patches: #!/bin/sh for run in `seq 10000` do cat /debug/regmap/spi0.0/registers > /dev/null done Before the patch: time test.sh real 3m 41.03s user 0m 29.41s sys 3m 7.22s time test.sh real 3m 44.24s user 0m 32.31s sys 3m 7.60s After the patch: time test.sh real 3m 41.32s user 0m 28.92s sys 3m 8.08s time test.sh real 3m 39.92s user 0m 30.20s sys 3m 5.56s So any performance differences seems to be in the error margin. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html