drivers: ethernet: renesas: Support Renesas RA8 Ethernet driver #77850
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
zephyrbot
added
manifest
manifest-hal_renesas
DNM
thaoluonguw
changed the title
thaoluonguw
force-pushed
the
support_renesas_ra8_ethernet
branch
from
7f2c197 to
46a85e2
Compare
thaoluonguw
requested review from
duynguyenxa,
kv2019i,
soburi and
ydamigos
zephyrbot
added
area: Networking
area: Ethernet
area: Pinctrl
area: Samples
zephyrbot
requested review from
KhiemNguyenT,
decsny,
jukkar,
kartben,
lmajewski,
maass-hamburg,
nashif,
pdgendt,
rlubos,
ssharks and
tbursztyka
decsny
requested changes
Sep 23, 2024
Member
There was a problem hiding this comment.
This is too similar to the generic phy-connection-type. Also I don't think it's a good idea to have an enum of a bunch of different specific phy devices. The phy should be a separate node in DT if it is a separate device in hardware.
dts/arm/renesas/ra/ra8/ra8x1.dtsi
Outdated
Member
There was a problem hiding this comment.
some info specific external phy doesn't belong in an soc devictree, unless that phy is embedded in the soc
Member
There was a problem hiding this comment.
@decsny , Thank you for you feedback, now we are using phy node
drivers/ethernet/eth_renesas_ra.c
Outdated
Member
There was a problem hiding this comment.
should be using zephyr phy API in the driver, no new vendor hal phy apis please, users hate this
Member
There was a problem hiding this comment.
@decsny , Thank you for you feedback, we change to implement mdio driver and now is using phy API from Zephyr, could you please help to recheck
duynguyenxa
force-pushed
the
support_renesas_ra8_ethernet
branch
from
46a85e2 to
d34901d
Compare
maass-hamburg
requested changes
Dec 4, 2024
duynguyenxa
force-pushed
the
support_renesas_ra8_ethernet
branch
from
e1e6740 to
9751913
Compare
Update hal_renesas new commit ID, in this version there are support for Ethernet and Ethernet phy in hal layer Signed-off-by: Duy Nguyen <[email protected]>
Add support for mdio driver for Renesas RA MCU series This support utilize the r_ether_phy driver in hal renesas to support mdio write and read function Signed-off-by: Duy Nguyen <[email protected]>
The ICS1894 phy AN_COMPLETE bit is latched high, this make the BMSR first read return incorrect status of the AN state, update one more BMSR read to ensure all latched bit is clear and BMSR return actual status of the phy chip Signed-off-by: Duy Nguyen <[email protected]>
This commit is to enable Ethernet drivers support on Renesas RA MCU, first target support is the Renesas RA8 series Signed-off-by: Duy Nguyen <[email protected]>
Enable Ethernet controller node and mdio node for RA boards. Add pinctl for mdio and Ethernet usage Signed-off-by: Duy Nguyen <[email protected]>
When publish message, the dup_flag is not intialize causing it to have random value and making the AWS MQTT broker to reject the message Add initialize dup_flag as 0 Signed-off-by: Duy Nguyen <[email protected]>
duynguyenxa
force-pushed
the
support_renesas_ra8_ethernet
branch
from
9751913 to
d9239c6
Compare
maass-hamburg
approved these changes
Dec 4, 2024
jukkar
approved these changes
Dec 4, 2024
KhiemNguyenT
approved these changes
Dec 5, 2024
|
@soburi It's in good shape. Please take a look. |
soburi
approved these changes
Dec 5, 2024
khoa-nguyen-18
added a commit
to renesas/zephyr
that referenced
this pull request
Jan 3, 2025
Currently, the SPI pinctrl is incorrect for the spi0 node. In this PR (zephyrproject-rtos#77850), we changed the pinctrl number for SPI from spi0 to spi1, but we forgot to update the node name to spi1. This commit aims to fix: - Correct the pinctrl name for spi - Correct the spi node on ek_ra8d1.dts Signed-off-by: Khoa Nguyen <[email protected]>
khoa-nguyen-18
added a commit
to renesas/zephyr
that referenced
this pull request
Jan 3, 2025
Currently, the SPI pinctrl is incorrect for the spi0 node. In this PR (zephyrproject-rtos#77850), we changed the pinctrl number for SPI from spi0 to spi1, but we forgot to update the node name to spi1. This commit aims to: - Correct the spi node in test app spi_loopback for ek_ra8d1 Signed-off-by: Khoa Nguyen <[email protected]>
kartben
pushed a commit
that referenced
this pull request
Jan 27, 2025
Currently, the SPI pinctrl is incorrect for the spi0 node. In this PR (#77850), we changed the pinctrl number for SPI from spi0 to spi1, but we forgot to update the node name to spi1. This commit aims to fix: - Correct the pinctrl name for spi - Correct the spi node on ek_ra8d1.dts Signed-off-by: Khoa Nguyen <[email protected]>
kartben
pushed a commit
that referenced
this pull request
Jan 27, 2025
Currently, the SPI pinctrl is incorrect for the spi0 node. In this PR (#77850), we changed the pinctrl number for SPI from spi0 to spi1, but we forgot to update the node name to spi1. This commit aims to: - Correct the spi node in test app spi_loopback for ek_ra8d1 Signed-off-by: Khoa Nguyen <[email protected]>
RuibinChang
pushed a commit
to RuibinChang/zephyr
that referenced
this pull request
Feb 10, 2025
Currently, the SPI pinctrl is incorrect for the spi0 node. In this PR (zephyrproject-rtos#77850), we changed the pinctrl number for SPI from spi0 to spi1, but we forgot to update the node name to spi1. This commit aims to fix: - Correct the pinctrl name for spi - Correct the spi node on ek_ra8d1.dts (cherry picked from commit 810ceb2) Original-Signed-off-by: Khoa Nguyen <[email protected]> GitOrigin-RevId: 810ceb2 Cr-Build-Id: 8724547022730561377 Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8724547022730561377 Copybot-Job-Name: zephyr-main-copybot-downstream Change-Id: I84e08cf6ffe94a2fb65afbf71d56abd868ec64ae Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/zephyr/+/6205016 Tested-by: ChromeOS Prod (Robot) <[email protected]> Bot-Commit: ChromeOS Prod (Robot) <[email protected]> Commit-Queue: ChromeOS Prod (Robot) <[email protected]>
RuibinChang
pushed a commit
to RuibinChang/zephyr
that referenced
this pull request
Feb 10, 2025
Currently, the SPI pinctrl is incorrect for the spi0 node. In this PR (zephyrproject-rtos#77850), we changed the pinctrl number for SPI from spi0 to spi1, but we forgot to update the node name to spi1. This commit aims to: - Correct the spi node in test app spi_loopback for ek_ra8d1 (cherry picked from commit 436a6d8) Original-Signed-off-by: Khoa Nguyen <[email protected]> GitOrigin-RevId: 436a6d8 Cr-Build-Id: 8724547022730561377 Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8724547022730561377 Copybot-Job-Name: zephyr-main-copybot-downstream Change-Id: I344be2d30b98399136af17321d81b0d5dd3212ef Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/zephyr/+/6205017 Bot-Commit: ChromeOS Prod (Robot) <[email protected]> Commit-Queue: ChromeOS Prod (Robot) <[email protected]> Tested-by: ChromeOS Prod (Robot) <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to support Ethernet driver for the Renesas RA8 boards
The driver design is based on the using Ethernet and Ethernet PHY FSP driver from hal_renesas to implement.