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

fix(eth): Set default clock in pin value to zero #10513

Merged
merged 1 commit into from
Oct 23, 2024

Conversation

me-no-dev
Copy link
Member

@me-no-dev me-no-dev commented Oct 23, 2024

When Arduino is used as component, CONFIG_ETH_RMII_CLK_IN_GPIO might not be defined, so we set it to const 0 to clear the issue.

Fixes: #10440

When Arduino is used as component, `CONFIG_ETH_RMII_CLK_IN_GPIO` might not be defined, so we set it to const `0` to clear the issue.
Copy link
Contributor

github-actions bot commented Oct 23, 2024

Warnings
⚠️

Some issues found for the commit messages in this PR:

  • the commit message "fix(eth): Set default clock in pin value to zero":
    • body's lines must not be longer than 100 characters

Please fix these commit messages - here are some basic tips:

  • follow Conventional Commits style
  • correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue
  • allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test
  • sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter
  • avoid Jira references in commit messages (unavailable/irrelevant for our customers)

TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).

⚠️
	The **target branch** for this Pull Request **must be the default branch** of the project (`master`).

	If you would like to add this feature to a different branch, please state this in the PR description and we will consider it.

👋 Hello me-no-dev, we appreciate your contribution to this project!


Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 62d2441

Copy link
Contributor

Memory usage test (comparing PR against master branch)

The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.

MemoryFLASH [bytes]FLASH [%]RAM [bytes]RAM [%]
TargetDECINCDECINCDECINCDECINC
ESP32P4000.000.00000.000.00
ESP32S30‼️ +17K0.00‼️ +2.680‼️ +2K0.00‼️ +8.27
ESP32S20‼️ +14K0.00‼️ +2.260‼️ +2K0.00‼️ +8.80
ESP32C30‼️ +20K0.00‼️ +3.260‼️ +2K0.00‼️ +10.32
ESP32C60‼️ +35K0.00‼️ +3.880‼️ +22K0.00‼️ +127.95
ESP32H20‼️ +11K0.00‼️ +2.070‼️ +22K0.00‼️ +126.07
ESP320‼️ +14K0.00‼️ +2.080⚠️ +13680.00‼️ +3.19
Click to expand the detailed deltas report [usage change in BYTES]
TargetESP32P4ESP32S3ESP32S2ESP32C3ESP32C6ESP32H2ESP32
ExampleFLASHRAMFLASHRAMFLASHRAMFLASHRAMFLASHRAMFLASHRAMFLASHRAM
Ethernet/examples/ETH_TLK110------------‼️ +10K⚠️ +800
Ethernet/examples/ETH_W5500_Arduino_SPI--‼️ +14K⚠️ +1940‼️ +12K⚠️ +1668‼️ +17K⚠️ +1744‼️ +19K‼️ +22K‼️ +11K‼️ +22K‼️ +8K⚠️ +736
Ethernet/examples/ETH_W5500_IDF_SPI--‼️ +14K⚠️ +1908‼️ +11K⚠️ +1620‼️ +17K⚠️ +1744‼️ +19K‼️ +22K‼️ +11K‼️ +22K‼️ +7K⚠️ +672
Ethernet/examples/ETH_WIFI_BRIDGE--‼️ +17K‼️ +2K‼️ +14K‼️ +2K‼️ +20K‼️ +2K‼️ +35K‼️ +4K--‼️ +14K⚠️ +1368
Ethernet/examples/ETH_LAN8720------------‼️ +10K⚠️ +800

@me-no-dev me-no-dev added the Status: Pending Merge Pull Request is ready to be merged label Oct 23, 2024
@me-no-dev me-no-dev merged commit 6dfd958 into release/v3.1.x Oct 23, 2024
59 of 60 checks passed
@me-no-dev me-no-dev deleted the bugfix/esp32_eth_component branch October 23, 2024 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pending Merge Pull Request is ready to be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant