[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK9yfHwZN93T=Cs0jZ=ce6PBnjoFM6OcpC2cT1TCZVjHLBEJ=Q@mail.gmail.com>
Date: Thu, 9 Jan 2014 10:39:34 +0530
From: Sachin Kamat <sachin.kamat@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Lee Jones <lee.jones@...aro.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
Sangbeom Kim <sbkim73@...sung.com>,
Patch Tracking <patches@...aro.org>
Subject: Re: [PATCH 2/3] regulator: Add support for S2MPA01 regulator
Hi Mark,
Thanks for reviewing.
On 8 January 2014 18:00, Mark Brown <broonie@...nel.org> wrote:
> On Wed, Jan 08, 2014 at 11:56:29AM +0530, Sachin Kamat wrote:
>
>> + if (!iodev->dev->of_node) {
>> + if (pdata) {
>> + goto common_reg;
>> + } else {
>> + dev_err(pdev->dev.parent,
>> + "Platform data or DT node not supplied\n");
>> + return -ENODEV;
>> + }
>> + }
>
> The driver shouldn't need these to probe, it should be able to start in
> read only mode with no configuration.
OK.
>
>> +static int __init s2mpa01_pmic_init(void)
>> +{
>> + return platform_driver_register(&s2mpa01_pmic_driver);
>> +}
>> +subsys_initcall(s2mpa01_pmic_init);
>
> module_platform_driver().
Just a small doubt here. Wouldn't changing this from subsys init to module init
cause problems to devices like mmc which would want the regulators available
(where they are not already enabled by the boot loader)?
--
With warm regards,
Sachin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists