From: Mark Brown <broonie@kernel.org>
To: "Sahin, Okan" <Okan.Sahin@analog.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
ChiYuan Huang <cy_huang@richtek.com>,
"Bolboaca, Ramona" <Ramona.Bolboaca@analog.com>,
Caleb Connolly <caleb.connolly@linaro.org>,
William Breathitt Gray <william.gray@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH v3 3/5] drivers: regulator: Add ADI MAX77541/MAX77540 Regulator Support
Date: Tue, 31 Jan 2023 13:32:09 +0000 [thread overview]
Message-ID: <Y9kYWfAkVnUFO9nN@sirena.org.uk> (raw)
In-Reply-To: <BY5PR03MB5153C18E65B954E9FEFD96B1E7D09@BY5PR03MB5153.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
On Tue, Jan 31, 2023 at 01:23:33PM +0000, Sahin, Okan wrote:
> Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> >> static const struct of_device_id max77541_regulator_of_id[] = {
> >> { .compatible = "adi,max77540-regulator", },
> >> { .compatible = "adi,max77541-regulator", },
> >> { /* sentinel */ }
> >> };
> >> MODULE_DEVICE_TABLE(of, max77541_regulator_of_id);
> >> What do you think?
> >If you have got all necessary data from the upper layer, why do you need to have
> >an ID table here? I'm not sure I understand how this OF ID table works in this
> >case.
> I added it since there is regulator node in device tree. With the help
> of devm_regulator_register(..), driver takes parameters of regulator
> node. I also used id to select and to initialize regulator descriptors
> which are chip specific. So far there is no comment about OF ID table
> so I kept it. I thought I need to add both of id table and platform id
> table as name matching is required to initialize platform device from
> mfd.
You probably shouldn't have compatibles for subdevices of a MFD unless
it's some reusable IP that'll appear elsewhere, especially for something
like the regulators where grouping them all into a single device is very
Linux specific.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-01-31 13:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 6:38 [PATCH v3 0/5] Add MAX77541/MAX77540 PMIC Support Okan Sahin
2023-01-18 6:38 ` [PATCH v3 1/5] drivers: mfd: Add ADI " Okan Sahin
2023-01-18 8:16 ` Andy Shevchenko
2023-01-19 14:27 ` Lee Jones
2023-01-19 15:06 ` Andy Shevchenko
2023-01-19 15:06 ` William Breathitt Gray
2023-01-18 6:38 ` [PATCH v3 2/5] dt-bindings: mfd: Add ADI MAX77541/MAX77540 Okan Sahin
2023-01-18 8:22 ` Krzysztof Kozlowski
2023-01-31 12:02 ` Sahin, Okan
2023-01-31 16:44 ` Krzysztof Kozlowski
2023-01-31 21:28 ` Sahin, Okan
2023-02-01 7:25 ` Krzysztof Kozlowski
2023-02-01 7:46 ` Sahin, Okan
2023-02-01 8:08 ` Krzysztof Kozlowski
2023-01-18 13:10 ` Rob Herring
2023-01-18 6:38 ` [PATCH v3 3/5] drivers: regulator: Add ADI MAX77541/MAX77540 Regulator Support Okan Sahin
2023-01-18 8:19 ` Andy Shevchenko
2023-01-31 7:20 ` Sahin, Okan
2023-01-31 9:27 ` Sahin, Okan
2023-01-31 12:26 ` Andy Shevchenko
2023-01-31 13:23 ` Sahin, Okan
2023-01-31 13:29 ` Andy Shevchenko
2023-01-31 13:59 ` Sahin, Okan
2023-01-31 14:13 ` Andy Shevchenko
2023-01-31 14:38 ` Sahin, Okan
2023-01-31 13:32 ` Mark Brown [this message]
2023-01-31 12:24 ` Andy Shevchenko
2023-01-31 13:12 ` Sahin, Okan
2023-01-31 13:26 ` Andy Shevchenko
2023-01-18 6:38 ` [PATCH v3 4/5] dt-bindings: regulator: Add ADI MAX77541/MAX77540 Regulator Okan Sahin
2023-01-18 8:33 ` Krzysztof Kozlowski
2023-01-18 6:38 ` [PATCH v3 5/5] drivers: iio: adc: Add ADI MAX77541 ADC Support Okan Sahin
2023-01-18 8:23 ` Andy Shevchenko
2023-01-21 17:55 ` Jonathan Cameron
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=Y9kYWfAkVnUFO9nN@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Okan.Sahin@analog.com \
--cc=Ramona.Bolboaca@analog.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=caleb.connolly@linaro.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=william.gray@linaro.org \
/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