From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Nicolin Chen <nicoleotsuka@gmail.com>,
brian.austin@cirrus.com, Paul.Handrigan@cirrus.com,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
lgirdwood@gmail.com, Tim.Howe@cirrus.com, somduttar@nvidia.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v6] ASoC: cs53l30: Add codec driver support for Cirrus CS53L30
Date: Wed, 25 May 2016 19:16:03 +0100 [thread overview]
Message-ID: <20160525181603.GD8206@sirena.org.uk> (raw)
In-Reply-To: <20160525172800.GB3056@rob-hp-laptop>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
On Wed, May 25, 2016 at 12:28:00PM -0500, Rob Herring wrote:
> On Mon, May 23, 2016 at 04:13:57PM -0700, Nicolin Chen wrote:
> > + - VA-supply, VP-supply : power supplies for the device,
> > + as covered in Documentation/devicetree/bindings/regulator/regulator.txt.
> Also, these are missing from the example yet are required. I'd argue
> they should be optional as you could have designs with no regulator
> control.
The general rule is that regulators should only be omitted if they are
physically absent, we can describe simple fixed supplies with no control
so we should do so (though in practice Linux is much more forgiving and
will provide one if the supply is just plain missing from the DT). This
is a simpler rule for people to follow than making them officially
optional and is more robust in the face of things like implementation
changes that allow supplies to become controlable or drivers that
suddenly form a desire to look at their supply voltages, as well as
allowing other OSs to have simpler implementations if it's followed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-05-25 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 23:13 [PATCH v6] ASoC: cs53l30: Add codec driver support for Cirrus CS53L30 Nicolin Chen
2016-05-25 17:26 ` Rob Herring
2016-05-25 17:28 ` Rob Herring
2016-05-25 17:37 ` Nicolin Chen
2016-05-25 18:16 ` Mark Brown [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=20160525181603.GD8206@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Paul.Handrigan@cirrus.com \
--cc=Tim.Howe@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicoleotsuka@gmail.com \
--cc=pawel.moll@arm.com \
--cc=robh@kernel.org \
--cc=somduttar@nvidia.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