From: nnet <nnet@fastmail.fm>
To: "Pali Rohár" <pali@kernel.org>
Cc: a.heider@gmail.com, andrew@lunn.ch, gerald@gk2.net,
gregory.clement@bootlin.com, kabel@kernel.org,
kostap@marvell.com, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
luka.perkov@sartura.hr, miquel.raynal@bootlin.com,
mturquette@baylibre.com, rmk+kernel@armlinux.org.uk,
sboyd@kernel.org, tmn505@gmail.com, vladimir.vid@sartura.hr
Subject: Re: [PATCH mvebu v2 00/10] Armada 37xx: Fix cpufreq changing base CPU speed to 800 MHz from 1000 MHz
Date: Tue, 09 Feb 2021 14:52:56 -0800 [thread overview]
Message-ID: <93745280-dbe9-491c-a79d-c9c364b83880@www.fastmail.com> (raw)
In-Reply-To: <20210209224223.p22yhjdy7ibzepss@pali>
On Tue, Feb 9, 2021, at 2:42 PM, Pali Rohár wrote:
> On Tuesday 09 February 2021 13:45:08 nnet wrote:
> > On Tue, Feb 9, 2021, at 1:33 PM, Pali Rohár wrote:
> > > On Tuesday 09 February 2021 13:00:26 nnet wrote:
> > > > > If you have other Armada 3720 boards (Espressobin v5/v7, uDPU, Devel Board, ...) then it will be nice to do an additional tests and check if instability issues are finally fixed.
> > > >
> > > > These patches applied to the 5.4.96 in OpenWrt (98d61b5) work fine so far on an Espressobin v7 AFAICT per changing values in /sys/devices/system/cpu/cpufreq/policy0.
> > > >
> > > > Are these changes intended to work @1.2 GHz on the v7?
> > >
> > > Hello! Do you have 1.2 GHz A3720 SoC?
> >
> > Maybe (not)? ESPRESSObin_V7_1-0 on the underside.
>
> Look at the package of SoC chip. On top of the package is printed
> identifier 88F3720. On the last line should be one of the string:
> C080, C100, C120, I080, I100 which identifies frequency
> (080 = 800 MHz, 100 = 1 GHz, 120 = 1.2 GHz)
>
> Can you check what is printed on A3720 SoC package?
Both of mine are 88F3720-A0-C120.
WARNING: multiple messages have this Message-ID (diff)
From: nnet <nnet@fastmail.fm>
To: "Pali Rohár" <pali@kernel.org>
Cc: kabel@kernel.org, andrew@lunn.ch, luka.perkov@sartura.hr,
sboyd@kernel.org, gregory.clement@bootlin.com,
a.heider@gmail.com, linux-kernel@vger.kernel.org,
vladimir.vid@sartura.hr, mturquette@baylibre.com,
rmk+kernel@armlinux.org.uk, tmn505@gmail.com, gerald@gk2.net,
miquel.raynal@bootlin.com, kostap@marvell.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH mvebu v2 00/10] Armada 37xx: Fix cpufreq changing base CPU speed to 800 MHz from 1000 MHz
Date: Tue, 09 Feb 2021 14:52:56 -0800 [thread overview]
Message-ID: <93745280-dbe9-491c-a79d-c9c364b83880@www.fastmail.com> (raw)
In-Reply-To: <20210209224223.p22yhjdy7ibzepss@pali>
On Tue, Feb 9, 2021, at 2:42 PM, Pali Rohár wrote:
> On Tuesday 09 February 2021 13:45:08 nnet wrote:
> > On Tue, Feb 9, 2021, at 1:33 PM, Pali Rohár wrote:
> > > On Tuesday 09 February 2021 13:00:26 nnet wrote:
> > > > > If you have other Armada 3720 boards (Espressobin v5/v7, uDPU, Devel Board, ...) then it will be nice to do an additional tests and check if instability issues are finally fixed.
> > > >
> > > > These patches applied to the 5.4.96 in OpenWrt (98d61b5) work fine so far on an Espressobin v7 AFAICT per changing values in /sys/devices/system/cpu/cpufreq/policy0.
> > > >
> > > > Are these changes intended to work @1.2 GHz on the v7?
> > >
> > > Hello! Do you have 1.2 GHz A3720 SoC?
> >
> > Maybe (not)? ESPRESSObin_V7_1-0 on the underside.
>
> Look at the package of SoC chip. On top of the package is printed
> identifier 88F3720. On the last line should be one of the string:
> C080, C100, C120, I080, I100 which identifies frequency
> (080 = 800 MHz, 100 = 1 GHz, 120 = 1.2 GHz)
>
> Can you check what is printed on A3720 SoC package?
Both of mine are 88F3720-A0-C120.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-10 1:21 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 21:00 [PATCH mvebu v2 00/10] Armada 37xx: Fix cpufreq changing base CPU speed to 800 MHz from 1000 MHz nnet
2021-02-09 21:33 ` Pali Rohár
2021-02-09 21:33 ` Pali Rohár
2021-02-09 21:45 ` nnet
2021-02-09 21:45 ` nnet
2021-02-09 22:42 ` Pali Rohár
2021-02-09 22:42 ` Pali Rohár
2021-02-09 22:52 ` nnet [this message]
2021-02-09 22:52 ` nnet
2021-02-09 22:56 ` Pali Rohár
2021-02-09 22:56 ` Pali Rohár
2021-02-09 23:16 ` nnet
2021-02-09 23:16 ` nnet
2021-02-09 23:26 ` Marek Behún
2021-02-09 23:26 ` Marek Behún
2021-02-10 1:31 ` nnet
2021-02-10 1:31 ` nnet
2021-02-10 1:51 ` nnet
2021-02-10 1:51 ` nnet
2021-02-10 2:07 ` nnet
2021-02-10 2:07 ` nnet
2021-02-10 9:23 ` Pali Rohár
2021-02-10 9:23 ` Pali Rohár
2021-02-10 17:34 ` nnet
2021-02-10 17:34 ` nnet
2021-02-10 18:03 ` Pali Rohár
2021-02-10 18:03 ` Pali Rohár
2021-02-10 19:08 ` nnet
2021-02-10 19:08 ` nnet
2021-02-10 19:18 ` Marek Behún
2021-02-10 19:18 ` Marek Behún
2021-02-11 19:55 ` Pali Rohár
2021-02-11 19:55 ` Pali Rohár
2021-02-11 20:22 ` nnet
2021-02-11 20:22 ` nnet
2021-02-11 23:44 ` Pali Rohár
2021-02-11 23:44 ` Pali Rohár
2021-02-12 0:41 ` nnet
2021-02-12 0:41 ` nnet
2021-02-13 10:01 ` Pali Rohár
2021-02-13 10:01 ` Pali Rohár
2021-02-13 18:30 ` nnet
2021-02-13 18:30 ` nnet
2021-02-14 12:33 ` Pali Rohár
2021-02-14 12:33 ` Pali Rohár
2021-02-16 5:48 ` nnet
2021-02-16 5:48 ` nnet
2021-02-16 10:41 ` Pali Rohár
2021-02-16 10:41 ` Pali Rohár
2021-02-16 16:27 ` nnet
2021-02-16 16:27 ` nnet
2021-02-19 19:33 ` Pali Rohár
2021-02-19 19:33 ` Pali Rohár
2021-02-22 3:17 ` nnet
2021-02-22 3:17 ` nnet
2021-02-22 9:51 ` Pali Rohár
2021-02-22 9:51 ` Pali Rohár
2021-02-22 16:36 ` nnet
2021-02-22 16:36 ` nnet
2021-02-22 16:40 ` Philip Soares
2021-02-22 16:40 ` Philip Soares
2021-02-10 2:12 ` Marek Behún
2021-02-10 2:12 ` Marek Behún
-- strict thread matches above, loose matches on Subject: below --
2021-01-14 12:40 Pali Rohár
2021-01-14 12:40 ` Pali Rohár
2021-02-01 14:35 ` Tomasz Maciej Nowak
2021-02-01 14:35 ` Tomasz Maciej Nowak
2021-02-03 19:29 ` Anders Trier Olesen
2021-02-03 19:29 ` Anders Trier Olesen
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=93745280-dbe9-491c-a79d-c9c364b83880@www.fastmail.com \
--to=nnet@fastmail.fm \
--cc=a.heider@gmail.com \
--cc=andrew@lunn.ch \
--cc=gerald@gk2.net \
--cc=gregory.clement@bootlin.com \
--cc=kabel@kernel.org \
--cc=kostap@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=miquel.raynal@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=pali@kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=sboyd@kernel.org \
--cc=tmn505@gmail.com \
--cc=vladimir.vid@sartura.hr \
/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.