From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Yangtao Li <tiny.windzz@gmail.com>
Cc: wens@csie.org, robh+dt@kernel.org, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATVH v2 0/4] arm64: dts: allwinner: h6: Enable CPU
Date: Fri, 15 Feb 2019 16:13:57 +0100 [thread overview]
Message-ID: <20190215151357.noovkx3r6ia4boag@flea> (raw)
In-Reply-To: <20190215134937.10259-1-tiny.windzz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
On Fri, Feb 15, 2019 at 08:49:33AM -0500, Yangtao Li wrote:
> Add the cpufreq support of h6, source of information is as follows.
>
> h6 cpu opp info:
> https://github.com/Allwinner-Homlet/H6-BSP4.9-linux/blob/master/arch/arm64/boot/dts/sunxi/sun50iw6p1.dtsi
>
> axp805 spec:
> http://linux-sunxi.org/images/b/bc/AXP805_Datasheet_V1.0_en.pdf
Was that tested on the two H6 boards this time?
Adding a changelog between version is nice as well so that we can see
what you changed.
Thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-02-15 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 13:49 [PATVH v2 0/4] arm64: dts: allwinner: h6: Enable CPU Yangtao Li
2019-02-15 13:49 ` [PATVH v2 1/4] arm64: dts: allwinner: h6: orangepi: Add CPU supply regulator Yangtao Li
2019-02-15 13:49 ` [PATVH v2 2/4] arm64: dts: allwinner: h6: pine: " Yangtao Li
2019-02-15 13:49 ` [PATVH v2 3/4] arm64: dts: allwinner: h6: Add clock to CPU cores Yangtao Li
2019-02-15 13:49 ` [PATVH v2 4/4] arm64: dts: allwinner: h6: Add CPU Operating Performance Points table Yangtao Li
2019-02-15 15:13 ` Maxime Ripard [this message]
2019-02-15 15:35 ` [PATVH v2 0/4] arm64: dts: allwinner: h6: Enable CPU Frank Lee
2019-02-18 8:46 ` Maxime Ripard
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=20190215151357.noovkx3r6ia4boag@flea \
--to=maxime.ripard@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tiny.windzz@gmail.com \
--cc=wens@csie.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