From: Mark Brown <broonie@kernel.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Sowjanya Komatineni <skomatineni@nvidia.com>,
thierry.reding@gmail.com, jonathanh@nvidia.com,
frankc@nvidia.com, hverkuil@xs4all.nl, luca@lucaceresoli.net,
leonl@leopardimaging.com, robh+dt@kernel.org,
lgirdwood@gmail.com, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] dt-bindings: media: imx274: Add optional input clock and supplies
Date: Fri, 31 Jul 2020 17:28:36 +0100 [thread overview]
Message-ID: <20200731162836.GA4510@sirena.org.uk> (raw)
In-Reply-To: <20200731161908.GA6401@valkosipuli.retiisi.org.uk>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
On Fri, Jul 31, 2020 at 07:19:08PM +0300, Sakari Ailus wrote:
> > +- VANA-supply: Sensor 2.8v analog supply.
> > +- VDIG-supply: Sensor 1.8v digital core supply.
> > +- VDDL-supply: Sensor digital IO 1.2v supply.
> I believe lower case is preferred.
Either is fine from my POV. The code always used to use upper case but
it's not clear if that's the best choice when it makes its way into
bindings.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-31 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 17:01 [PATCH v3 1/3] media: i2c: imx274: Fix Y_OUT_SIZE register setting Sowjanya Komatineni
2020-07-20 17:01 ` [PATCH v3 2/3] dt-bindings: media: imx274: Add optional input clock and supplies Sowjanya Komatineni
2020-07-31 16:19 ` Sakari Ailus
2020-07-31 16:28 ` Mark Brown [this message]
2020-07-20 17:01 ` [PATCH v3 3/3] media: i2c: imx274: Add IMX274 power on and off sequence Sowjanya Komatineni
2020-07-21 14:03 ` Luca Ceresoli
2020-07-21 14:28 ` Sowjanya Komatineni
2020-07-31 16:26 ` Sakari Ailus
2020-07-31 16:34 ` Sowjanya Komatineni
2020-08-13 22:01 ` Sakari Ailus
2020-08-27 22:55 ` Sowjanya Komatineni
2020-08-31 16:25 ` Sowjanya Komatineni
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=20200731162836.GA4510@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frankc@nvidia.com \
--cc=hverkuil@xs4all.nl \
--cc=jonathanh@nvidia.com \
--cc=leonl@leopardimaging.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luca@lucaceresoli.net \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=skomatineni@nvidia.com \
--cc=thierry.reding@gmail.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).