From: Rob Herring <robh@kernel.org>
To: honghui.zhang@mediatek.com
Cc: joro@8bytes.org, treding@nvidia.com, mark.rutland@arm.com,
matthias.bgg@gmail.com, robin.murphy@arm.com,
p.zabel@pengutronix.de, devicetree@vger.kernel.org,
pebolle@tiscali.nl, kendrick.hsu@mediatek.com, arnd@arndb.de,
srv_heupstream@mediatek.com, catalin.marinas@arm.com,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
tfiga@google.com, iommu@lists.linux-foundation.org,
djkurtz@google.com, kernel@pengutronix.de,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, l.stach@pengutronix.de,
yingjoe.chen@mediatek.com, eddie.huang@mediatek.com,
youlin.pei@mediatek.com, erin.lo@mediatek.com
Subject: Re: [PATCH v2 1/5] dt-bindings: mediatek: add descriptions for mediatek mt2701 iommu and smi
Date: Mon, 23 May 2016 10:41:38 -0500 [thread overview]
Message-ID: <20160523154138.GA31426@rob-hp-laptop> (raw)
In-Reply-To: <1463658558-567-2-git-send-email-honghui.zhang@mediatek.com>
On Thu, May 19, 2016 at 07:49:14PM +0800, honghui.zhang@mediatek.com wrote:
> From: Honghui Zhang <honghui.zhang@mediatek.com>
>
> This patch defines the local arbitor port IDs for mediatek SoC MT2701 and
> add descriptions of binding for mediatek generation one iommu and smi.
>
> Signed-off-by: Honghui Zhang <honghui.zhang@mediatek.com>
> ---
> .../devicetree/bindings/iommu/mediatek,iommu.txt | 13 +++-
> .../memory-controllers/mediatek,smi-common.txt | 21 +++++-
> .../memory-controllers/mediatek,smi-larb.txt | 4 +-
> include/dt-bindings/memory/mt2701-larb-port.h | 85 ++++++++++++++++++++++
> 4 files changed, 115 insertions(+), 8 deletions(-)
> create mode 100644 include/dt-bindings/memory/mt2701-larb-port.h
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-05-23 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 11:49 [PATCH v2 0/5] MT2701 iommu support honghui.zhang
2016-05-19 11:49 ` [PATCH v2 1/5] dt-bindings: mediatek: add descriptions for mediatek mt2701 iommu and smi honghui.zhang
2016-05-23 15:41 ` Rob Herring [this message]
2016-05-19 11:49 ` [PATCH v2 2/5] iommu/mediatek: move the common struct into header file honghui.zhang
2016-05-19 11:49 ` [PATCH v2 3/5] memory/mediatek: add support for mt2701 honghui.zhang
2016-05-19 11:49 ` [PATCH v2 4/5] iommu/mediatek: add support for mtk iommu generation one HW honghui.zhang
2016-05-23 19:31 ` Robin Murphy
2016-05-24 9:57 ` Honghui Zhang
2016-05-24 15:36 ` Robin Murphy
2016-05-25 7:58 ` Honghui Zhang
2016-05-19 11:49 ` [PATCH 5/5] ARM: dts: mt2701: add iommu/smi dtsi node for mt2701 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=20160523154138.GA31426@rob-hp-laptop \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@google.com \
--cc=eddie.huang@mediatek.com \
--cc=erin.lo@mediatek.com \
--cc=honghui.zhang@mediatek.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kendrick.hsu@mediatek.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=pebolle@tiscali.nl \
--cc=robin.murphy@arm.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@google.com \
--cc=treding@nvidia.com \
--cc=will.deacon@arm.com \
--cc=yingjoe.chen@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