devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erick Chen <erick.chen@spreadtrum.com>
To: Mark Brown <broonie@kernel.org>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, lgirdwood@gmail.com,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	baolin.wang@linaro.org, baolin.wang@spreadtrum.com
Subject: Re: [PATCH 2/2] regulator: sc2731: Add regulator driver to support Spreadtrum SC2731 PMIC
Date: Mon, 4 Dec 2017 17:03:14 +0800	[thread overview]
Message-ID: <20171204090313.GA2242@spreadtrum.com> (raw)
In-Reply-To: <201712020333.vB23X0mT082692@TPSPAM01.spreadtrum.com>

Hi Mark,

On Fri, Dec 01, 2017 at 01:01:37PM +0000, Mark Brown wrote:
> On Fri, Dec 01, 2017 at 04:58:16PM +0800, Erick Chen wrote:
> 
> > +static const struct of_device_id sc2731_regulator_of_match[] = {
> > +	{.compatible = "sprd,sc2731-regulator",},
> > +	{}
> > +};
> > +MODULE_DEVICE_TABLE(of, sc2731_regulator_of_match);
> 
> This looks like a subdriver for one specific device that can't be reused
> with anything else as it's specific to an individual device so I'd not
> expect it to appear as a separate thing in DT - the way Linux splits
> things up might not map well onto other OSs and may even change in
> future versions of Linux (look at all the audio drivers with clock
> controllers in them for example).  I'd expect the MFD to just register
> the subdevice without needing it to appear in the DT.
>

Make sense, i will remove the of_device_id table in next version.
 
> > +subsys_initcall(sc2731_regulator_init);
> > +module_exit(sc2731_regulator_exit);
> 
> Why not module_platform_driver()?  Deferred probe should sort out probe
> order.

On some Spreadtrum old platforms, we need to power on the CPU cores ASAP.
But now this issue had been fixed after some investigation, so we can change
subsys_initcall() to module_init() level as you suggested.

Very appreciated for your helpful comments.

      parent reply	other threads:[~2017-12-04  9:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01  8:58 [PATCH 1/2] dt-bindings: regulator: Add Spreadtrum SC27xx regulator documentation Erick Chen
2017-12-01  8:58 ` [PATCH 2/2] regulator: sc2731: Add regulator driver to support Spreadtrum SC2731 PMIC Erick Chen
2017-12-01  9:13   ` Philippe Ombredanne
     [not found]     ` <CAOFm3uFWhOMy=0nibOjDP_vP+m7Dcf1cGOmXXgcrSy6PDfqEWQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-01 12:49       ` Mark Brown
     [not found]         ` <20171201124935.qgqclyoatnnph63p-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2017-12-01 13:39           ` Philippe Ombredanne
     [not found]             ` <CAOFm3uHsT8PTZL0tQ0E+7Bje9C8ZUcPd13qz9v6jZHzqEoXqKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-01 14:24               ` Mark Brown
2017-12-04  9:11       ` Erick Chen
     [not found]   ` <75a6a48f603a25d744ef46287e036975b0203608.1512118703.git.erick.chen-lxIno14LUO0EEoCn2XhGlw@public.gmane.org>
2017-12-01 13:01     ` Mark Brown
     [not found]   ` <201712020333.vB23X0mT082692@TPSPAM01.spreadtrum.com>
2017-12-04  9:03     ` Erick Chen [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=20171204090313.GA2242@spreadtrum.com \
    --to=erick.chen@spreadtrum.com \
    --cc=baolin.wang@linaro.org \
    --cc=baolin.wang@spreadtrum.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).