linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Gene Chen <gene.chen.richtek@gmail.com>
Cc: Gene Chen <gene_chen@richtek.com>,
	devicetree@vger.kernel.org, lgirdwood@gmail.com,
	linux-kernel@vger.kernel.org, robh+dt@kernel.org,
	linux-mediatek@lists.infradead.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/2] regulator: mt6360: Add DT binding documentation
Date: Tue, 25 Aug 2020 10:34:04 +0100	[thread overview]
Message-ID: <20200825093404.GB5379@sirena.org.uk> (raw)
In-Reply-To: <CAE+NS37p38dAN1bAi_VvEYYGNiWDVFKrdHL-hTgi2nim_7Zvqw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 634 bytes --]

On Tue, Aug 25, 2020 at 05:21:06PM +0800, Gene Chen wrote:
> Mark Brown <broonie@kernel.org> 於 2020年8月25日 週二 上午3:49寫道:

> > So shouldn't there be a documented LDO_VIN1/2 then?

> LDO_VINx is HW design layout, so actually it can't be changed by device tree.
> LDO_VIN1/LDO_VIN2 supply from VSYS, not regulator, so I think usually
> not to show the supply from in device tree.
> or I should declare a dummy reference to system power like "*-supply =
> <&system_power>;"?

When you say it's from the hardware design do you mean it's fixed by the
silicon or is this something that's fixed in the board?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-08-25  9:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20  7:53 [PATCH v3 0/2] regulator: mt6360: Add support for MT6360 regulator Gene Chen
2020-08-20  7:53 ` [PATCH v3 1/2] " Gene Chen
2020-08-20 11:45   ` Mark Brown
2020-08-24 10:23     ` Gene Chen
2020-08-24 11:04       ` Mark Brown
2020-08-25  9:13         ` Gene Chen
2020-08-25  9:26           ` Mark Brown
2020-08-20  7:53 ` [PATCH v3 2/2] regulator: mt6360: Add DT binding documentation Gene Chen
2020-08-20 11:30   ` Mark Brown
2020-08-24  7:21     ` Gene Chen
2020-08-24 19:48       ` Mark Brown
2020-08-25  9:21         ` Gene Chen
2020-08-25  9:34           ` Mark Brown [this message]
2020-08-25 10:01             ` Gene Chen
2020-08-25 10:08               ` Mark Brown
2020-08-25 11:07                 ` Gene Chen
2020-08-26 12:55 ` [PATCH v3 0/2] regulator: mt6360: Add support for MT6360 regulator Mark Brown

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=20200825093404.GB5379@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gene.chen.richtek@gmail.com \
    --cc=gene_chen@richtek.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.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).