Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • F firmware
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 74
    • Issues 74
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 29
    • Merge requests 29
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • card10card10
  • firmware
  • Merge requests
  • !393

neither vibrate nor panic, if zero or negative values are passed to vibra.vibrate

  • Review changes

  • Download
  • Patches
  • Plain diff
Closed malte requested to merge mdik/firmware:vibrate-chill into master Jul 14, 2020
  • Overview 5
  • Commits 1
  • Pipelines 1
  • Changes 1

Is there a need for the vibration motor to go off the charts when vibra.vibrate gets passed a value < 1?

I hope not, and this should fix it? (I don't know, I have not installed the toolchain, yet to properly test it, but then it is also a pretty small change?)

Sincerely,

Malte

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: vibrate-chill