From: Drew Fustini <dfustini@baylibre.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Dave Gerlach <d-gerlach@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Drew Fustini <dfustini@baylibre.com>
Subject: [PATCH v3 0/2] soc: ti: wkup_m3_ipc: support i2c voltage scaling
Date: Tue, 26 Apr 2022 13:07:40 -0700 [thread overview]
Message-ID: <20220426200741.712842-1-dfustini@baylibre.com> (raw)
Allow loading of a binary file containing i2c scaling sequences to be
provided to the Cortex-M3 firmware in order to properly scale voltage
rails on the PMIC during low power modes like DeepSleep0.
The 'firmware-name' property which contains the name of a binary file.
A prerequisite for this series is:
[PATCH v3 0/2] soc: ti: wkup_m3_ipc: Add support for IO Isolation
https://lore.kernel.org/linux-devicetree/20220414192722.2978837-1-dfustini@baylibre.com/
Changes from v2:
- correct the name of the property in the commit message of the bindings
patch to firmware-name instead of the old ti,scale-data-fw property
Changes from v1:
- change 'ti,scale-data-fw' to 'firmware-name'
- add 'firmware-name' property to the examples
Dave Gerlach (2):
dt-bindings: wkup-m3-ipc: Add firmware-name property
soc: ti: wkup_m3_ipc: Add support for i2c voltage scaling
.../bindings/soc/ti/wkup-m3-ipc.yaml | 12 +++
drivers/soc/ti/wkup_m3_ipc.c | 93 ++++++++++++++++++-
include/linux/wkup_m3_ipc.h | 9 ++
3 files changed, 113 insertions(+), 1 deletion(-)
--
2.32.0
next reply other threads:[~2022-04-26 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 20:07 Drew Fustini [this message]
2022-04-26 20:07 ` [PATCH v3 1/2] dt-bindings: wkup-m3-ipc: Add firmware-name property Drew Fustini
2022-04-29 22:18 ` Rob Herring
2022-04-26 20:07 ` [PATCH v3 2/2] soc: ti: wkup_m3_ipc: Add support for i2c voltage scaling Drew Fustini
2022-05-03 13:09 ` (subset) [PATCH v3 0/2] soc: ti: wkup_m3_ipc: support " Nishanth Menon
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=20220426200741.712842-1-dfustini@baylibre.com \
--to=dfustini@baylibre.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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).