From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 4.4.y-cip 08/17] ARM: dts: r8a7744: Add SMP support
Date: Wed, 20 Nov 2019 15:44:03 +0100 [thread overview]
Message-ID: <20191120144402.GC4940@duo.ucw.cz> (raw)
In-Reply-To: <OSBPR01MB21036B733D92772413ABF197B84F0@OSBPR01MB2103.jpnprd01.prod.outlook.com>
Hi!
> > > + clock-latency = <300000>; /* 300 us */
> > > + power-domains = <&cpg_clocks>;
> > > + next-level-cache = <&L2_CA15>;
> > > +
> > > + /* kHz - uV - OPPs unknown yet */
> > > + operating-points = <1500000 1000000>,
> > > + <1312500 1000000>,
> > > + <1125000 1000000>,
> > > + < 937500 1000000>,
> > > + < 750000 1000000>,
> > > + < 375000 1000000>;
> > > + };
> >
> > Does this mean this is working progress and voltages will be lowered for
> > lower frequencies as testing proceeds?
>
> It supports only DFS not DVFS(ie, by controlling CPUFREQ register you can control the CPU frequency.)
If it does not support voltage scaling, is the /* kHz - uV - OPPs
unknown yet */ comment up-to-date? Would something like /* hardware
does not support voltage scaling */ be more useful?
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191120/4d0c5f95/attachment.sig>
next prev parent reply other threads:[~2019-11-20 14:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 14:53 [cip-dev] [PATCH 4.4.y-cip 00/17] Add SYS-DMAC/GPIO/AVB/SMP/SCIF/HSCIF/I2C/IIC/CMT/RWDT support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 01/17] dt-bindings: rcar-dmac: Document r8a7744 support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 02/17] ARM: dts: r8a7744: Add SYS-DMAC support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 03/17] dt-bindings: gpio: rcar: Add r8a7744 (RZ/G1N) support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 04/17] ARM: dts: r8a7744: Add GPIO support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 05/17] dt-bindings: net: ravb: Add support for r8a7744 SoC Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 06/17] ARM: dts: r8a7744: Add Ethernet AVB support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 07/17] dt-bindings: apmu: Document r8a7744 support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 08/17] ARM: dts: r8a7744: Add SMP support Biju Das
2019-11-20 14:36 ` Pavel Machek
2019-11-20 14:38 ` Biju Das
2019-11-20 14:44 ` Pavel Machek [this message]
2019-11-20 14:55 ` Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 09/17] ARM: dts: r8a7744: Add [H]SCIF{A|B} support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 10/17] dt-bindings: i2c: rcar: Document r8a7744 support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 11/17] dt-bindings: i2c: sh_mobile: " Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 12/17] ARM: dts: r8a7744: Add I2C and IIC support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 13/17] dt-bindings: timer: renesas, cmt: Document r8a7744 CMT Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 14/17] ARM: dts: r8a7744: Add CMT SoC specific support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 15/17] dt-bindings: watchdog: renesas-wdt: Document r8a7744 support Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 16/17] ARM: dts: r8a7744: Add RWDT node Biju Das
2019-11-19 14:53 ` [cip-dev] [PATCH 4.4.y-cip 17/17] ARM: dts: iwg20d-q7-common: Move cmt/rwdt node out of RZ/G1M SOM Biju Das
2019-11-20 14:38 ` [cip-dev] [PATCH 4.4.y-cip 00/17] Add SYS-DMAC/GPIO/AVB/SMP/SCIF/HSCIF/I2C/IIC/CMT/RWDT support Pavel Machek
2019-11-21 0:16 ` nobuhiro1.iwamatsu at toshiba.co.jp
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=20191120144402.GC4940@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.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