Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add max frequency parameter #400

Closed
wants to merge 1 commit into from
Closed

Conversation

crmdias
Copy link
Contributor

@crmdias crmdias commented Oct 4, 2024

Summary:
WHAT?
Add max frequency parameter to ts2phc command

WHY?
Avoid issues where device reports wrong max adjustment value (for instance, driver issues)

Considerations

  • Why math.Min(maxFreq, deviceFreq)??
    • I want to use the most restrictive value always, so that if device reports lower value, using this configuration does not cause invalid clock steps.

Reviewed By: leoleovich

Differential Revision: D63832053

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 4, 2024
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D63832053

crmdias added a commit to crmdias/time that referenced this pull request Oct 8, 2024
Summary:

WHAT?
Add max frequency parameter to ts2phc command

WHY?
Avoid issues where device reports wrong max adjustment value (for instance, driver issues)

Considerations
  - Why math.Min(maxFreq, deviceFreq)??
    - I want to use the most restrictive value always, so that if device reports lower value, using this configuration does not cause invalid clock steps.

Reviewed By: leoleovich

Differential Revision: D63832053
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D63832053

crmdias added a commit to crmdias/time that referenced this pull request Oct 9, 2024
Summary:

WHAT?
Add max frequency parameter to ts2phc command

WHY?
Avoid issues where device reports wrong max adjustment value (for instance, driver issues)

Considerations
  - Why math.Min(maxFreq, deviceFreq)??
    - I want to use the most restrictive value always, so that if device reports lower value, using this configuration does not cause invalid clock steps.

Reviewed By: leoleovich

Differential Revision: D63832053
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D63832053

crmdias added a commit to crmdias/time that referenced this pull request Oct 9, 2024
Summary:

WHAT?
Add max frequency parameter to ts2phc command

WHY?
Avoid issues where device reports wrong max adjustment value (for instance, driver issues)

Considerations
  - Why math.Min(maxFreq, deviceFreq)??
    - I want to use the most restrictive value always, so that if device reports lower value, using this configuration does not cause invalid clock steps.

Reviewed By: leoleovich

Differential Revision: D63832053
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D63832053

Summary:

WHAT?
Add max frequency parameter to ts2phc command

WHY?
Avoid issues where device reports wrong max adjustment value (for instance, driver issues)

Considerations
  - Why math.Min(maxFreq, deviceFreq)??
    - I want to use the most restrictive value always, so that if device reports lower value, using this configuration does not cause invalid clock steps.

Reviewed By: leoleovich

Differential Revision: D63832053
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D63832053

crmdias added a commit to crmdias/time that referenced this pull request Oct 9, 2024
Summary:

WHAT?
Add max frequency parameter to ts2phc command

WHY?
Avoid issues where device reports wrong max adjustment value (for instance, driver issues)

Considerations
  - Why math.Min(maxFreq, deviceFreq)??
    - I want to use the most restrictive value always, so that if device reports lower value, using this configuration does not cause invalid clock steps.

Reviewed By: leoleovich

Differential Revision: D63832053
@facebook-github-bot
Copy link
Contributor

This pull request has been merged in 0622257.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported Merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants