From: honghui.zhang@mediatek.com (honghui.zhang at mediatek.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] Add larbid init routine for mediatek's gen1 smi larb driver
Date: Fri, 28 Jul 2017 18:55:40 +0800 [thread overview]
Message-ID: <1501239343-9190-1-git-send-email-honghui.zhang@mediatek.com> (raw)
From: Honghui Zhang <honghui.zhang@mediatek.com>
Mediatek's gen1 smi need the hardware larbid to identify the offset for
the register which controls whether enable iommu for this larb.
In the commit 3c8f4ad85c4b ("memory/mediatek: add support for mt2701"),
the larbid was used without properly initialized. This patchset fixed
that.
This patchset was based on the v2 version of the patch:
memory: mtk-smi: Use of_device_get_match_data helper[1],
which was base on 4.13-rc1
[1] https://patchwork.kernel.org/patch/9864719
Change since v1:
- Using mtk_smi_larb_gen to identify whether larbid was needed instead of
checking hard code bindings.
Honghui Zhang (3):
memory: mtk-smi: add larbid handle routine
dt-bindings: mediatek: add descriptions for larbid
arm: dts: mediatek: add larbid property for larb
.../bindings/memory-controllers/mediatek,smi-larb.txt | 15 +++++++++++++++
arch/arm/boot/dts/mt2701.dtsi | 3 +++
drivers/memory/mtk-smi.c | 12 ++++++++++++
3 files changed, 30 insertions(+)
--
2.6.4
next reply other threads:[~2017-07-28 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 10:55 honghui.zhang at mediatek.com [this message]
2017-07-28 10:55 ` [PATCH v2 1/3] memory: mtk-smi: add larbid handle routine honghui.zhang at mediatek.com
2017-07-31 9:32 ` Matthias Brugger
2017-07-28 10:55 ` [PATCH v2 2/3] dt-bindings: mediatek: add descriptions for larbid honghui.zhang at mediatek.com
2017-07-28 10:55 ` [PATCH v2 3/3] arm: dts: mediatek: add larbid property for larb honghui.zhang at mediatek.com
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=1501239343-9190-1-git-send-email-honghui.zhang@mediatek.com \
--to=honghui.zhang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.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).