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

On Wed, Mar 25, 2009 at 2:48 PM, Wolfgang Grandegger <wg@grandegger.com> wrote:
> Grant Likely wrote:
>> For the chip offset, it's not clear what the meaning is.  First, does
>> the UPM controller support access of multiple chips simultaneously?
>
> The offset drives the corresponding address lines, which are used to
> select the chip. That's how it's done on the TQM8548 board. In
> principle, the chips could also be selected through dedicated GPIO pins.
> Well, I'm not a hardware guy.

Heh.  I mean elaborate in the binding documentation.  :-)

>> If so, then can you elaborate in the description on how board design
>> translates to a chip-offset value.  If it cannot, then it might be
>> better to have multiple tuples in the 'reg' property for each discrete
>> chip.  Multiple reg tuples would also remove the need for the
>> num-chips property.
>
> The node still describes one device mapping all relevant control
> registers. How about using fsl,upm-chip-offsets = <0x200 0x400>. It
> would be more generic and makes num-chips obsolete as well. And the
> property would be reserved for that way of implementing the chip select
> in hardware.

It really sounds like this binding is describing multiple NAND chips
mapped to different base addresses (and looking at the fsm_upm.c
driver appears to confirm it).  So, does this work?  reg = <3 0x200 4
 3 0x400 4>;

It is true that other methods could be used for implementing the chip
select, but that is *not* what the proposed binding describes.  This
proposed binding describes NAND chips selected by address lines
(particular addresses), and in this case I think using reg is the
natural description.

g.

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

  reply	other threads:[~2009-03-26  5:09 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 [this message]
     [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
     [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=fa686aa40903252209r52a1bc1cn995a7da16bc3527f@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