[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200820114524.GC5854@sirena.org.uk>
Date: Thu, 20 Aug 2020 12:45:24 +0100
From: Mark Brown <broonie@...nel.org>
To: Gene Chen <gene.chen.richtek@...il.com>
Cc: matthias.bgg@...il.com, robh+dt@...nel.org, lgirdwood@...il.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Gene Chen <gene_chen@...htek.com>
Subject: Re: [PATCH v3 1/2] regulator: mt6360: Add support for MT6360
regulator
On Thu, Aug 20, 2020 at 03:53:41PM +0800, Gene Chen wrote:
> + mrd->regmap = dev_get_regmap(pdev->dev.parent, NULL);
> + if (!mrd->regmap) {
> + dev_err(&pdev->dev, "Failed to get parent regmap\n");
> + return -ENODEV;
> + }
> +static const struct of_device_id __maybe_unused mt6360_regulator_of_id[] = {
> + { .compatible = "mediatek,mt6360-regulator", },
> + {},
> +};
> +MODULE_DEVICE_TABLE(of, mt6360_regulator_of_id);
This device only exists in the context of a single parent device, there
should be no need for a compatible string here - this is just a detail
of how Linux does things. The MFD should just instntiate the platform
device.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists