From: Scott Wood <scottwood@freescale.com>
To: Priyanka Jain <Priyanka.Jain@freescale.com>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-mtd@lists.infradead.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH] devicetree/bindings: Add binding for micron n25q512a memory
Date: Thu, 3 Jul 2014 17:10:00 -0500 [thread overview]
Message-ID: <1404425400.21434.89.camel@snotra.buserror.net> (raw)
In-Reply-To: <1404382376-3115-1-git-send-email-Priyanka.Jain@freescale.com>
On Thu, 2014-07-03 at 15:42 +0530, Priyanka Jain wrote:
> -Micron n25q512a memory is supported by m25p80 driver.
> Add compatible field required to support n25q512a in m25p80.txt
> -Add micron to the vendor-prefixes.txt file
>
> Signed-off-by: Priyanka Jain <Priyanka.Jain@freescale.com>
> ---
> Documentation/devicetree/bindings/mtd/m25p80.txt | 1 +
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> 2 files changed, 2 insertions(+), 0 deletions(-)
Why did you send this to the ppc list but not the spi or mtd lists?
I'm having a hard time following the flow of how these SPI devices get
bound -- is the compatible involved at all? I don't see this string
(with vendor prefix included) in the driver. I do see a table that
contains what looks like device IDs. If the device can report its id,
shouldn't we rely on that rather than device tree compatible?
-Scott
> diff --git a/Documentation/devicetree/bindings/mtd/m25p80.txt b/Documentation/devicetree/bindings/mtd/m25p80.txt
> index 4611aa8..ce02e81 100644
> --- a/Documentation/devicetree/bindings/mtd/m25p80.txt
> +++ b/Documentation/devicetree/bindings/mtd/m25p80.txt
> @@ -7,6 +7,7 @@ Required properties:
> the DT binding is not Linux-only, but in case of Linux, see the
> "spi_nor_ids" table in drivers/mtd/spi-nor/spi-nor.c for the list
> of supported chips.
> + example: "micron,n25q512a"
> - reg : Chip-Select number
> - spi-max-frequency : Maximum frequency of the SPI bus the chip can operate at
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index 4d7f375..a44cfee 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -79,6 +79,7 @@ marvell Marvell Technology Group Ltd.
> maxim Maxim Integrated Products
> micrel Micrel Inc.
> microchip Microchip Technology Inc.
> +micron Micron Technology Inc.
> mosaixtech Mosaix Technologies, Inc.
> moxa Moxa
> mpl MPL AG
next parent reply other threads:[~2014-07-03 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1404382376-3115-1-git-send-email-Priyanka.Jain@freescale.com>
2014-07-03 22:10 ` Scott Wood [this message]
2014-07-04 4:08 ` [PATCH] devicetree/bindings: Add binding for micron n25q512a memory Priyanka Jain
2014-07-07 21:25 ` Scott Wood
2014-07-08 4:41 ` Priyanka Jain
2014-07-09 1:53 ` Scott Wood
2014-07-29 9:24 ` Mark Rutland
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=1404425400.21434.89.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=Priyanka.Jain@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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