On Tue, Aug 20, 2019 at 04:48:39PM +0300, Vladimir Oltean wrote: > On Tue, 20 Aug 2019 at 15:55, Mark Brown <broonie@xxxxxxxxxx> wrote: > > On Fri, Aug 16, 2019 at 05:05:53PM +0300, Vladimir Oltean wrote: > > > Maybe the SPI master driver should just report what sort of > > > snapshotting capability it can offer, ranging from none (default > > > unless otherwise specified), to transfer-level (DMA style) or > > > byte-level. > > That does then have the consequence that the majority of controllers > > aren't going to be usable with the API which isn't great. > Can we continue this discussion on this thread: > https://www.spinics.net/lists/netdev/msg593772.html > The whole point there is that if there's nothing that the driver can > do, the SPI core will take the timestamps and record their (bad) > precision. I'm not on that thread. > > I'm not 100% clear what the problem you're trying to solve is, or if > > it's a sensible problem to try to solve for that matter. > The problem can simply be summarized as: you're trying to read a clock > over SPI, but there's so much timing jitter in you doing that, that > you have a high degree of uncertainty in the actual precision of the > readout you took. That doesn't seem like a great idea...
Attachment:
signature.asc
Description: PGP signature
