From: Hector Martin <marcan@marcan.st>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Janne Grunau <j@jannau.net>, Sven Peter <sven@svenpeter.dev>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/4] arm64: dts: apple: t8103: Add i2c nodes
Date: Wed, 24 Nov 2021 14:42:12 +0900 [thread overview]
Message-ID: <f13b54bd-d776-0d06-113a-5ca2bcbccfcd@marcan.st> (raw)
In-Reply-To: <CACRpkdZghfRvox4aY4ROXYwFqiV6mnXZgw+42ZWYisXXgQ5+jQ@mail.gmail.com>
On 24/11/2021 08.26, Linus Walleij wrote:
> On Tue, Nov 23, 2021 at 3:43 PM Hector Martin <marcan@marcan.st> wrote:
>
>> For those following along in the list: the reason why i2c3 was getting
>> stuck is because it seems the unused bus is weakly pulled low on these
>> machines, which jams it.
>
> That looks like some power saving attempt.
>
> I suppose that means that even i2c buses that are in use
> could be weakly pulled low when suspending the system
> and maybe even inbetween transactions to save some
> leak current.
Pulled up vs. down dosn't really result in better power savings; neither
state will necessarily have more leakage. I think it's just that the
pins are completely disconnected, and there's some very minor leakage to
ground (megaohms will do) that ends up pulling them down.
Pulling down an I2C bus between transactions is not legal; the idle
state has to be high.
Apple are actually not very good at configuring GPIOs for power saving;
e.g. the I/Os for that unused i2c bus still have their input buffers
turned on, which is a waste of power. If they wanted to save the
smallest drop of power they'd turn that off. But the effect of this is
so trivial it probably makes no difference in the context of a laptop,
nevermind a desktop like the Mac Mini.
--
Hector Martin (marcan@marcan.st)
Public Key: https://mrcn.st/pub
next prev parent reply other threads:[~2021-11-24 5:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 22:58 [PATCH v3 0/4] Add DTs for all Apple M1 (t8103) devices Janne Grunau
2021-11-22 22:58 ` [PATCH v3 1/4] dt-bindings: arm: apple: Add iMac (24-inch 2021) to Apple bindings Janne Grunau
2021-11-22 22:58 ` [PATCH v3 2/4] arm64: dts: apple: Add missing M1 (t8103) devices Janne Grunau
2021-11-22 22:58 ` [PATCH v3 3/4] arm64: dts: apple: t8103: Add i2c nodes Janne Grunau
2021-11-23 4:47 ` Hector Martin
2021-11-23 5:41 ` Hector Martin
2021-11-23 14:41 ` Hector Martin
2021-11-23 23:26 ` Linus Walleij
2021-11-24 5:42 ` Hector Martin [this message]
2021-11-25 15:50 ` Linus Walleij
2021-11-25 16:01 ` Hector Martin "marcan"
2021-11-23 11:46 ` Sven Peter
2021-11-22 22:58 ` [PATCH v3 4/4] arm64: dts: apple: t8103: Add cd321x nodes Janne Grunau
2021-11-23 11:56 ` Sven Peter
2021-11-26 5:38 ` Hector Martin
2021-11-26 5:39 ` [PATCH v3 0/4] Add DTs for all Apple M1 (t8103) devices Hector Martin
2021-11-26 6:33 ` Janne Grunau
2021-11-26 6:50 ` Hector Martin
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=f13b54bd-d776-0d06-113a-5ca2bcbccfcd@marcan.st \
--to=marcan@marcan.st \
--cc=alyssa@rosenzweig.io \
--cc=devicetree@vger.kernel.org \
--cc=j@jannau.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sven@svenpeter.dev \
/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).