From: Huang Shijie <shijie8@gmail.com>
To: Stefan Roese <sr@denx.de>
Cc: devicetree@vger.kernel.org,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: gpmi: Remove "We support only one NAND chip" from bindings doc
Date: Sat, 29 Nov 2014 10:40:50 +0800 [thread overview]
Message-ID: <20141129024047.GA5056@localhost.localdomain> (raw)
In-Reply-To: <54781DD5.5030801@denx.de>
On Fri, Nov 28, 2014 at 08:01:41AM +0100, Stefan Roese wrote:
> On 28.11.2014 02:48, Huang Shijie wrote:
> >On Thu, Nov 27, 2014 at 03:18:49PM +0100, Stefan Roese wrote:
> >>This sentence "We support only one NAND chip now" is not true any more.
> >>Multiple chips are supported. So lets remove this sentence to not
> >
> >The gpmi can only supports one chip. Of course, there are maybe two dies
> >in this single chip.
>
> Now I'm a bit confused. The i.MX6 supports 4 chips select signals. And isn't
> "two dies in this single chip" not practically the same as connecting 2 (or
> more) chips (same device) to multiple chip selects of the SoC? Where is the
> difference here?
The "one chip" here is means the "one package" (TSOP or BGA ....).
(In logic, "two dies in this single chip" is same as connecting 2 chips
to the gpmi.)
thanks
Huang Shijie
WARNING: multiple messages have this Message-ID (diff)
From: Huang Shijie <shijie8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>
Cc: linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Brian Norris
<computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] mtd: gpmi: Remove "We support only one NAND chip" from bindings doc
Date: Sat, 29 Nov 2014 10:40:50 +0800 [thread overview]
Message-ID: <20141129024047.GA5056@localhost.localdomain> (raw)
In-Reply-To: <54781DD5.5030801-ynQEQJNshbs@public.gmane.org>
On Fri, Nov 28, 2014 at 08:01:41AM +0100, Stefan Roese wrote:
> On 28.11.2014 02:48, Huang Shijie wrote:
> >On Thu, Nov 27, 2014 at 03:18:49PM +0100, Stefan Roese wrote:
> >>This sentence "We support only one NAND chip now" is not true any more.
> >>Multiple chips are supported. So lets remove this sentence to not
> >
> >The gpmi can only supports one chip. Of course, there are maybe two dies
> >in this single chip.
>
> Now I'm a bit confused. The i.MX6 supports 4 chips select signals. And isn't
> "two dies in this single chip" not practically the same as connecting 2 (or
> more) chips (same device) to multiple chip selects of the SoC? Where is the
> difference here?
The "one chip" here is means the "one package" (TSOP or BGA ....).
(In logic, "two dies in this single chip" is same as connecting 2 chips
to the gpmi.)
thanks
Huang Shijie
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-29 2:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 14:18 [PATCH] mtd: gpmi: Remove "We support only one NAND chip" from bindings doc Stefan Roese
2014-11-27 14:18 ` Stefan Roese
2014-11-28 1:48 ` Huang Shijie
2014-11-28 1:48 ` Huang Shijie
2014-11-28 7:01 ` Stefan Roese
2014-11-28 7:01 ` Stefan Roese
2014-11-29 2:40 ` Huang Shijie [this message]
2014-11-29 2:40 ` Huang Shijie
2014-11-30 6:53 ` Brian Norris
2014-11-30 6:53 ` Brian Norris
2014-11-30 15:42 ` Huang Shijie
2014-11-30 15:42 ` Huang Shijie
2014-12-01 9:58 ` Stefan Roese
2014-12-01 9:58 ` Stefan Roese
2014-12-02 0:38 ` Huang Shijie
2014-12-02 0:38 ` Huang Shijie
2014-12-02 7:28 ` Stefan Roese
2014-12-02 7:28 ` Stefan Roese
2014-12-03 0:35 ` Huang Shijie
2014-12-03 0:35 ` Huang Shijie
2014-12-17 1:17 ` Brian Norris
2014-12-17 1:17 ` Brian Norris
2014-12-18 2:45 ` Brian Norris
2014-12-18 2:45 ` Brian Norris
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=20141129024047.GA5056@localhost.localdomain \
--to=shijie8@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sr@denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.