From: xiaolei li <xiaolei.li@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: <boris.brezillon@free-electrons.com>,
<computersforpeace@gmail.com>, <dwmw2@infradead.org>,
<linux-mtd@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <robh+dt@kernel.org>,
<rogercc.lin@mediatek.com>, <yt.shen@mediatek.com>,
<srv_heupstream@mediatek.com>
Subject: Re: [PATCH v4 1/4] mtd: nand: mediatek: update DT bindings
Date: Wed, 7 Jun 2017 15:24:57 +0800 [thread overview]
Message-ID: <1496820297.28992.1.camel@mhfsdcap03> (raw)
In-Reply-To: <e9286a90-8829-8b37-476a-ac8bd057d341@gmail.com>
Hi Mattias,
On Tue, 2017-06-06 at 12:55 +0200, Matthias Brugger wrote:
>
> On 31/05/17 05:37, Xiaolei Li wrote:
> > Add MT2712 NAND Flash Controller dt bindings documentation.
> >
> > Signed-off-by: Xiaolei Li <xiaolei.li@mediatek.com>
> > Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> > ---
>
> Subject line should be something like;
> dt-bindings: mtd: Update mediatek bindings.
This patch has been accepted on PATCH v5 by Boris. So, should I send
PATCH v6?
Thanks.
>
> > Documentation/devicetree/bindings/mtd/mtk-nand.txt | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/mtd/mtk-nand.txt b/Documentation/devicetree/bindings/mtd/mtk-nand.txt
> > index 069c192..dbf9e05 100644
> > --- a/Documentation/devicetree/bindings/mtd/mtk-nand.txt
> > +++ b/Documentation/devicetree/bindings/mtd/mtk-nand.txt
> > @@ -12,7 +12,8 @@ tree nodes.
> >
> > The first part of NFC is NAND Controller Interface (NFI) HW.
> > Required NFI properties:
> > -- compatible: Should be "mediatek,mtxxxx-nfc".
> > +- compatible: Should be one of "mediatek,mt2701-nfc",
> > + "mediatek,mt2712-nfc".
> > - reg: Base physical address and size of NFI.
> > - interrupts: Interrupts of NFI.
> > - clocks: NFI required clocks.
> > @@ -141,7 +142,7 @@ Example:
> > ==============
> >
> > Required BCH properties:
> > -- compatible: Should be "mediatek,mtxxxx-ecc".
> > +- compatible: Should be one of "mediatek,mt2701-ecc", "mediatek,mt2712-ecc".
> > - reg: Base physical address and size of ECC.
> > - interrupts: Interrupts of ECC.
> > - clocks: ECC required clocks.
> >
next prev parent reply other threads:[~2017-06-07 7:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 3:37 [PATCH v4 0/4] Mediatek MT2712 NAND FLASH Controller driver Xiaolei Li
2017-05-31 3:37 ` [PATCH v4 1/4] mtd: nand: mediatek: update DT bindings Xiaolei Li
2017-06-06 10:55 ` Matthias Brugger
2017-06-07 7:24 ` xiaolei li [this message]
2017-06-07 7:34 ` Boris Brezillon
2017-06-07 7:37 ` xiaolei li
2017-05-31 3:37 ` [PATCH v4 2/4] mtd: nand: mediatek: refine register NFI_PAGEFMT setting Xiaolei Li
2017-05-31 3:37 ` [PATCH v4 3/4] mtd: nand: mediatek: add support for different MTK NAND FLASH Controller IP Xiaolei Li
2017-05-31 6:12 ` Boris Brezillon
2017-05-31 6:52 ` xiaolei li
2017-05-31 3:37 ` [PATCH v4 4/4] mtd: nand: mediatek: add support for MT2712 NAND FLASH Controller Xiaolei Li
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=1496820297.28992.1.camel@mhfsdcap03 \
--to=xiaolei.li@mediatek.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=rogercc.lin@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=yt.shen@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