[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160401204236.GE3645@localhost>
Date: Fri, 1 Apr 2016 13:42:36 -0700
From: Brian Norris <computersforpeace@...il.com>
To: Cyrille Pitchen <cyrille.pitchen@...el.com>
Cc: Rob Herring <robh+dt@...nel.org>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
Nicolas Ferre <nicolas.ferre@...el.com>,
boris brezillon <boris.brezillon@...e-electrons.com>,
Marek VaĊĦut <marex@...x.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>
Subject: Re: [PATCH v2 2/2] doc: dt: mtd: add a DT property to enable the use
of 4byte-address op codes
On Fri, Mar 25, 2016 at 03:44:34PM +0100, Cyrille Pitchen wrote:
> Hi all,
>
> Since the framework is named spi-nor, what about spi-nor-4byte-opcodes?
> Is it okay for everyone?
>
> It would follow the same pattern as spi-max-frequency which applies to all SPI
> devices.
"spi-nor-" as a prefix seems better, thanks.
I'm still not confident we've settled the discussion on the need for
this property. I really don't like having a mixture of ways to specify
the same thing, so if we can avoid it in any way (e.g., by just being
more specific about device names), then I'd probably prefer that.
Brian
Powered by blists - more mailing lists