From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] arm64: dts: mt8173: Add nor flash node
Date: Fri, 11 Sep 2015 14:56:34 -0700 [thread overview]
Message-ID: <20150911215634.GF11487@google.com> (raw)
In-Reply-To: <1441965076.23394.7.camel@mhfsdcap03>
On Fri, Sep 11, 2015 at 05:51:16PM +0800, bayi.cheng wrote:
> On Tue, 2015-09-08 at 18:46 -0500, Rob Herring wrote:
> > On 09/08/2015 10:18 AM, Ezequiel Garcia wrote:
> > > On 8 September 2015 at 08:53, Jagan Teki <jteki@openedev.com> wrote:
> > >> On 8 September 2015 at 15:19, Bayi Cheng <bayi.cheng@mediatek.com> wrote:
> > >>> Add Mediatek nor flash node
> > >>>
> > >>> Signed-off-by: Bayi Cheng <bayi.cheng@mediatek.com>
> > >>> ---
> > >>> arch/arm64/boot/dts/mediatek/mt8173.dtsi | 10 ++++++++++
> > >>> 1 file changed, 10 insertions(+)
> > >>>
> > >>> diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> > >>> index d18ee42..a14f005 100644
> > >>> --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> > >>> +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> > >>> @@ -365,6 +365,16 @@
> > >>> status = "disabled";
> > >>> };
> > >>>
> > >>> + nor_flash: nor at 1100d000 {
> > >>
> > >> Based on the comments from 1/3 - this notation needs to be change something like
> > >> qspi0: quadspi at 1100d000
> > >>
> > >
> > > Actually, to follow ePAPR recomendations it should be named as flash at 1100d000.
> > > (See ePAPR, 2.2.2 Generic Names Recommendation).
> >
> > The flash device node should, but this is the controller which should be
> > "spi" IMO even if this is not a general purpose controller.
> >
> > Rob
> >
> HI Rob, Thanks for your instruct! I will fix it !
OK, so given there are several cooks in the kitchen, and I just read
these replies after replying independently to the binding doc, I'll try
to summarize the consensus, flavored with my own opinion:
* the node name should not be 'nor'; it should be something more along
the lines of ePAPR. So 'flash' or 'spi'
* the phandle name is less important, and can be more descriptive
* there should be a subnode to represent the flash separately from the
controller
So we might put this together to:
whatever_name_you_like: spi at 1100d000 {
...
flash at 0 {
...
};
};
Brian
next prev parent reply other threads:[~2015-09-11 21:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 9:49 [PATCH 0/3] Mediatek SPI-NOR flash driver Bayi Cheng
2015-09-08 9:49 ` [PATCH 1/3] doc: dt: add documentation for Mediatek spi-nor controller Bayi Cheng
2015-09-08 11:34 ` Jagan Teki
2015-09-15 6:49 ` bayi.cheng
2015-09-09 5:47 ` Sascha Hauer
2015-09-15 6:39 ` bayi.cheng
2015-09-11 21:47 ` Brian Norris
2015-09-11 21:49 ` Brian Norris
2015-09-15 6:53 ` bayi.cheng
2015-09-08 9:49 ` [PATCH 2/3] mtd: mtk-nor: mtk serial flash controller driver Bayi Cheng
2015-09-09 6:37 ` Sascha Hauer
2015-09-09 13:00 ` Lothar Waßmann
2015-09-15 16:37 ` bayi.cheng
2015-09-15 16:23 ` bayi.cheng
2015-09-08 9:49 ` [PATCH 3/3] arm64: dts: mt8173: Add nor flash node Bayi Cheng
2015-09-08 11:53 ` Jagan Teki
2015-09-08 15:18 ` Ezequiel Garcia
2015-09-08 23:46 ` Rob Herring
2015-09-11 9:51 ` bayi.cheng
2015-09-11 21:56 ` Brian Norris [this message]
2015-09-11 9:49 ` bayi.cheng
2015-09-11 9:47 ` bayi.cheng
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=20150911215634.GF11487@google.com \
--to=computersforpeace@gmail.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).