Skip to content

fix(lvgl_tick): correct lvgl timer configuration.#295

Merged
sunzhen222 merged 1 commit intomainfrom
fix/lvgl_tick
Apr 17, 2025
Merged

fix(lvgl_tick): correct lvgl timer configuration.#295
sunzhen222 merged 1 commit intomainfrom
fix/lvgl_tick

Conversation

@sunzhen222
Copy link
Copy Markdown
Contributor

@sunzhen222 sunzhen222 commented Apr 17, 2025

Summary by CodeRabbit

  • Refactor
    • Updated timer configuration to trigger every 2 ms instead of 1 ms, improving timing consistency.
    • Timer tick increment now matches the new timer period for more accurate time tracking.

@sunzhen222 sunzhen222 requested a review from a team as a code owner April 17, 2025 03:21
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 17, 2025

Walkthrough

The timer setup in timer.c was updated to use a prescaler of 1000 and a configurable period defined by LVGL_TIMER_PERIOD_MS, now set to 2 ms. The interrupt now fires every 2 ms, and the tick increment matches this period. The callback checks for TIM4 before incrementing the tick.

Changes

File(s) Change Summary
core/embed/trezorhal/timer.c Updated timer prescaler and period logic, and adjusted tick increment

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🔭 Outside diff range comments (1)
core/embed/trezorhal/timer.c (1)

22-23: ⚠️ Potential issue

Empty if block.

Missing error handling.

🧹 Nitpick comments (2)
core/embed/trezorhal/timer.c (2)

5-6: Missing comment.

No explanation for 2ms choice.


15-17: Formula is complex.

Magic number 2 * 1000 needs clarification.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b37a61c and 123d372.

📒 Files selected for processing (1)
  • core/embed/trezorhal/timer.c (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Gen check
  • GitHub Check: Style check
  • GitHub Check: Defs check
🔇 Additional comments (1)
core/embed/trezorhal/timer.c (1)

37-42: Good check added.

TIM4 instance verification improves robustness.

@sunzhen222 sunzhen222 merged commit 6decb51 into main Apr 17, 2025
9 checks passed
@sunzhen222 sunzhen222 deleted the fix/lvgl_tick branch April 17, 2025 03:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants