From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Karl Mehltretter <kmehltretter@gmail.com>,
Yoshinori Sato <yoshinori.sato@nifty.com>,
Rich Felker <dalias@libc.org>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: sh7785lcr: register the PCA9564 as I2C bus 0
Date: Sat, 03 Oct 2026 11:38:43 +0200 [thread overview]
Message-ID: <e3c88969f18c493859f7c382db7ed2afeb15b4fa.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <a4dcd9e615dc4e3c98c00e75cdd0c7fdeef02254.camel@physik.fu-berlin.de>
On Sat, 2026-10-03 at 11:07 +0200, John Paul Adrian Glaubitz wrote:
> On Sat, 2026-10-03 at 10:28 +0200, Karl Mehltretter wrote:
> > The R2025S/D board information is registered on I2C bus 0. Commit
> > 44454baa7ca7 ("i2c: Dynamically assign adapter id if it wasn't explictly
> > specified") changed the PCA9564 platform driver to pass negative platform
> > device IDs to the I2C core. The SH7785LCR device uses ID -1, so the core
> > assigns it a dynamic bus number. Reserving bus 0 for the board information
> > makes i2c-1 the first dynamic bus, and the RTC is never instantiated.
> >
> > Set the platform device ID to 0 so the adapter is registered as i2c-0 and
> > the RTC board information matches it.
> >
> > Fixes: 44454baa7ca7 ("i2c: Dynamically assign adapter id if it wasn't explictly specified")
> > Assisted-by: LLM
> > Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
> > ---
> >
> > Tested with 29-bit and 32-bit kernels on a custom QEMU model of the
> > SH7785LCR. Both registered the controller as i2c-0 and the R2025S/D as
> > rtc0.
> > Testing on real hardware is welcome.
> >
> > arch/sh/boards/board-sh7785lcr.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/sh/boards/board-sh7785lcr.c b/arch/sh/boards/board-sh7785lcr.c
> > index 25c4968f0d8b..b93423df582f 100644
> > --- a/arch/sh/boards/board-sh7785lcr.c
> > +++ b/arch/sh/boards/board-sh7785lcr.c
> > @@ -256,7 +256,7 @@ static struct i2c_pca9564_pf_platform_data i2c_platform_data = {
> >
> > static struct platform_device i2c_device = {
> > .name = "i2c-pca-platform",
> > - .id = -1,
> > + .id = 0,
> > .dev = {
> > .platform_data = &i2c_platform_data,
> > },
>
> Reviewed-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
I have to admit though I don't fully understand the description of this
patch. Either I don't have enough coffee or it's not precise enough.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2026-10-03 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 8:28 Karl Mehltretter
2026-10-03 8:53 ` John Paul Adrian Glaubitz
2026-10-03 9:07 ` John Paul Adrian Glaubitz
2026-10-03 9:38 ` John Paul Adrian Glaubitz [this message]
2026-10-03 9:51 ` Karl Mehltretter
2026-10-03 9:57 ` John Paul Adrian Glaubitz
2026-10-03 12:52 ` Geert Uytterhoeven
2026-10-03 18:17 ` John Paul Adrian Glaubitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3c88969f18c493859f7c382db7ed2afeb15b4fa.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=kmehltretter@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=yoshinori.sato@nifty.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®