[PATCH v3 00/16] Introduce and use generic parity16/32/64 helper
Jeremy Kerr
jk at ozlabs.org
Fri Apr 4 09:01:09 UTC 2025
Hi Kuan-Wei,
> Thanks for your feedback.
No problem!
> IIUC, from the fsi-i2c perspective, parity efficiency isn't a major
> concern,
Yes
> but you still prefer optimizing with methods like __builtin_parity().
No, it's not really about optimisation. In the case of this driver, my
preference would be more directed to using common code (either in the
form of these changes, or __builtin_parity) rather than any performance
considerations.
The implementation details I gave was more a note about the platforms
that are applicable for the driver.
Cheers,
Jeremy
More information about the dri-devel
mailing list