Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
F
FMC TDC 1ns 5cha - Software
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
image/svg+xml
Discourse
Discourse
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Projects
FMC TDC 1ns 5cha - Software
Commits
63ced64c
Commit
63ced64c
authored
Feb 17, 2015
by
Federico Vaga
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: improve doxygen documentation
Signed-off-by:
Federico Vaga
<
federico.vaga@cern.ch
>
parent
8ad4d965
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
78 additions
and
30 deletions
+78
-30
fmctdc-lib.c
lib/fmctdc-lib.c
+69
-27
fmctdc-lib.h
lib/fmctdc-lib.h
+9
-3
No files found.
lib/fmctdc-lib.c
View file @
63ced64c
This diff is collapsed.
Click to expand it.
lib/fmctdc-lib.h
View file @
63ced64c
...
...
@@ -35,9 +35,15 @@ struct fmctdc_board;
* FMC-TDC time-stamp descriptor
*/
struct
fmctdc_time
{
uint64_t
seconds
;
/**< number of seconds */
uint32_t
coarse
;
/**< number of ticks of 8ns */
uint32_t
frac
;
/**< number of frac of 81.03ps */
uint64_t
seconds
;
/**< TAI seconds. Note this is *not* an UTC time;
the counter does not support leap seconds. The
internal counter is also limited to 32 bits
(2038-error-prone). */
uint32_t
coarse
;
/**< number of ticks of 8ns since the beginning of
the last second*/
uint32_t
frac
;
/**< fractional part of an 8 ns tick, rescaled
to (0..4095) range - i.e. 0 = 0 ns, and
4095 = 7.999 ns. */
uint32_t
seq_id
;
/**< channel sequence number*/
uint32_t
gseq_id
;
/**< board sequence number */
uint32_t
ref_gseq_id
;
/**< board sequence number of the reference */
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment