public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
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 v1 1/2] mtd: nand: mediatek: update DT bindings
Date: Thu, 11 May 2017 16:55:52 +0800	[thread overview]
Message-ID: <1494492952.15376.4.camel@mhfsdcap03> (raw)
In-Reply-To: <fdf9d691-347d-83e0-d4e4-734be5fbecd3@gmail.com>

Hi Matthias,

On Thu, 2017-05-11 at 10:08 +0200, Matthias Brugger wrote:
> 
> On 11/05/17 09:25, Xiaolei Li wrote:
> > Add MT2712 NAND Flash Controller dt bindings documentation.
> > 
> > Signed-off-by: Xiaolei Li <xiaolei.li@mediatek.com>
> > ---
> >   Documentation/devicetree/bindings/mtd/mtk-nand.txt | 7 +++++--
> >   1 file changed, 5 insertions(+), 2 deletions(-)
> > 
> > diff --git a/Documentation/devicetree/bindings/mtd/mtk-nand.txt b/Documentation/devicetree/bindings/mtd/mtk-nand.txt
> > index 069c192..6482650 100644
> > --- a/Documentation/devicetree/bindings/mtd/mtk-nand.txt
> > +++ b/Documentation/devicetree/bindings/mtd/mtk-nand.txt
> > @@ -12,7 +12,9 @@ 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 "mediatek,mt{SoC name}-nfc".
> > +				So far, the supported are
> > +				"mediatek,mt2701-nfc", "mediatek,mt2712-nfc".
> 
> Better would be:
> Should be one of "mediatek,mt2701-nfc", "mediatek,mt2712-nfc".

OK.
> 
> >   - reg:				Base physical address and size of NFI.
> >   - interrupts:			Interrupts of NFI.
> >   - clocks:			NFI required clocks.
> > @@ -141,7 +143,8 @@ Example:
> >   ==============
> >   
> >   Required BCH properties:
> > -- compatible:	Should be "mediatek,mtxxxx-ecc".
> > +- compatible:	Should be "mediatek,mt{SoC name}-ecc". So far, the supported
> > +		are "mediatek,mt2701-ecc", "mediatek,mt2712-ecc".
> 
> Same here.
> 
OK.
> >   - reg:		Base physical address and size of ECC.
> >   - interrupts:	Interrupts of ECC.
> >   - clocks:	ECC required clocks.
> > -- 
> > 1.9.1
> > 
> > ************* Email Confidentiality Notice
> >   ********************
> > The information contained in this e-mail message (including any
> > attachments) may be confidential, proprietary, privileged, or otherwise
> > exempt from disclosure under applicable laws. It is intended to be
> > conveyed only to the designated recipient(s). Any use, dissemination,
> > distribution, printing, retaining or copying of this e-mail (including its
> > attachments) by unintended recipient(s) is strictly prohibited and may
> > be unlawful. If you are not an intended recipient of this e-mail, or believe
> >   
> > that you have received this e-mail in error, please notify the sender
> > immediately (by replying to this e-mail), delete any and all copies of
> > this e-mail (including any attachments) from your system, and do not
> > disclose the content of this e-mail to any other person. Thank
> >   you!
> > 
> 
> Please fix your mail setup to not send this footer.
> 
OK. Has updated mail setting, should be OK now.

> Regards,
> Matthias

  reply	other threads:[~2017-05-11  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1494487532-36594-1-git-send-email-xiaolei.li@mediatek.com>
     [not found] ` <1494487532-36594-2-git-send-email-xiaolei.li@mediatek.com>
2017-05-11  8:08   ` [PATCH v1 1/2] mtd: nand: mediatek: update DT bindings Matthias Brugger
2017-05-11  8:55     ` xiaolei li [this message]
     [not found] ` <1494487532-36594-3-git-send-email-xiaolei.li@mediatek.com>
2017-05-11  8:21   ` [PATCH v1 2/2] mtd: nand: mediatek: add support for MT2712 NFC and ECC Matthias Brugger
2017-05-11  9:02     ` 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=1494492952.15376.4.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