Added support for AiP31068 and PCA9633

[CutterXYZ]

Support for AiP31068.
This is a standard I2C controller for HD44780 LCD displays.

Spec sheet:
https://www.orientdisplay.com/wp-content/uploads/2022/08/AIP31068L.pdf

Support for PCA9633.
This is a RGB backlight controller over a dedicated I2C port.

Spec sheet:
https://www.nxp.com/docs/en/data-sheet/PCA9633.pdf

This has been tested with the Waveshare LCD1602 display:
https://www.waveshare.com/wiki/LCD1602_RGB_Module

[gemini-code-assist]

Summary of Changes

Hello @CutterXYZ, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the library's display hardware compatibility by integrating support for two new I2C-based components. It allows for direct control of HD44780-compatible LCDs via the AiP31068 controller and provides comprehensive management of RGB backlights using the PCA9633 driver, expanding the range of display modules that can be easily interfaced.

Highlights

• AiP31068 LCD Controller Support: Introduced a new I2C interface class, aip31068, to support the AiP31068 LCD controller, which is a standard I2C controller for HD44780 LCD displays. This class is configured for 8-bit mode operation.
• PCA9633 RGB Backlight Driver Support: Added a new I2C interface class, pca9633, for the PCA9633 RGB backlight driver. This class provides methods to control backlight color (Red, Green, Blue, Amber) and overall brightness, and includes initialization for default settings and LED control.
• Tested Hardware: The new implementations have been tested with the Waveshare LCD1602 display, which utilizes both the AiP31068 for the LCD and the PCA9633 for the RGB backlight.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces support for two new I2C devices, AiP31068 and PCA9633. The changes are well-structured. I've identified a bug in the pca9633 implementation where setting a color channel to 0 is not handled correctly. I've also provided suggestions to improve the docstrings for both new classes for better clarity and maintainability.

[rm-hull]

@CutterXYZ PR looks reasonable, however:

• there are some flake8 adjustments needed as CI fails - see https://github.com/rm-hull/luma.core/actions/runs/20011875325/job/57383435391?pr=292#step:10:24 - you should be able to run tox -e qa to reproduce
• some tests would be good