12:11 a.m.
On Tue, Dec 07, 2021 at 12:32:52PM +0100, Nicolas Frattaroli wrote:
So my question is: do I need to care about this? This hardware
will never be used on MIPS, and a lot of other drivers (as seen in
the errors snippet from the test robot) have the same issue, and
the problem is most likely not in my driver but in that specific
configuration's clock API implementation.
It's fine, in theory you should care and add suitable dependencies but
in practice it's not bothering anyone and at this point I'd rather see
this sorted on the MIPS side, supporting things like this is just
ongoing hassle.