From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "Frank Wunderlich (linux)" <linux@fw-web.de>
Cc: angelogioacchino.delregno@collabora.com, matthias.bgg@kernel.org,
Andi Shyti <andi.shyti@kernel.org>,
Qii Wang <qii.wang@mediatek.com>,
Wojciech Siudy <wojciech.siudy@nokia.com>,
linux-mediatek@lists.infradead.org, linux-i2c@vger.kernel.org,
daniel@makrotopia.org
Subject: Re: i2c issues in 6.18 on R4, but not r4pro (both mt7988 with i2c-mux on i2c2)
Date: Sun, 2 Nov 2025 23:49:54 +0100 [thread overview]
Message-ID: <aQfgEuelvU-8_2rh@shikoro> (raw)
In-Reply-To: <1144f62ad9886fed60620bce0bbed7ee@fw-web.de>
> from reset maintainers as i have my own defconfig. Tested and my mux works
> now again.
Glad it works again!
> Maybe this option should be enabled by default or when the i2c-mux is
> selected?
That's what we were discussing. At least a warning will now get printed
to the logs when booting suggesting the above solution.
> When moving from specific to a generic aproach (which makes sense) imho it
> should be
> mentioned in commit description which option needed instead :)
We didn't realize this back then. Only when the first bug report came
in :/
> btw. the Authors Email seems not working, got
Yes, he quit Nokia meanwhile.
next prev parent reply other threads:[~2025-11-02 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 10:38 i2c issues in 6.18 on R4, but not r4pro (both mt7988 with i2c-mux on i2c2) Frank Wunderlich (linux)
2025-11-02 11:39 ` Frank Wunderlich (linux)
2025-11-02 12:45 ` Wolfram Sang
2025-11-02 18:00 ` Frank Wunderlich (linux)
2025-11-02 22:49 ` Wolfram Sang [this message]
2025-11-05 11:51 ` Wolfram Sang
2025-11-05 12:02 ` AngeloGioacchino Del Regno
2025-11-05 12:08 ` Frank Wunderlich
2025-11-05 12:30 ` AngeloGioacchino Del Regno
2025-11-05 11:25 ` AngeloGioacchino Del Regno
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=aQfgEuelvU-8_2rh@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@makrotopia.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@kernel.org \
--cc=qii.wang@mediatek.com \
--cc=wojciech.siudy@nokia.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