Add chipId 0xB4 to allowlist of CST816S

[pascaldornfeld]

See #533

Might be a duplicate of #522. Consider this to be a mr that fixes the issue following the current code structure and the other mr to refactor that piece of code.

[Copilot]

Pull request overview

Expands the CST816S touch controller chip ID allowlist to support hardware reporting chip ID 0xB4 (as reported in lvgl-micropython issue #533).

Changes:

• Add 0xB4 as an additional allowed CST816S chip ID.
• Update the chip ID allowlist check to accept the new value.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The RuntimeError message still hard-codes the expected chip ID as _ChipIDValue (0xB5), but the allowlist now includes 0xB4/0xB5/0xB6. This will mislead users debugging mismatches. Consider including the actual chip_id read and the full set of allowed IDs in the error message (e.g., “expected one of …, got …”).

Suggested change

	if chip_id not in (_ChipIDValue, _ChipIDValue2, _ChipIDValue3):
	raise RuntimeError(f'Incorrect chip id ({hex(_ChipIDValue)})')
	allowed_ids = (_ChipIDValue, _ChipIDValue2, _ChipIDValue3)
	if chip_id not in allowed_ids:
	allowed_hex = ", ".join(hex(i) for i in allowed_ids)
	raise RuntimeError(
	f"Incorrect chip id: expected one of {allowed_hex}, got {hex(chip_id)}"
	)