From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: paul.j.murphy@intel.com, daniele.alessandrelli@intel.com,
mchehab@kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org
Cc: robert.foss@linaro.org, hfink@snap.com, jgrahsl@snap.com,
dmitry.baryshkov@linaro.org, vladimir.zapolskiy@linaro.org,
bryan.odonoghue@linaro.org
Subject: [RESEND PATCH 0/2] media: i2c: imx412: Add regulator control to imx412
Date: Sun, 10 Apr 2022 17:35:51 +0100 [thread overview]
Message-ID: <20220410163553.3501938-1-bryan.odonoghue@linaro.org> (raw)
The imx412 has three regulators which depending on platform may need to be
individually enabled.
- dovdd
- avdd
- dvdd
Existing code for an Intel platform doesn't appear to need to enable these
rails directly. On my reference hardware, a Qualcomm Thundercomm RB5 some
of these rails do need to be enabled individually.
Add in the above named rails as optional in the YAML in the first patch
along with code to switch them on in the second patch.
Existing imx412 users should get dummy regulators populated which the
regulator_bulk_enable()/regulator_bulk_disable() code can safely ignore.
Resend + devicetree@vger.kernel.org
Bryan O'Donoghue (2):
media: dt-bindings: imx412: Add regulator descriptions
media: i2c: imx412: Add bulk regulator support
.../bindings/media/i2c/sony,imx412.yaml | 12 ++++++
drivers/media/i2c/imx412.c | 38 +++++++++++++++++++
2 files changed, 50 insertions(+)
--
2.35.1
next reply other threads:[~2022-04-10 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 16:35 Bryan O'Donoghue [this message]
2022-04-10 16:35 ` [RESEND PATCH 1/2] media: dt-bindings: imx412: Add regulator descriptions Bryan O'Donoghue
2022-04-10 18:43 ` Krzysztof Kozlowski
2022-04-11 0:48 ` Bryan O'Donoghue
2022-04-10 16:35 ` [RESEND PATCH 2/2] media: i2c: imx412: Add bulk regulator support Bryan O'Donoghue
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=20220410163553.3501938-1-bryan.odonoghue@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=daniele.alessandrelli@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=hfink@snap.com \
--cc=jgrahsl@snap.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=paul.j.murphy@intel.com \
--cc=robert.foss@linaro.org \
--cc=vladimir.zapolskiy@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.