linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: linux-mtd@lists.infradead.org
Subject: Re: atmel nand bindings vs. actual dts files
Date: Thu, 07 Mar 2019 17:25:17 +0100	[thread overview]
Message-ID: <4099561.5sHrvDXGx3@ada> (raw)
In-Reply-To: <1823900.qPX5mxbl1h@ada>

Hello,

Am Mittwoch, 6. März 2019, 15:07:52 CET schrieb Alexander Dahl:
> So instead of "always 0x800000" that node has 0x2 as third entry for the
> 'reg' property. Why is that?

I didn't investigate that further yet, but I'm curious, so if anyone knows?

> Bonus question: if the R/B line is not connected, how is that expressed in
> dts? As far as I understood that is possible, if the driver polls some
> status register instead of that line level, right?

Or just waits until a certain timeout …

For v4.19.25 (this is the currently latest base for PREEMPT RT patches) I 
found this:

https://elixir.bootlin.com/linux/v4.19.25/source/include/linux/mtd/
rawnand.h#L1195

It says: 

 * @dev_ready:		[BOARDSPECIFIC] hardwarespecific function for accessing
 *			device ready/busy line. If set to NULL no access to
 *			ready/busy is available and the ready/busy information
 *			is read from the chip status register.

However I see no way to explicitly set this to NULL via device tree for the 
atmel raw nand driver, or did I miss something? 

I guess that's no recommended hardware setup?

Greets
Alex


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2019-03-07 16:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 14:07 atmel nand bindings vs. actual dts files Alexander Dahl
2019-03-07 16:25 ` Alexander Dahl [this message]
2019-04-29  9:55   ` Miquel Raynal
2019-04-30  9:24     ` Alexander Dahl
2019-04-30  9:32       ` Miquel Raynal
2019-06-04  1:53         ` Alexandre Belloni
2019-06-04  7:43           ` 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=4099561.5sHrvDXGx3@ada \
    --to=ada@thorsis.com \
    --cc=linux-mtd@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).