From: Segher Boessenkool <segher@kernel.crashing.org>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] booting-without-of: add more bindings for FSL UPM driver
Date: Tue, 10 Jun 2008 01:47:30 +0200 [thread overview]
Message-ID: <a9f4227722f169bc9c2e712df774b748@kernel.crashing.org> (raw)
In-Reply-To: <484D49FF.4090604@grandegger.com>
>>> + - chip-delay : may specify a delay value in milliseconds.
>>
>> Delay for what? The binding should say. "chip-delay" is a bit
>> too generic name as well, it could be more descriptive perhaps.
>
> The chip-delay property defines an appropriate maximum delay
> time (tR) required for read operations if the R/B pin is not
> connected.
Yeah. So please put that in the binding.
>> Shouldn't this be a property of the NAND device anyway, not the
>> NAND controller?
>
> Strictly speaking, it's a property of the NAND device. Therefore it
> should be inside the node nand@0, I thhink:
>
> + nand@0 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + chip-delay = <25>; // in micro-seconds
Something like that, yes. You wrote milliseconds before; which is it?
And, a better property name, please.
> Where should that be documented?
In the binding for nand devices. If there isn't any yet, it might be
best to include that with the binding for your nand controller (i.e.,
describe the whole sub node there).
Segher
next prev parent reply other threads:[~2008-06-09 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 8:42 [PATCH] booting-without-of: add more bindings for FSL UPM driver Wolfgang Grandegger
2008-06-09 10:30 ` Segher Boessenkool
2008-06-09 15:19 ` Wolfgang Grandegger
2008-06-09 23:47 ` Segher Boessenkool [this message]
2008-06-12 8:10 ` Wolfgang Grandegger
2008-06-26 13: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=a9f4227722f169bc9c2e712df774b748@kernel.crashing.org \
--to=segher@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).