[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170727125812.GD21502@8bytes.org>
Date: Thu, 27 Jul 2017 14:58:12 +0200
From: Joerg Roedel <joro@...tes.org>
To: honghui.zhang@...iatek.com
Cc: matthias.bgg@...il.com, robh@...nel.org, robin.murphy@....com,
devicetree@...r.kernel.org, kendrick.hsu@...iatek.com,
srv_heupstream@...iatek.com, will.deacon@....com,
linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
robh+dt@...nel.org, linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, youlin.pei@...iatek.com,
erin.lo@...iatek.com, yong.wu@...iatek.com,
xinping.qian@...iatek.com
Subject: Re: [PATCH 0/3] Add larbid init routine for mediatek's gen1 smi larb
driver
On Thu, Jul 27, 2017 at 10:01:09AM +0800, honghui.zhang@...iatek.com wrote:
> From: Honghui Zhang <honghui.zhang@...iatek.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
Powered by blists - more mailing lists