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

Remove USB stack patches working around obsoleted Z-Wave devices issues #3854

Merged
merged 2 commits into from
Feb 4, 2025

Conversation

sairon
Copy link
Member

@sairon sairon commented Feb 3, 2025

In #3224 we've introduced a patch reverting some changes in the USB stack that was supposed to work around issues with some USB devices. Later discussions revealed these devices are obsoleted by the manufacturer and there is no official way of fixing those in newer Linux kernels. However, carrying the patches makes us diverge from upstream and can eventually trigger other problems not present upstream we'll have to handle.

Drop these patches now to be part of the upcoming OS 15 release, rather than needing to drop them later in any of the patch revisions later.

Summary by CodeRabbit

  • Bug Fixes
    • Reverted recent USB subsystem modifications to restore reliable device recognition and initialization.
    • Improved high-speed USB operation for more consistent connectivity.
    • Enhanced support for connected devices, ensuring smoother performance (including for systems using the Z-Wave.me USB stick).

@sairon sairon added the os label Feb 3, 2025
@sairon sairon requested a review from agners February 3, 2025 15:14
@sairon sairon force-pushed the drop-usb-core-patch branch from bff99ea to 4e51a38 Compare February 3, 2025 15:15
In #3224 we've introduced a patch reverting some changes in the USB stack that
was supposed to work around issues with some USB devices. Later discussions
revealed these devices are obsoleted by the manufacturer and there is no
official way of fixing those in newer Linux kernels. However, carrying the
patches makes us diverge from upstream and can eventually trigger other
problems not present upstream we'll have to handle.

Drop these patches now to be part of the upcoming OS 15 release, rather than
needing to drop them later in any of the patch revisions later.
Copy link

coderabbitai bot commented Feb 3, 2025

📝 Walkthrough

Walkthrough

The changes remove patch files that had previously reverted USB core modifications meant to address issues with the Z-Wave.me UZB stick. The rollback undoes alterations to SuperSpeed initialization, race conditions in hub port descriptor handling, and API changes for retrieving device descriptors. Additionally, the method signature for usb_get_device_descriptor is updated in both the USB core header and the message file, changing its return type from a pointer to an integer with an added size parameter.

Changes

File(s) Change Summary
buildroot-external/.../patches/linux/0005-Revert-USB-core-changes-causing-issues-with-Z-Wave.m.patch
buildroot-external/.../patches/linux/6.12.11/0002-Revert-USB-core-changes-causing-issues-with-Z-Wave.m.patch
Removed patch files that previously reverted modifications in the USB core subsystem—changes that affected SuperSpeed initialization, descriptor race conditions, and the device descriptor API used to support the Z-Wave.me UZB stick.
drivers/usb/core/usb.h
drivers/usb/core/message.c
Updated the declaration of usb_get_device_descriptor: the method signature changed from returning a device descriptor pointer to returning an integer and now accepts a device pointer along with an unsigned size parameter.

Sequence Diagram(s)

sequenceDiagram
    participant Driver
    participant USB_Core
    participant USB_Device

    Driver->>+USB_Core: Call usb_get_device_descriptor(dev, size)
    USB_Core->>+USB_Device: Request device descriptor
    USB_Device-->>-USB_Core: Returns descriptor data
    USB_Core-->>-Driver: Returns descriptor data or error code
Loading

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c63f9ec and 4e51a38.

📒 Files selected for processing (2)
  • buildroot-external/board/raspberrypi/patches/linux/0005-Revert-USB-core-changes-causing-issues-with-Z-Wave.m.patch (0 hunks)
  • buildroot-external/patches/linux/6.12.11/0002-Revert-USB-core-changes-causing-issues-with-Z-Wave.m.patch (0 hunks)
💤 Files with no reviewable changes (2)
  • buildroot-external/patches/linux/6.12.11/0002-Revert-USB-core-changes-causing-issues-with-Z-Wave.m.patch
  • buildroot-external/board/raspberrypi/patches/linux/0005-Revert-USB-core-changes-causing-issues-with-Z-Wave.m.patch

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
  • @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 or @coderabbitai title 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.

@sairon sairon changed the title Remove USB stack patches working around obsoleted Z-Wave devices isses Remove USB stack patches working around obsoleted Z-Wave devices issues Feb 3, 2025
@sairon sairon merged commit b5b2f5d into dev Feb 4, 2025
3 checks passed
@sairon sairon deleted the drop-usb-core-patch branch February 4, 2025 10:43
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