linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: honghui.zhang@mediatek.com (Honghui Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 5/5] ARM: dts: mt2701: add iommu/smi dtsi node for mt2701
Date: Mon, 16 Jan 2017 10:48:50 +0800	[thread overview]
Message-ID: <1484534930.27576.1.camel@mtksdaap41> (raw)
In-Reply-To: <5a45da57-9262-b1ff-1c6a-c5c211c1bfd4@gmail.com>

On Fri, 2017-01-13 at 15:54 +0100, Matthias Brugger wrote:
> 
> On 04/07/16 10:00, Matthias Brugger wrote:
> >
> >
> > On 04/07/16 03:32, Honghui Zhang wrote:
> >> On Sun, 2016-07-03 at 21:12 +0200, Matthias Brugger wrote:
> >>>
> >>> On 07/03/2016 08:24 AM, Matthias Brugger wrote:
> >>>>
> >>>>
> >>>> On 06/08/2016 11:51 AM, honghui.zhang at mediatek.com wrote:
> >>>>> From: Honghui Zhang <honghui.zhang@mediatek.com>
> >>>>>
> >>>>> Add the dtsi node of iommu and smi for mt2701.
> >>>>>
> >>>>> Signed-off-by: Honghui Zhang <honghui.zhang@mediatek.com>
> >>>>> ---
> >>>>>   arch/arm/boot/dts/mt2701.dtsi | 51
> >>>>> +++++++++++++++++++++++++++++++++++++++++++
> >>>>>   1 file changed, 51 insertions(+)
> >>>>>
> >>>>
> >>>> Applied,
> >>>
> >>> Please resend the patch including the infracfg and mmsys node.
> >>>
> >>
> >> Hi, Matthias,
> >>
> >> Please hold this one.
> >> This one is based on CCF "arm: dts: mt2701: Add clock controller device
> >> nodes"[1] and power domain patch "Mediatek MT2701 SCPSYS power domain
> >> support v7"[2],
> >> But these two patchset are still being reviewed now.
> >>
> >> Do you think it's better that I send this one later after ccf and power
> >> domain patch got merged? I will send this patch later if it's OK with
> >> you.
> >>
> >
> > Sounds good.
> 
> Applied now to v4.10-next/dts32
> 
> Thanks.
> 

Thanks.

> >
> > Thanks a lot,
> > Matthias
> >
> >> Thanks.
> >> [1] https://patchwork.kernel.org/patch/9109081
> >> [2]
> >> http://lists.infradead.org/pipermail/linux-mediatek/2016-May/005429.html
> >>

      reply	other threads:[~2017-01-16  2:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08  9:50 [PATCH v4 0/5] MT2701 iommu support honghui.zhang at mediatek.com
2016-06-08  9:50 ` [PATCH v4 1/5] dt-bindings: mediatek: add descriptions for mediatek mt2701 iommu and smi honghui.zhang at mediatek.com
2016-06-08  9:50 ` [PATCH v4 2/5] iommu/mediatek: move the common struct into header file honghui.zhang at mediatek.com
2016-06-08  9:50 ` [PATCH v4 3/5] memory/mediatek: add support for mt2701 honghui.zhang at mediatek.com
2016-06-08  9:51 ` [PATCH v4 4/5] iommu/mediatek: add support for mtk iommu generation one HW honghui.zhang at mediatek.com
2016-06-08  9:51 ` [PATCH v4 5/5] ARM: dts: mt2701: add iommu/smi dtsi node for mt2701 honghui.zhang at mediatek.com
2016-06-21  9:41   ` Joerg Roedel
2016-06-21  9:55     ` Honghui Zhang
2016-06-21  9:57   ` Joerg Roedel
2016-06-22  5:45     ` Eddie Huang
2016-06-22  7:45       ` Honghui Zhang
2016-06-22  8:31         ` Joerg Roedel
2016-06-22  8:39           ` Honghui Zhang
2016-06-22  8:58             ` Joerg Roedel
2016-07-03  6:24   ` Matthias Brugger
2016-07-03 19:12     ` Matthias Brugger
2016-07-04  1:32       ` Honghui Zhang
2016-07-04  8:00         ` Matthias Brugger
2017-01-13 14:54           ` Matthias Brugger
2017-01-16  2:48             ` Honghui Zhang [this message]

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=1484534930.27576.1.camel@mtksdaap41 \
    --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).