Add kernel config to support external i2c devices

[xtsrthm]

This pull request adds support for usb to i2c adapters, the i2c chardev and the bme280 family environment sensors for the ova board.

The same changes were already made to the kernel config for the generic-x86-64 board in #2800 and #2813.

Now i would like to move Home Assistant from a bare metal install to a virtual machine.

Summary by CodeRabbit

• New Features
  • Enhanced support for I2C and GPIO devices, improving compatibility with various hardware interfaces.
  • Added support for new sensors, including BMP280, enhancing sensor integration capabilities.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes involve modifications to the kernel configuration file for the buildroot-external project. New configuration options have been added to enhance support for I2C and GPIO functionalities, as well as additional device drivers. These modifications include enabling support for various components related to the DLN2 platform, specifically targeting I2C devices and sensors. The existing configurations remain unchanged, ensuring the overall structure of the configuration file is preserved.

Changes

File Path	Change Summary
buildroot-external/board/pc/ova/kernel.config	Added new configuration options for I2C and GPIO support, including options for I2C devices and sensors. The following options were added: CONFIG_I2C_BOARDINFO, CONFIG_I2C_COMPAT, CONFIG_I2C_CHARDEV, CONFIG_I2C_TINY_USB, CONFIG_I2C_DLN2, CONFIG_GPIO_DLN2, CONFIG_MFD_DLN2, CONFIG_DLN2_ADC, CONFIG_IIO, and CONFIG_BMP280.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant KernelConfig
    participant I2C
    participant GPIO
    participant Sensor

    User->>KernelConfig: Modify configuration
    KernelConfig->>I2C: Enable I2C support
    KernelConfig->>GPIO: Enable GPIO support
    KernelConfig->>Sensor: Enable sensor support
    I2C->>KernelConfig: Configuration options added
    GPIO->>KernelConfig: Configuration options added
    Sensor->>KernelConfig: Configuration options added
    KernelConfig->>User: Configuration updated

Loading

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a2ff594 and 16dbefd.

📒 Files selected for processing (1)

• buildroot-external/board/pc/ova/kernel.config (1 hunks)

🧰 Additional context used

🔇 Additional comments (6)

buildroot-external/board/pc/ova/kernel.config (6)

127-128: LGTM: I2C board info and compatibility options added.

These options enhance I2C support, which aligns with the PR objectives. They enable I2C board information support and compatibility mode, which are beneficial for broader I2C device support.

---

129-129: LGTM: I2C character device support added.

This change enables the I2C character device driver as a module, which directly fulfills one of the PR objectives. This will allow user-space access to I2C devices, enhancing the system's flexibility for I2C operations.

---

131-131: LGTM: I2C Tiny USB adapter support added.

This change enables support for the I2C Tiny USB adapter as a module, which aligns with the PR objective of enhancing support for USB to I2C adapters. This will allow users to connect I2C devices via USB, increasing the system's versatility.

---

133-136: LGTM: DLN2 related configurations added. Please clarify the specific need.

These changes enable support for various DLN2 functionalities (I2C, GPIO, MFD, and ADC) as modules. While they align with the overall goal of enhancing I2C and GPIO support, they weren't explicitly mentioned in the PR objectives.

Could you please clarify the specific need for DLN2 support in this context? This will help ensure that these additions are necessary for the intended use cases.

---

138-139: LGTM: IIO and BMP280 sensor support added. Consider BME280 support.

These changes enable the Industrial I/O subsystem and BMP280 sensor support as modules, which aligns with the PR objective of adding support for the BME280 family of environmental sensors.

The PR objectives specifically mention BME280 sensors. While BMP280 is part of the same family, you might want to consider adding explicit support for BME280 (CONFIG_BME280) if it's not already included elsewhere. Could you confirm if this is necessary for your use case?

---

127-139: Summary: Kernel configuration changes enhance I2C and sensor support for OVA board

The changes made to the kernel configuration file for the OVA board are consistent with the PR objectives and previous modifications for the generic-x86-64 board. These additions should significantly improve support for USB to I2C adapters, I2C character devices, and environmental sensors, facilitating the integration of external I2C devices into the Home Assistant operating system.

Key improvements include:

1. Enhanced I2C support (board info, compatibility, character device, and Tiny USB adapter)
2. Added DLN2 platform support for various functionalities
3. Enabled Industrial I/O subsystem and BMP280 sensor support

These changes appear to be well-thought-out and should contribute to a more versatile Home Assistant operating system, especially for users transitioning to virtual machine environments.

To ensure completeness:

1. Please clarify the specific need for DLN2 support in this context.
2. Confirm if explicit BME280 support is required or if the current BMP280 support is sufficient for your use case.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 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]

Have you had an opportunity to test it? Otherwise it looks good to me, thanks!

[xtsrthm]

I built HAOS locally and tried loading the relevant kernel modules in a VM, but haven't tested this with actual hardware, cause that requires physical access, if you want i can do that though