From: Richard Weinberger <richard@sigma-star.at>
To: Boris Brezillon <boris.brezillon@bootlin.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-mtd <linux-mtd@lists.infradead.org>
Cc: Philipp Rosenberger <p.rosenberger@linutronix.de>,
Benedikt Spranger <b.spranger@linutronix.de>
Subject: Re: DENALI: can't detect NAND chip
Date: Mon, 04 Jun 2018 22:41:40 +0200 [thread overview]
Message-ID: <2325115.CDikpRts66@blindfold> (raw)
In-Reply-To: <20180604223453.0e233668@bbrezillon>
Am Montag, 4. Juni 2018, 22:34:53 CEST schrieb Boris Brezillon:
> > I got access to that board and did initial debugging of the problem.
> >
> > The problem seems to be that after your rework the NAND timings get
> > derived from the NAND clock.
> > When I make denali_setup_data_interface() a NOP, the NAND is being
> > detected and works.
> >
> > Can it be that the function does not calculate the timings correctly
> > in all cases?
> > Please see the following debug output for good and bad case.
> >
> > bad case:
> > [ 0.946757] XXX: denali clk rate: 0x2faf080
> > [ 0.950932] XXX: denali clk phase: 0x0
> > [ 0.954671] XXX: denali clk accuracy: 0x0
> > [ 0.958920] denali-nand-dt ff900000.nand: clk_x_rate: 0x2faf080
> > [ 0.964846] denali-nand-dt ff900000.nand: Dump timing register values:
> > [ 0.964846] acc_clks: 2, re_2_we: 10, re_2_re: 10
> > [ 0.964846] we_2_re: 25, addr_2_data: 20, rdwr_en_lo_cnt: 4
> > [ 0.964846] rdwr_en_hi_cnt: 2, cs_setup_cnt: 3
> >
> > good case:
> > [ 0.961061] XXX: denali clk rate: 0x2faf080
> > [ 0.965231] XXX: denali clk phase: 0x0
> > [ 0.968967] XXX: denali clk accuracy: 0x0
> > [ 0.973031] denali-nand-dt ff900000.nand: Dump timing register values:
> > [ 0.973031] acc_clks: 4, re_2_we: 20, re_2_re: 20
> > [ 0.973031] we_2_re: 12, addr_2_data: 14, rdwr_en_lo_cnt: 2
> > [ 0.973031] rdwr_en_hi_cnt: 2, cs_setup_cnt: 2
> >
> > Does this ring a bell?
> >
>
> Could it be that clk_get_rate() returns an invalid value? Looks like
> all good timings are almost equal to bad timings multiplied by 2, so
> maybe the ->recalc_rate() method of clk driver returns freq / 2 instead
> of freq.
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. :)
Thanks,
//richard
--
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y
next prev parent reply other threads:[~2018-06-04 20:41 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 [this message]
2018-06-04 20:51 ` Boris Brezillon
2018-06-04 20:57 ` Richard Weinberger
2018-06-04 22:01 ` Richard Weinberger
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=2325115.CDikpRts66@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox