From: Crystal Guo <crystal.guo@mediatek.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Crystal Guo <crystal.guo@mediatek.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: [v3,0/2] Add an interface to get current DDR data rate
Date: Wed, 26 Mar 2025 14:30:30 +0800 [thread overview]
Message-ID: <20250326063041.7126-1-crystal.guo@mediatek.com> (raw)
This series is based on linux-next, tag: next-20250324.
Vcore DVFS feature need know the current DDR data rate.
Add MediaTek DRAMC driver to provide an interface that can
obtain current DDR data rate.
---
Changes in v3:
- Move register offset, register mask and other SoC-dependent variables
to the platform data;
- Correct the spelling error.
---
Changes in v2:
- Remove pr_info and pr_err, use dev_err or dev_err_probe to print
error message;
- Replace module_init by module_platform_driver;
- Remove unnecessary global variables;
- Change fmeter-verison to platform data;
- Remove mtk-dramc.h;
- Refine compatible to "mediatek,mt8196-dramc";
- Refine CONFIG name to MEDIATEK_MC;
- Fix yaml build errors, remove unnecessary properties on yaml file.
Link to v2:
https://patchwork.kernel.org/patch/13964208
Crystal Guo (2):
dt-bindings: memory-controllers: Add MediaTek DRAM controller
interface
memory/mediatek: Add an interface to get current DDR data rate
.../memory-controllers/mediatek,dramc.yaml | 44 ++++
drivers/memory/Kconfig | 1 +
drivers/memory/Makefile | 1 +
drivers/memory/mediatek/Kconfig | 21 ++
drivers/memory/mediatek/Makefile | 2 +
drivers/memory/mediatek/mtk-dramc.c | 232 ++++++++++++++++++
6 files changed, 301 insertions(+)
create mode 100644 Documentation/devicetree/bindings/memory-controllers/mediatek,dramc.yaml
create mode 100644 drivers/memory/mediatek/Kconfig
create mode 100644 drivers/memory/mediatek/Makefile
create mode 100644 drivers/memory/mediatek/mtk-dramc.c
--
2.18.0
next reply other threads:[~2025-03-26 6:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 6:30 Crystal Guo [this message]
2025-03-26 6:30 ` [v3,1/2] dt-bindings: memory-controllers: Add MediaTek DRAM controller interface Crystal Guo
2025-03-26 7:56 ` Krzysztof Kozlowski
2025-03-26 10:17 ` AngeloGioacchino Del Regno
2025-03-26 10:27 ` Krzysztof Kozlowski
2025-03-26 10:18 ` AngeloGioacchino Del Regno
2025-04-02 3:51 ` Crystal Guo (郭晶)
2025-04-02 9:24 ` AngeloGioacchino Del Regno
2025-03-26 6:30 ` [v3,2/2] memory/mediatek: Add an interface to get current DDR data rate Crystal Guo
2025-03-26 10:27 ` AngeloGioacchino Del Regno
2025-04-02 3:36 ` Crystal Guo (郭晶)
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=20250326063041.7126-1-crystal.guo@mediatek.com \
--to=crystal.guo@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.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