diff options
| author | Karl Mehltretter <kmehltretter@gmail.com> | 2026-10-04 20:46:44 +0200 |
|---|---|---|
| committer | John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> | 2026-10-13 19:00:35 +0200 |
| commit | f3b8138e148b86c74dad6adf209ae61c7d958f2f (patch) | |
| tree | ba9d356aac48de8dc94baf587c15453b0fa8dc0f /tools/lib/python/__init__.py | |
| parent | 014aa19e4f25163ba7862c5b4635b5f1d01b0613 (diff) | |
| download | linux-next-f3b8138e148b86c74dad6adf209ae61c7d958f2f.tar.gz linux-next-f3b8138e148b86c74dad6adf209ae61c7d958f2f.zip | |
sh: sh7785lcr: Register the PCA9564 controller as I2C bus 0
Before commit 44454baa7ca7 ("i2c: Dynamically assign adapter id if it
wasn't explictly specified"), a negative ID was replaced by zero, and
I2C bus zero was instantiated. Since that commit, a negative ID is passed
verbatim, instantiating an I2C bus with a dynamic number. As SH boards
still use i2c_register_board_info(0, ...) to register I2C devices, they
rely on the I2C bus being bus zero.
The SH7785LCR is the only SH board whose I2C adapter has a negative ID
and its PCA9564 controller becomes i2c-1, causing registration of the
R2025S/D RTC to fail and hwclock not detecting /dev/rtc0.
Set the platform device ID to 0 so that the adapter is registered as
bus zero again.
Fixes: 44454baa7ca7 ("i2c: Dynamically assign adapter id if it wasn't explictly specified")
Tested-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Reviewed-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Signed-off-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Diffstat (limited to 'tools/lib/python/__init__.py')
0 files changed, 0 insertions, 0 deletions