From: Chanwoo Choi <cwchoi00@gmail.com>
To: Samuel Holland <samuel@sholland.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-pm@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 6/6] PM / devfreq: Add a driver for the sun8i/sun50i MBUS
Date: Fri, 10 Dec 2021 15:57:00 +0900 [thread overview]
Message-ID: <21922806-e64c-1c41-1373-55603604cf34@gmail.com> (raw)
In-Reply-To: <20211118031841.42315-7-samuel@sholland.org>
On 21. 11. 18. 오후 12:18, Samuel Holland wrote:
> This driver works by adjusting the divider on the DRAM controller's
> module clock. Thus there is no fixed set of OPPs, only "full speed" down
> to "quarter speed" (or whatever the maximum divider is on that variant).
>
> It makes use of the MDFS hardware in the MBUS, in "DFS" mode, which
> takes care of updating registers during the critical section while DRAM
> is inaccessible.
>
> This driver should support several sunxi SoCs, starting with the A33,
> which have a DesignWare DDR3 controller with merged PHY register space
> and the matching MBUS register layout (so not A63 or later). However,
> the driver has only been tested on the A64/H5, so those are the only
> compatibles enabled for now.
>
> Acked-by: Chanwoo Choi <cw00.choi@samsung.com>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
> ---
> drivers/devfreq/Kconfig | 8 +
> drivers/devfreq/Makefile | 1 +
> drivers/devfreq/sun8i-a33-mbus.c | 511 +++++++++++++++++++++++++++++++
> 3 files changed, 520 insertions(+)
> create mode 100644 drivers/devfreq/sun8i-a33-mbus.c
>
(snip)
Applied it. Thanks.
--
Best Regards,
Samsung Electronics
Chanwoo Choi
prev parent reply other threads:[~2021-12-10 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 3:18 [PATCH v3 0/6] DRAM devfreq support for Allwinner A64/H5 Samuel Holland
2021-11-18 3:18 ` [PATCH v3 1/6] dt-bindings: clock: sunxi: Export CLK_DRAM for devfreq Samuel Holland
2021-11-23 10:40 ` (subset) " Maxime Ripard
2021-11-18 3:18 ` [PATCH v3 2/6] dt-bindings: arm: sunxi: Expand MBUS binding Samuel Holland
2021-11-18 13:58 ` Rob Herring
2021-11-23 10:40 ` (subset) " Maxime Ripard
2021-11-18 3:18 ` [PATCH v3 3/6] dt-bindings: arm: sunxi: Add H5 MBUS compatible Samuel Holland
2021-11-23 10:40 ` (subset) " Maxime Ripard
2021-11-18 3:18 ` [PATCH v3 4/6] ARM: dts: sunxi: h3/h5: Update MBUS node Samuel Holland
2021-11-23 10:40 ` (subset) " Maxime Ripard
2021-11-18 3:18 ` [PATCH v3 5/6] arm64: dts: allwinner: a64: " Samuel Holland
2021-11-23 10:40 ` (subset) " Maxime Ripard
2021-11-18 3:18 ` [PATCH v3 6/6] PM / devfreq: Add a driver for the sun8i/sun50i MBUS Samuel Holland
2021-12-10 6:57 ` Chanwoo Choi [this message]
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=21922806-e64c-1c41-1373-55603604cf34@gmail.com \
--to=cwchoi00@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--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;
as well as URLs for NNTP newsgroup(s).