From: Simon Arlott <simon@fire.lp0.eu>
To: Mark Brown <broonie@kernel.org>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
linux-kernel@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
Jonas Gorski <jogo@openwrt.org>
Subject: Re: [PATCH 1/2] regulator: Add brcm,bcm63xx-regulator device tree binding
Date: Thu, 3 Dec 2015 23:51:16 +0000 [thread overview]
Message-ID: <5660D574.7030803@simon.arlott.org.uk> (raw)
In-Reply-To: <20151203234548.GJ5727@sirena.org.uk>
On 03/12/15 23:45, Mark Brown wrote:
> On Thu, Dec 03, 2015 at 11:38:28PM +0000, Simon Arlott wrote:
>
>> #define MISC_IDDQ_CTRL_GMAC (1<<18)
>> #define MISC_IDDQ_CTRL_WLAN_PADS (1<<13)
>> #define MISC_IDDQ_CTRL_PCIE (1<<12)
>> #define MISC_IDDQ_CTRL_FAP (1<<11)
>> #define MISC_IDDQ_CTRL_VDSL_MIPS (1<<10)
>> #define MISC_IDDQ_CTRL_VDSL_PHY (1<<9)
>> #define MISC_IDDQ_CTRL_PERIPH (1<<8)
>> #define MISC_IDDQ_CTRL_PCM (1<<7)
>> #define MISC_IDDQ_CTRL_ROBOSW (1<<6)
>> #define MISC_IDDQ_CTRL_USBD (1<<5)
>> #define MISC_IDDQ_CTRL_USBH (1<<4)
>> #define MISC_IDDQ_CTRL_DECT (1<<3)
>> #define MISC_IDDQ_CTRL_MIPS (1<<2)
>> #define MISC_IDDQ_CTRL_IPSEC (1<<1)
>> #define MISC_IDDQ_CTRL_SAR (1<<0)
>
> Are you *sure* these are regulators and not power domains? These names
> look a lot like they could be power domains.
No, I'm not sure. Some of them are may actually be regulators (the "PHY"
ones) while others are almost definitely power domains (like the "FAP"
Forwarding Assist Processor).
--
Simon Arlott
next prev parent reply other threads:[~2015-12-03 23:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 21:13 [PATCH 1/2] regulator: Add regmap support to regulator-fixed device tree binding Simon Arlott
2015-11-28 21:14 ` [PATCH 2/2] regulator: fixed: Add support for regmap Simon Arlott
2015-11-30 12:10 ` [PATCH 1/2] regulator: Add regmap support to regulator-fixed device tree binding Mark Brown
2015-11-30 20:30 ` [PATCH 1/2] regulator: Add brcm,bcm63xx-regulator " Simon Arlott
2015-11-30 20:30 ` [PATCH 2/2] regulator: bcm63xx: Add BCM63xx fixed regulator device Simon Arlott
2015-11-30 20:38 ` [PATCH (v2) " Simon Arlott
2015-12-01 15:11 ` Mark Brown
2015-12-01 22:16 ` [PATCH 1/2] regulator: Add brcm,bcm63xx-regulator device tree binding Mark Brown
2015-12-02 12:45 ` Simon Arlott
2015-12-02 12:53 ` Mark Brown
2015-12-02 20:26 ` Simon Arlott
2015-12-03 0:06 ` Mark Brown
2015-12-03 8:14 ` Simon Arlott
2015-12-03 15:05 ` Mark Brown
2015-12-03 23:38 ` Simon Arlott
2015-12-03 23:45 ` Mark Brown
2015-12-03 23:51 ` Simon Arlott [this message]
2015-12-04 11:00 ` Mark Brown
2015-12-04 12:26 ` Simon Arlott
2015-12-04 14:31 ` 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=5660D574.7030803@simon.arlott.org.uk \
--to=simon@fire.lp0.eu \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jogo@openwrt.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 \
/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).