From: Joerg Roedel <joro@8bytes.org>
To: honghui.zhang@mediatek.com
Cc: matthias.bgg@gmail.com, robh@kernel.org, robin.murphy@arm.com,
devicetree@vger.kernel.org, kendrick.hsu@mediatek.com,
srv_heupstream@mediatek.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
robh+dt@kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, youlin.pei@mediatek.com,
erin.lo@mediatek.com, yong.wu@mediatek.com,
xinping.qian@mediatek.com
Subject: Re: [PATCH 0/3] Add larbid init routine for mediatek's gen1 smi larb driver
Date: Thu, 27 Jul 2017 14:58:12 +0200 [thread overview]
Message-ID: <20170727125812.GD21502@8bytes.org> (raw)
In-Reply-To: <1501120872-19652-1-git-send-email-honghui.zhang@mediatek.com>
On Thu, Jul 27, 2017 at 10:01:09AM +0800, honghui.zhang@mediatek.com wrote:
> 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.
>
> Honghui Zhang (3):
> memory: mtk-smi: add larbid init routine
> dt-bindings: mediatek: add descriptions for larbid
> arm: dts: mediatek: add larbid property for larb
What are these patches based on? They don't apply to v4.13-rc2.
Joerg
next prev parent reply other threads:[~2017-07-27 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 2:01 [PATCH 0/3] Add larbid init routine for mediatek's gen1 smi larb driver honghui.zhang-NuS5LvNUpcJWk0Htik3J/w
[not found] ` <1501120872-19652-1-git-send-email-honghui.zhang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-07-27 2:01 ` [PATCH 1/3] memory: mtk-smi: add larbid init routine honghui.zhang-NuS5LvNUpcJWk0Htik3J/w
[not found] ` <1501120872-19652-2-git-send-email-honghui.zhang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-07-27 15:42 ` Matthias Brugger
[not found] ` <f7dac4d6-4ef8-e10d-e483-088120392ab2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-07-28 1:15 ` Honghui Zhang
2017-07-28 9:59 ` Robin Murphy
[not found] ` <a4a00e4b-175c-88d3-d2b4-9f4f1c41a935-5wv7dgnIgG8@public.gmane.org>
2017-07-28 10:38 ` Honghui Zhang
2017-07-27 2:01 ` [PATCH 2/3] dt-bindings: mediatek: add descriptions for larbid honghui.zhang-NuS5LvNUpcJWk0Htik3J/w
2017-07-27 2:01 ` [PATCH 3/3] arm: dts: mediatek: add larbid property for larb honghui.zhang
2017-07-27 12:58 ` Joerg Roedel [this message]
[not found] ` <20170727125812.GD21502-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-07-28 0:55 ` [PATCH 0/3] Add larbid init routine for mediatek's gen1 smi larb driver Honghui Zhang
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=20170727125812.GD21502@8bytes.org \
--to=joro@8bytes.org \
--cc=devicetree@vger.kernel.org \
--cc=erin.lo@mediatek.com \
--cc=honghui.zhang@mediatek.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kendrick.hsu@mediatek.com \
--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+dt@kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=srv_heupstream@mediatek.com \
--cc=will.deacon@arm.com \
--cc=xinping.qian@mediatek.com \
--cc=yong.wu@mediatek.com \
--cc=youlin.pei@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).