From: Gerard Marull-Paretas <gerard@teslabs.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Frank Li" <Frank.li@nxp.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] iio: magnetometer: mmc5633: Enable the VDD supply
Date: Sun, 22 Nov 2026 22:11:28 +0100 [thread overview]
Message-ID: <20261122211128.14591-1-gerard@teslabs.com> (raw)
In-Reply-To: <20261122205211.6c46f3cc@jic23-hlaptop>
On Sun, 22 Nov 2026 20:52:11 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> > #define MMC5633_WAIT_SET_RESET_US (1 * USEC_PER_MSEC)
> > +#define MMC5633_POWER_ON_US (5 * USEC_PER_MSEC)
>
> Obviously the line above isn't great on this, but is there a spec reference
> we can make for this timing?
Both datasheets list it in the "Operating Timing Diagram" table as tOp,
"Time to operate device after VDD valid", 5 ms minimum. I'll add a comment
referencing it in v3, and annotate the set/reset wait with tSR (1 ms
minimum, same table) while at it.
Thanks,
Gerard
next prev parent reply other threads:[~2026-11-22 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 19:08 [PATCH v2 0/3] iio: magnetometer: mmc5633: Binding, supply and mount matrix Gerard Marull-Paretas
2026-11-22 19:08 ` [PATCH v2 1/3] dt-bindings: iio: magnetometer: Add MEMSIC MMC5603 and MMC5633 Gerard Marull-Paretas
2026-11-22 19:08 ` [PATCH v2 2/3] iio: magnetometer: mmc5633: Enable the VDD supply Gerard Marull-Paretas
2026-11-22 20:52 ` Jonathan Cameron
2026-11-22 21:11 ` Gerard Marull-Paretas [this message]
2026-11-22 19:08 ` [PATCH v2 3/3] iio: magnetometer: mmc5633: Add mount matrix support Gerard Marull-Paretas
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=20261122211128.14591-1-gerard@teslabs.com \
--to=gerard@teslabs.com \
--cc=Frank.li@nxp.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@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