devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Beomho Seo <beomho.seo@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org, sameo@linux.intel.com,
	lee.jones@linaro.org, lgirdwood@gmail.com, sre@kernel.org,
	dbaryshkov@gmail.com, dwmw2@infradead.org, robh+dt@kernel.org,
	pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	kyungmin.park@samsung.com, cw00.choi@samsung.com,
	jonghwa3.lee@samsung.com, geunsik.lim@samsung.com,
	inki.dae@samsung.com, sw0312.kim@samsung.com
Subject: Re: [PATCH 5/5] Documentation: Add documentation for rt5033 multifunction device
Date: Fri, 7 Nov 2014 10:34:40 +0000	[thread overview]
Message-ID: <20141107103440.GD8509@sirena.org.uk> (raw)
In-Reply-To: <1415328727-16245-6-git-send-email-beomho.seo@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 568 bytes --]

On Fri, Nov 07, 2014 at 11:52:07AM +0900, Beomho Seo wrote:

> +Required properties:
> +- compatible = Must be "richtek,rt5033-regulator"
> +
> +	regulators {
> +		compatible = "richtek,rt5033-regulator";

There should be no need for this extra compatible, it's not adding
anything we didn't know from the fact that it's part of the MFD.

> +		regulator-name {
> +			regulator-name = LDO/BUCK
> +			standard regulator constraints...
> +		};

Better to just say something like "regulator subnodes called X, Y and Z"
described using the standard regulator binding in...

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-11-07 10:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07  2:52 [PATCH 0/5] mfd: rt5033: Add Richtek RT5033 drivers Beomho Seo
2014-11-07  2:52 ` [PATCH 1/5] mfd: rt5033: Add Richtek RT5033 driver core Beomho Seo
2014-11-07  2:52 ` [PATCH 2/5] regulator: rt5033: Add RT5033 Regulator device driver Beomho Seo
     [not found]   ` <1415328727-16245-3-git-send-email-beomho.seo-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-11-07 10:27     ` Mark Brown
2014-11-07  2:52 ` [PATCH 3/5] power: rt5033_battery: Add RT5033 Fuel gauge " Beomho Seo
2014-11-07  2:52 ` [PATCH 4/5] power: rt5033_charger: Add RT5033 charger " Beomho Seo
2014-11-07  2:52 ` [PATCH 5/5] Documentation: Add documentation for rt5033 multifunction device Beomho Seo
2014-11-07 10:34   ` Mark Brown [this message]
2014-11-10  5:40     ` Beomho Seo

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=20141107103440.GD8509@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=beomho.seo@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=dbaryshkov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=galak@codeaurora.org \
    --cc=geunsik.lim@samsung.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=inki.dae@samsung.com \
    --cc=jonghwa3.lee@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=sre@kernel.org \
    --cc=sw0312.kim@samsung.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).