From: Marek Vasut <marex@denx.de>
To: Vignesh R <vigneshr@ti.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
Rob Herring <robh@kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Graham Moore <grmoore@opensource.altera.com>,
Alan Tull <atull@opensource.altera.com>,
David Woodhouse <dwmw2@infradead.org>,
Dinh Nguyen <dinguyen@opensource.altera.com>,
Yves Vandervennet <yvanderv@opensource.altera.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH V8 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver.
Date: Thu, 4 Feb 2016 12:25:11 +0100 [thread overview]
Message-ID: <201602041225.11679.marex@denx.de> (raw)
In-Reply-To: <56B30007.1010305@ti.com>
On Thursday, February 04, 2016 at 08:38:47 AM, Vignesh R wrote:
> On 02/02/2016 02:43 AM, Marek Vasut wrote:
> > On Monday, February 01, 2016 at 10:03:35 PM, Brian Norris wrote:
> >> On Wed, Jan 13, 2016 at 03:39:17AM +0100, Marek Vasut wrote:
> >>> On Wednesday, January 13, 2016 at 03:26:08 AM, Rob Herring wrote:
> >>>> On Mon, Jan 11, 2016 at 05:34:45AM +0100, Marek Vasut wrote:
> [...]
>
> >>> All these SoCs should be capable of tweaking the block to fit their
> >>> needs by just the DT properties. I believe they differ only in the
> >>> FIFO depth and sometimes someone is greedy and uses 4:16 CS
> >>> multiplexer, which is an external passive component, but that's all.
> >>>
> >>> Would we need soc-specific compatible strings if this is the case?
> >>
> >> It's nice when most things can be supported with a small set of DT
> >> properties, as you've done. But IUIC, I think it's usually good practice
> >> to define and use SoC-specific (or maybe SoC family) compatible strings
> >> in the docs and DTS files, in addition to the generic one, in case there
> >> are future quirks that need to be handled. Note that you don't actually
> >> have to use these in the driver yet, but it's good to have a definition.
> >>
> >> So you can, today, have:
> >> foo@xxxx {
> >>
> >> compatible = "ti,baz-12345", "cdns,qspi-nor";
> >> ...
> >>
> >> };
> >>
> >> And we have the option to pick up "ti,baz-12345" in the Linux driver *if
> >> needed.*
>
> The support for TI SoC that has this IP is not in upstream yet. I will
> add TI-specific compatible later. It will be:
>
> foo@xxxx {
> compatible = "ti,k2g-qspi", "cdns,qspi-nor";
> ...
> };
Do you expect any specifics which cannot be handled by the current bindings btw?
In my socfpga case, the compatible strings will be probably:
"altr,socfpga-gen5-qspi"
Dinh, Graham, do you agree with this or should we use something else ?
Thanks!
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-02-04 11:47 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 4:34 [PATCH V8 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver Marek Vasut
2016-01-11 4:34 ` [PATCH V10 2/2] mtd: spi-nor: Add driver for Cadence Quad SPI Flash Controller Marek Vasut
2016-01-11 16:09 ` Dinh Nguyen
2016-01-11 16:32 ` Marek Vasut
2016-01-12 4:41 ` Vignesh R
2016-01-12 13:49 ` Marek Vasut
2016-04-06 16:55 ` R, Vignesh
2016-04-06 19:30 ` Marek Vasut
2016-04-07 4:55 ` Vignesh R
2016-04-13 10:27 ` Marek Vasut
2016-04-13 15:06 ` Marek Vasut
2016-04-14 16:41 ` R, Vignesh
2016-04-14 17:46 ` Marek Vasut
2016-05-13 0:00 ` Trent Piepho
2016-05-13 0:24 ` Marek Vasut
2016-05-13 20:43 ` Trent Piepho
2016-05-25 23:08 ` Marek Vasut
2016-05-25 23:02 ` Marek Vasut
2016-01-11 16:06 ` [PATCH V8 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver Dinh Nguyen
2016-01-11 16:32 ` Marek Vasut
2016-01-11 17:03 ` Dinh Nguyen
2016-01-11 17:27 ` Marek Vasut
2016-01-13 2:26 ` Rob Herring
2016-01-13 2:39 ` Marek Vasut
2016-02-01 21:03 ` Brian Norris
2016-02-01 21:13 ` Marek Vasut
2016-02-04 7:38 ` Vignesh R
2016-02-04 11:25 ` Marek Vasut [this message]
2016-02-04 17:04 ` Dinh Nguyen
2016-02-06 7:42 ` Marek Vasut
2016-02-04 17:30 ` R, Vignesh
2016-02-06 7:42 ` Marek Vasut
2016-02-08 11:19 ` Vignesh R
2016-02-08 15:27 ` Marek Vasut
2016-02-10 16:10 ` Graham Moore
2016-02-10 16:17 ` Marek Vasut
2016-03-10 20:55 ` Graham Moore
2016-03-10 21:10 ` Marek Vasut
2016-03-14 18:17 ` Graham Moore
2016-03-14 22:47 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2016-06-04 0:39 Marek Vasut
2016-06-07 14:00 ` Rob Herring
2016-07-18 17:00 ` Brian Norris
2015-08-21 9:20 Marek Vasut
2015-08-27 17:44 ` vikas
2015-08-27 18:12 ` Marek Vasut
2015-08-27 20:18 ` vikas
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=201602041225.11679.marex@denx.de \
--to=marex@denx.de \
--cc=atull@opensource.altera.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=dwmw2@infradead.org \
--cc=grmoore@opensource.altera.com \
--cc=linux-mtd@lists.infradead.org \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
--cc=yvanderv@opensource.altera.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;
as well as URLs for NNTP newsgroup(s).