From: Paul Cercueil <paul@crapouillou.net>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: list@opendingux.net, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Conor Dooley <conor+dt@kernel.org>,
linux-mips@vger.kernel.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Paul Boddie <paul@boddie.org.uk>,
Paul Burton <paulburton@kernel.org>,
Christophe Branchereau <cbranchereau@gmail.com>
Subject: Re: [PATCH 0/9] MIPS: CI20: Add WiFi / Bluetooth support
Date: Sun, 18 Jun 2023 15:58:01 +0200 [thread overview]
Message-ID: <5511fba10119cdc08a18ea2cca98fed343f9cd33.camel@crapouillou.net> (raw)
In-Reply-To: <ebf776a8fb8dee045e7661daaca4564fe39917a6.camel@crapouillou.net>
Hi All,
[...]
> Looking at the JZ4780_DS.PDF file, the SoC actually wants 1.1V so the
> DT is not wrong - in theory. But in practice it does not work, as you
> experienced yourself. However, if the ACT8600 defaults to 1.2V, or if
> the bootloader configures it to 1.2V, I would think that this is
> actually a voltage that the SoC can handle - otherwise the SoC would
> be
> overvolted until the kernel starts, and the board design would be
> flawed.
>
> I measured that the old 3.x kernel keeps the SoC voltage at 1.2V, so
> it
> sounds like a better default. Therefore the fix here would be to
> raise
> the DCDC1 regulator to 1.2V.
>
> I'll send a patch later today.
After a talk with Christophe (Cc'd), I changed my mind.
A +100 mV overvolt is a *huge* step up, and although the SoC doesn't
burst into flames, it could very well reduce its life span.
I used to have huge stability issues (kernel not booting to userspace
half the times, or just plain reboots after a few minutes of uptime)
and I now realize it's because I was running the core at 1.1V, because
these issues disappeared the moment I switched to 1.2V.
However, I am now running at 1.125 volts, which is just 25mV above the
nominal voltage - and it's been extremely stable so far.
Nikolaus: could you test at 1.125 volts? If it's stable for you as
well, I'd suggest to use this as the new default.
Paul (Burton): As you wrote most of the drivers (and uboot?) for the
board, do you know why VDDCORE was set to 1.2V?
Cheers,
-Paul
next prev parent reply other threads:[~2023-06-18 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230615084006.79194526F801@goldelico.com>
2023-06-15 8:45 ` H. Nikolaus Schaller
2023-06-15 9:14 ` H. Nikolaus Schaller
2023-06-15 12:28 ` H. Nikolaus Schaller
2023-06-16 20:21 ` H. Nikolaus Schaller
2023-06-17 10:45 ` H. Nikolaus Schaller
2023-06-18 11:51 ` Paul Cercueil
2023-06-18 13:58 ` Paul Cercueil [this message]
2023-06-19 4:42 ` H. Nikolaus Schaller
2023-06-19 4:42 ` H. Nikolaus Schaller
[not found] <E1q9iWM-0004zB-00@elvis.franken.de>
2023-06-15 9:08 ` Thomas Bogendoerfer
2023-06-15 9:32 ` H. Nikolaus Schaller
2023-06-04 14:56 Paul Cercueil
2023-06-09 8:23 ` Thomas Bogendoerfer
2023-06-15 7:08 ` H. Nikolaus Schaller
2023-06-15 7:00 ` H. Nikolaus Schaller
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=5511fba10119cdc08a18ea2cca98fed343f9cd33.camel@crapouillou.net \
--to=paul@crapouillou.net \
--cc=cbranchereau@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=list@opendingux.net \
--cc=paul@boddie.org.uk \
--cc=paulburton@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®