linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Po-Kai Chi <pk.chi@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <wsd_upstream@mediatek.com>,
	CC Hwang <cc.hwang@mediatek.com>,
	Loda Chou <loda.chou@mediatek.com>,
	Po-Kai Chi <pk.chi@mediatek.com>
Subject: [PATCH v1] memory: mediatek: add DRAM controller driver
Date: Tue, 30 Mar 2021 13:22:07 +0800	[thread overview]
Message-ID: <1617081731-7408-1-git-send-email-pk.chi@mediatek.com> (raw)

These patch series introduces the MediaTek DRAM controller driver (DRAMC)
on MT6779 SoC, and enables to be built as a module by default for the
ARM64 builds.

MediaTek DRAMC driver provides cross-platform features as below:
  - API provided to other kernel modules for querying DRAM type,
    rank count, rank size, channel count and mode register settings.
  - Sysfs interface used to pass DRAM mode register settings and current
    DRAM data rate to user-space for MediaTek ecosystem.

The API user includes MediaTek External Memory Interface (EMI) and
DVFS Resource Control (DVFSRC), which will be sent to mainline later.


             reply	other threads:[~2021-03-30  5:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30  5:22 Po-Kai Chi [this message]
2021-03-30  5:22 ` [PATCH v1 1/4] dt-bindings: memory: Add binding for MediaTek Common DRAM Controller Po-Kai Chi
2021-03-30 13:08   ` Rob Herring
2021-03-30 13:58   ` Rob Herring
2021-04-01  8:52     ` Po-Kai Chi
2021-03-30  5:22 ` [PATCH v1 2/4] memory: mediatek: add DRAM controller driver Po-Kai Chi
2021-03-30  5:22 ` [PATCH v1 3/4] arm64: dts: add DRAMC node for MT6779 Po-Kai Chi
2021-03-30  5:22 ` [PATCH v1 4/4] arm64: defconfig: Enable MediaTek DRAMC common driver Po-Kai Chi

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=1617081731-7408-1-git-send-email-pk.chi@mediatek.com \
    --to=pk.chi@mediatek.com \
    --cc=cc.hwang@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=loda.chou@mediatek.com \
    --cc=matthias.bgg@gmail.com \
    --cc=wsd_upstream@mediatek.com \
    /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).