From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Mark Brown <broonie@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: mt6358-regulator does not probe automatically on MT8183 and MT8186 Chromebooks
Date: Sun, 22 Dec 2024 00:30:57 +0300 [thread overview]
Message-ID: <44580fb7-a0ab-41c9-a4e7-fe053742883a@gmail.com> (raw)
In-Reply-To: <f3c6ea1d-da0f-40cc-ba70-7cabb5c3189f@gmail.com>
Hi,
On 2024-12-21 18:38 +03:00, Alper Nebi Yasak wrote:
> Hello,
>
> I'm left with one small problem trying to boot Debian on MT8183 and
> MT8186 Chromebooks (Cozmo and Magneton respectively). I see a lot of
> probe deferrals and get dropped into an initramfs shell. All of them
> get resolved if I run `modprobe mt6358-regulator`, after which I can
> exit the initramfs shell to continue booting.
>
> It has been happening for a long time, still unsolved as of v6.12 and
> next-20241220. I am using `softdep mediatek-drm pre: mt6358-regulator`
> and so on in /etc/modprobe.d/ to trigger it to probe, as a workaround.
>
> But I would like if it was solved upstream so distro kernels can work
> "out of the box". Any ideas why isn't it probing automatically, and how
> to make it so it works?
>
> More info from a serial connection below (on mt8183-kukui-jacuzzi-cozmo):
>
> [...]
I found this patch [1] from Matthias, sent around 2021 about adding an
OF match table to the driver, which fixes this problem for my boards.
[1]
https://lore.kernel.org/linux-mediatek/20210112100659.19350-1-matthias.bgg@kernel.org/T/#u
There on 2021-01-12 13:52, Mark Brown wrote:
> As previously discussed it'd be better to fix the binding document to
> deprecate the requirement for the compatible and remove the usage from
> the MFD.
This doesn't seem to have happened in the last almost-four years, so
please reconsider resending/applying the patch.
next prev parent reply other threads:[~2024-12-21 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 15:38 Alper Nebi Yasak
2024-12-21 21:30 ` Alper Nebi Yasak [this message]
2024-12-23 16:00 ` Mark Brown
2024-12-23 11:21 ` AngeloGioacchino Del Regno
2025-05-23 12:58 ` Alper Nebi Yasak
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=44580fb7-a0ab-41c9-a4e7-fe053742883a@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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®