Devicetree
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org,
	devicetree-discuss list <devicetree-discuss@ozlabs.org>
Subject: Re: [PATCH v3 3/4] powerpc: NAND: FSL UPM: document new bindings
Date: Thu, 26 Mar 2009 17:22:36 -0600	[thread overview]
Message-ID: <fa686aa40903261622wa2a93f9i98435080c7ab6cea@mail.gmail.com> (raw)
In-Reply-To: <49CBFE52.6090706@grandegger.com>

On Thu, Mar 26, 2009 at 4:14 PM, Wolfgang Grandegger <wg@grandegger.com> wrote:
> Anton Vorontsov wrote:
>> On Thu, Mar 26, 2009 at 11:02:06AM -0600, Grant Likely wrote:
>>> In other words, this device is not register-level compatible with the
>>> fsl,upm-nand device.  Give the node a new compatible value
>>> (tqc,tqm8548-upm-nand) and add another entry to the of_fun_match table
>>> for the new device.  Use the .data element in the match table to
>>> supply an alternate fun_cmd_ctrl() function for this board (instead of
>>> using a property value do decide which fun_cmd_ctrl() behaviour to
>>> use).  New boards that *do* use the same addressing scheme can claim
>>> compatibility with tqc,tqm8548-upm-nand.
>>
>> I don't like this. :-/
>>
>> UPM is an universal thing, so there are thousands of ways we can
>> connect NAND to the UPM. Of which only ~10 would be sane (others are
>> insane, and nobody would do this. If they do, _then_ we'll fall back
>> to <board>-upm-nand scheme for a particular board).
>
> Yep.
>
>> I don't see any problem with fsl,upm-addr-line-cs-offsets. It can
>> describe any scheme in "addr lines are cs" connection, it's a common
>> setup for multi-chip memory, we shouldn't treat it is as something
>> extraordinary.
>
> I fully agree. I'm going to provide a patch on monday.

Well, I still don't think it is the wisest choice.  My position is
that it is better to be conservative and pedantic now because it is
easy to relax the rules from that point.  If it turns out after some
experience with "fsl,upm-addr-line-cs-offset" that the scheme has a
serious flaw, then the impact is contained.  On the other side, if it
is confirmed and useful and correct, it is a trivial change to make it
available to everything that claims compatibility with fsl,upm-nand.

That said, I won't oppose it if you go this route.  However at the
very least, please change the nand node's compatible list to be:

compatible = "tqc,tqm8548-upm-nand", "fsl,upm-nand";

The custom glue logic makes it something unique, so "tqc,..." should
be at the start of the list to describe it as such, even if the driver
only ever uses "fsl,upm-nand".

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2009-03-26 23:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1237975701-23201-1-git-send-email-wg@grandegger.com>
     [not found] ` <1237975701-23201-2-git-send-email-wg@grandegger.com>
     [not found]   ` <fa686aa40903250631w6a0cc8b9p3b2e3c1348e0acee@mail.gmail.com>
     [not found]     ` <fa686aa40903250631w6a0cc8b9p3b2e3c1348e0acee-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-25 13:32       ` [PATCH v3 1/4] NAND: FSL-UPM: add multi chip support Grant Likely
2009-03-25 13:43         ` Wolfgang Grandegger
     [not found]           ` <49CA3503.5040006-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2009-03-25 17:26             ` Grant Likely
     [not found]   ` <1237975701-23201-3-git-send-email-wg@grandegger.com>
     [not found]     ` <1237975701-23201-4-git-send-email-wg@grandegger.com>
2009-03-25 15:11       ` [PATCH v3 3/4] powerpc: NAND: FSL UPM: document new bindings Anton Vorontsov
2009-03-25 17:48       ` Grant Likely
2009-03-25 20:48         ` Wolfgang Grandegger
2009-03-26  5:09           ` Grant Likely
     [not found]             ` <fa686aa40903252209r52a1bc1cn995a7da16bc3527f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-26  7:42               ` Wolfgang Grandegger
     [not found]                 ` <49CB31CB.2010704-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2009-03-26 14:27                   ` Grant Likely
     [not found]                     ` <fa686aa40903260727y3266e394g5e574680fe70bbbf-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-26 15:33                       ` Wolfgang Grandegger
     [not found]                         ` <49CBA062.5050000-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2009-03-26 16:04                           ` Grant Likely
2009-03-26 16:35                             ` Wolfgang Grandegger
2009-03-26 17:02                               ` Grant Likely
2009-03-26 17:33                                 ` Anton Vorontsov
2009-03-26 22:14                                   ` Wolfgang Grandegger
2009-03-26 23:22                                     ` Grant Likely [this message]
     [not found]                                       ` <fa686aa40903261622wa2a93f9i98435080c7ab6cea-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-26 23:32                                         ` Anton Vorontsov
2009-03-27  8:07                                       ` Wolfgang Grandegger

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=fa686aa40903261622wa2a93f9i98435080c7ab6cea@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=wg@grandegger.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