On Mon, Sep 7, 2015 at 1:44 PM, ferran <ranker72@xxxxxxxxx> wrote: > > So firstly, why can't I call drv_get_tsf from there? Is it because TSF > is exactly then being reset? Secondly, I feel unsafe about You left out posting the actual panic/warning you got, but one possibility is beacon_get is called under a lock that the driver also takes inside drv_get_tsf(). Usually this function just reads a register so it's unlikely that reading the tsf itself during an update will give any troubles (other than wrong values). > Finally, I would be interested on using TSF to measure the time passed > since a packet is scheduled to transmit in tx.c and its report is > received at status.c. Do you think that TSF be usable for this? I am not sure what you want to do, but some things to think about regarding TSF: - reading the TSF from the driver with drv_get_tsf() will give you something that may or may not be usable. For example, depending on calling context, the process that reads the TSF might get scheduled out for an unknown amount of time between when you read it and when you use it. - in mesh, the TSF changes as the network operates. The stations try to adjust their clocks so that their timing offsets are synchronized (making it possible to know a neighbor's TBTT). -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
