From: Mark Brown <broonie@kernel.org>
To: matthias.bgg@kernel.org
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>,
Axel Lin <axel.lin@ingics.com>,
Chen Zhong <chen.zhong@mediatek.com>,
Gene Chen <gene_chen@richtek.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Matthias Brugger <mbrugger@suse.com>
Subject: Re: [PATCH v3 1/2] regulator: mt6358: Add OF match table
Date: Tue, 12 Jan 2021 13:52:17 +0000 [thread overview]
Message-ID: <20210112135217.GB4646@sirena.org.uk> (raw)
In-Reply-To: <20210112100659.19350-1-matthias.bgg@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
On Tue, Jan 12, 2021 at 11:06:57AM +0100, matthias.bgg@kernel.org wrote:
> The binding documentation mentions that a compatible is required for the
> MT6358 device node. But the driver does not provide a OF match table.
> This way auto-loading is broken as the MFD driver that registers the
> device has a .of_compatible set which makes the platform .uevent
> callback report a OF modalias, but that's not in the module.
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-01-12 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 10:06 [PATCH v3 1/2] regulator: mt6358: Add OF match table matthias.bgg
2021-01-12 10:06 ` [PATCH v3 2/2] regulator: mt6323: " matthias.bgg
2021-01-12 13:52 ` Mark Brown [this message]
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=20210112135217.GB4646@sirena.org.uk \
--to=broonie@kernel.org \
--cc=axel.lin@ingics.com \
--cc=chen.zhong@mediatek.com \
--cc=gene_chen@richtek.com \
--cc=hsin-hsiung.wang@mediatek.com \
--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 \
--cc=matthias.bgg@kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mbrugger@suse.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;
as well as URLs for NNTP newsgroup(s).