[bsp][rockchip] Fixup rockchip run

[GuEe-GUI]

拉取/合并请求描述：(PR description)

[

1. fixup the drivers' configure
2. fixup the regulator ref of enabled status

]

当前拉取/合并请求的状态 Intent for your PR

必须选择一项 Choose one (Mandatory):

• 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
• 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality：

我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

• 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
• 代码风格正确，包括缩进空格，命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
• 没有垃圾代码，代码尽量精简，不包含#if 0代码，不包含已经被注释了的代码 All redundant code is removed and cleaned up
• 所有变更均有原因及合理的，并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
• 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
• 代码是高质量的 Code in this PR is of high quality
• 已经使用formatting 等源码格式化工具确保格式符合RT-Thread代码规范 This PR complies with RT-Thread code specification
• 如果是新增bsp, 已经添加ci检查到.github/ALL_BSP_COMPILE.json 详细请参考链接BSP自查

[github-actions]

👋 感谢您对 RT-Thread 的贡献！Thank you for your contribution to RT-Thread!

为确保代码符合 RT-Thread 的编码规范，请在你的仓库中执行以下步骤运行代码格式化工作流（如果格式化CI运行失败）。
To ensure your code complies with RT-Thread's coding style, please run the code formatting workflow by following the steps below (If the formatting of CI fails to run).

---

🛠 操作步骤 | Steps

1. 前往 Actions 页面 | Go to the Actions page
   点击进入工作流 → | Click to open workflow →

2. 点击 Run workflow | Click Run workflow

• 设置需排除的文件/目录（目录请以"/"结尾）
  Set files/directories to exclude (directories should end with "/")
• 将目标分支设置为 \ Set the target branch to：fixup_rockchip_run
• 设置PR number为 \ Set the PR number to：11320

3. 等待工作流完成 | Wait for the workflow to complete
   格式化后的代码将自动推送至你的分支。
   The formatted code will be automatically pushed to your branch.

完成后，提交将自动更新至 fixup_rockchip_run 分支，关联的 Pull Request 也会同步更新。
Once completed, commits will be pushed to the fixup_rockchip_run branch automatically, and the related Pull Request will be updated.

如有问题欢迎联系我们，再次感谢您的贡献！💐
If you have any questions, feel free to reach out. Thanks again for your contribution!

[github-actions]

📌 Code Review Assignment

🏷️ Tag: components

Reviewers: @Maihuanyi

Changed Files (Click to expand)

• components/drivers/regulator/regulator.c

---

📊 Current Review Status (Last Updated: 2026-04-07 20:54 CST)

• ⌛ @Maihuanyi Pending Review

---

📝 Review Instructions

1. 维护者可以通过单击此处来刷新审查状态: 🔄 刷新状态
   Maintainers can refresh the review status by clicking here: 🔄 Refresh Status

2. 确认审核通过后评论 LGTM/lgtm
   Comment LGTM/lgtm after confirming approval

3. PR合并前需至少一位维护者确认
   PR must be confirmed by at least one maintainer before merging

ℹ️ 刷新CI状态操作需要具备仓库写入权限。
ℹ️ Refresh CI status operation requires repository Write permission.

[GuEe-GUI]

@Rbb666

[GuEe-GUI]

静态检查处代码逻辑没有问题

[dmanzhang]

为什么在rk3568 rk3562 64bit系统上面，通过rt_ioremap映射出来的64bit地址高32位为0
正常的（修改DM之的的rtt版本，1月9号之前的）
(*eth)->dev->pReg(0x00000000fe2a0000) GMAC0(0xfffffffff0101000) cfg->id(0x00000000fe2a0000)

错误的
(*eth)->dev->pReg(0x00000000ffa80000) GMAC0(0x0000000000064000) cfg->id(0x00000000ffa80000)

GMAC0的高32位为0

[GuEe-GUI]

是不是选了 RT-Thread 的版本

[dmanzhang]

[*] Enable RT-Thread Smart (microkernel on kernel/userland) 用的是smart版本

[0xffffffff00215000 - 0xffffffff00225000] phy-map
_ paddr = 0x00000000ff080000
[0xffffffff00225000 - 0xffffffff00235000] phy-map
_ paddr = 0x00000000ff060000
[0xffffffff00235000 - 0xffffffff00245000] phy-map
_ paddr = 0x00000000ff070000

list_kmem 显示是正常的

{
rt_kprintf("per pin3562_init: GPIO1_IOC %p GPIO2_IOC %p GPIO3_IOC %p GPIO4_IOC %p\n", GPIO1_IOC, GPIO2_IOC, GPIO3_IOC, GPIO4_IOC);

GPIO0_IOC = rt_ioremap((volatile uint32_t *)GPIO0_IOC, 0x10000);
GPIO1_IOC = rt_ioremap((volatile uint32_t *)GPIO1_IOC, 0x10000);
GPIO2_IOC = GPIO1_IOC;
GPIO3_IOC = rt_ioremap((volatile uint32_t *)GPIO3_IOC, 0x10000);
GPIO4_IOC = GPIO3_IOC;

rt_kprintf("pin3562_init: GPIO1_IOC %p GPIO2_IOC %p GPIO3_IOC %p GPIO4_IOC %p\n", GPIO1_IOC, GPIO2_IOC, GPIO3_IOC, GPIO4_IOC);

}

initialize rk_hal340_pin3562_init
per pin3562_init: GPIO1_IOC 0x00000000ff060000 GPIO2_IOC 0x00000000ff060000 GPIO3_IOC 0x00000000ff070000 GPIO4_IOC 0x00000000ff070000
pin3562_init: GPIO1_IOC 0x00000000000d4000 GPIO2_IOC 0x00000000000d4000 GPIO3_IOC 0x00000000000e4000 GPIO4_IOC 0x00000000000e4000
:0 done

[GuEe-GUI]

要不你跟踪一下 rt_ioremap？正常情况是 0xffffffff00000000 开头的地址。

[dmanzhang]

啊，这边没有调试器，只能printf。rk356xgmac_base = rt_dm_dev_iomap(pdev, 0); ，rt_dm_dev_iomap返回的也是高32位为0