Skip to content

Conversation

@GuEe-GUI
Copy link
Contributor

@GuEe-GUI GuEe-GUI commented Dec 9, 2025

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

[

  1. New interface for 'pin_gpio_request'.
  2. Fixup the DM Kconfig import in DM mode only.
  3. Add ARM PL061 GPIO driver.
  4. Add Single Pinctrl.
  • BSP:
    Spacemit K1

]

当前拉取/合并请求的状态 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
Copy link

github-actions bot commented Dec 9, 2025

👋 感谢您对 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:pin
  • 设置PR number为 \ Set the PR number to:11027
  1. 等待工作流完成 | Wait for the workflow to complete
    格式化后的代码将自动推送至你的分支。
    The formatted code will be automatically pushed to your branch.

完成后,提交将自动更新至 pin 分支,关联的 Pull Request 也会同步更新。
Once completed, commits will be pushed to the pin 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
Copy link

github-actions bot commented Dec 9, 2025

📌 Code Review Assignment

🏷️ Tag: components

Reviewers: Maihuanyi

Changed Files (Click to expand)
  • components/drivers/include/drivers/dev_pin.h
  • components/drivers/pin/Kconfig
  • components/drivers/pin/SConscript
  • components/drivers/pin/dev_pin_dm.c
  • components/drivers/pin/dev_pin_dm.h
  • components/drivers/pin/pin-pl061.c
  • components/drivers/pinctrl/Kconfig
  • components/drivers/pinctrl/SConscript
  • components/drivers/pinctrl/pinctrl-single.c

📊 Current Review Status (Last Updated: 2025-12-09 23:14 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.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds Device Manager (DM) support for pin control subsystem with the following changes:

  • New ARM PL061 GPIO driver for DM-based systems
  • Single Pinctrl driver supporting TI and generic pinctrl-single bindings
  • New pin_gpio_request API for GPIO pin configuration via pinctrl
  • Kconfig updates to ensure DM-related options are only available when DM is enabled

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 11 comments.

Show a summary per file
File Description
components/drivers/pinctrl/pinctrl-single.c New pinctrl-single driver with support for TI SoCs and generic pinctrl configuration
components/drivers/pinctrl/SConscript Add build support for pinctrl-single driver
components/drivers/pinctrl/Kconfig Add configuration option for RT_PINCTRL_SINGLE driver
components/drivers/pin/pin-pl061.c New ARM PL061 GPIO driver with interrupt support
components/drivers/pin/dev_pin_dm.h Add declaration for new pin_gpio_request API
components/drivers/pin/dev_pin_dm.c Implement pin_gpio_request function for pinctrl integration
components/drivers/pin/SConscript Add build support for PL061 driver
components/drivers/pin/Kconfig Add RT_PIN_PL061 config option and restrict DM Kconfig to DM mode
components/drivers/include/drivers/dev_pin.h Add pin_ctrl_gpio_request callback to rt_pin_ops

⚠️ PR Title and Description Issues (RT-Thread Guidelines):

🟡 [PR Title/PR 标题]: Title could be more specific / 标题可以更具体

English: PR title "Update for DM" is somewhat vague. Based on modified files, a more specific title would be: [dm][pin][pinctrl] Add PL061 GPIO and single pinctrl drivers for DM

中文:PR 标题"Update for DM"有些模糊。基于修改的文件,更具体的标题应为:[dm][pin][pinctrl] Add PL061 GPIO and single pinctrl drivers for DM

🟢 [PR Description/PR 描述]: Description is adequate / 描述充分

English: The PR description adequately lists the changes and affected BSP (Spacemit K1). Well structured with clear points.

中文:PR 描述充分列出了更改和受影响的 BSP(Spacemit K1)。结构清晰,要点明确。

Some GPIO should apply GPIO mode by pinctrl, add `pin_ctrl_gpio_request`
for GPIO driver to apply it auto.

Signed-off-by: GuEe-GUI <[email protected]>
1. ARM PL061 GPIO
2. Single Pinctrl

Signed-off-by: GuEe-GUI <[email protected]>
@GuEe-GUI
Copy link
Contributor Author

GuEe-GUI commented Dec 9, 2025

@Rbb666 AI相关要求已修改

@Rbb666 Rbb666 merged commit 357c9b7 into RT-Thread:master Dec 10, 2025
60 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants