All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@sigma-star.at>
To: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	Philipp Rosenberger <p.rosenberger@linutronix.de>,
	Benedikt Spranger <b.spranger@linutronix.de>
Subject: Re: DENALI: can't detect NAND chip
Date: Tue, 05 Jun 2018 00:01:51 +0200	[thread overview]
Message-ID: <1864836.G720OGCVI0@blindfold> (raw)
In-Reply-To: <38227338.JIUUFn9IOS@blindfold>

Am Montag, 4. Juni 2018, 22:57:32 CEST schrieb Richard Weinberger:
> Am Montag, 4. Juni 2018, 22:51:17 CEST schrieb Boris Brezillon:
> > > According to the datasheet, the NAND clock rate should be 50Mhz, which is what
> > > is returned in both cases.
> > > So this does not really look invalid to me. :)
> > 
> > Did you try to put a scope on the RE or WE pin? The x2 factor looks too
> > perfect to be just a coincidence.
> 
> Not yet, but you are right the x2 factor is really interesting.

The NFC uses two clocks, nand_x_clk and nand_clk.
nand_clk is nand_x_clk / 4.
In the device tree nand_clk is referenced, and therefore used to calculate
the timings. So we might need to use the 200Mhz clock instead of the 50Mhz
for the calculation.

Thanks,
//richard

-- 
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y

  reply	other threads:[~2018-06-04 22:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 14:29 DENALI: can't detect NAND chip Philipp Rosenberger
2018-03-13  8:48 ` Masahiro Yamada
2018-06-04 19:58   ` Richard Weinberger
2018-06-04 20:34     ` Boris Brezillon
2018-06-04 20:41       ` Richard Weinberger
2018-06-04 20:51         ` Boris Brezillon
2018-06-04 20:57           ` Richard Weinberger
2018-06-04 22:01             ` Richard Weinberger [this message]
2018-06-05  1:43               ` Masahiro Yamada
2018-06-05  7:36                 ` Boris Brezillon
2018-06-05  7:54                   ` Richard Weinberger
2018-06-12  9:21                   ` Richard Weinberger
2018-06-12  9:24                     ` Masahiro Yamada
2018-06-12  9:34                       ` Richard Weinberger
2018-06-12  9:29                     ` Boris Brezillon

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=1864836.G720OGCVI0@blindfold \
    --to=richard@sigma-star.at \
    --cc=b.spranger@linutronix.de \
    --cc=boris.brezillon@bootlin.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=p.rosenberger@linutronix.de \
    --cc=yamada.masahiro@socionext.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 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.