From: hs@denx.de (Heiko Schocher)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm, davinci: configure davinci aemif chipselects through OF
Date: Thu, 08 Dec 2011 10:06:47 +0100 [thread overview]
Message-ID: <4EE07E27.8090602@denx.de> (raw)
In-Reply-To: <DF0F476B391FA8409C78302C7BA518B6040A03@DBDE01.ent.ti.com>
Hello Nori,
Nori, Sekhar wrote:
> On Thu, Dec 08, 2011 at 13:17:05, Heiko Schocher wrote:
>
>>>> diff --git a/Documentation/devicetree/bindings/arm/davinci/aemif.txt b/Documentation/devicetree/bindings/arm/davinci/aemif.txt
>>>> new file mode 100644
>>>> index 0000000..c9ed551
>>>> --- /dev/null
>>>> +++ b/Documentation/devicetree/bindings/arm/davinci/aemif.txt
>>>> @@ -0,0 +1,85 @@
>>>> +* Texas Instruments Davinci AEMIF
>>>> +
>>>> +This file provides information, what the device node for the
>>>> +davinci aemifa interface contain.
>>> ^^^^^^
>>> aemif
>> fixed, thanks.
>>
>>>> +
>>>> +Required properties:
>>>> +- compatible: "ti,davinci-emifa";
>> Shouldn't this also be "ti,davinci-aemif" ?
>
> Yes, makes sense.
Ok, change this.
>> [...]
>>>> diff --git a/arch/arm/mach-davinci/aemif.c b/arch/arm/mach-davinci/aemif.c
>>>> index 1ce70a9..12c559f 100644
>>>> --- a/arch/arm/mach-davinci/aemif.c
>>>> +++ b/arch/arm/mach-davinci/aemif.c
>>>> @@ -13,12 +13,14 @@
>>>> #include <linux/err.h>
>>>> #include <linux/clk.h>
>>>> #include <linux/module.h>
>>>> +#include <linux/of.h>
>>>> +#include <linux/of_address.h>
>>>> #include <linux/time.h>
>>>>
>>>> #include <mach/aemif.h>
>>>>
>>>> /* Timing value configuration */
>>>> -
>>>> +#define ASIZE(x) (x)
>>>> #define TA(x) ((x) << 2)
>>>> #define RHOLD(x) ((x) << 4)
>>>> #define RSTROBE(x) ((x) << 7)
>>>> @@ -26,7 +28,10 @@
>>>> #define WHOLD(x) ((x) << 17)
>>>> #define WSTROBE(x) ((x) << 20)
>>>> #define WSETUP(x) ((x) << 26)
>>>> +#define EW(x) ((x) << 30)
>>>> +#define SS(x) ((x) << 31)
>>> You are adding support for additional configuration
>>> parameters which should be done in a separate patch.
>> Hmm.. they are only used in the OF case ... is this split
>> really needed?
>
> But they should also be useful in the non-OF case, no?
> Why restrict their usage to the OF case?
I thought there is no need, because nobody needed this yet ...
Ok, I change this too, so I have to fix this files:
$ grep -lr davinci_aemif_timing .
./arch/arm/mach-davinci/board-dm644x-evm.c
./arch/arm/mach-davinci/board-dm646x-evm.c
./arch/arm/mach-davinci/board-da850-evm.c
./arch/arm/mach-davinci/include/mach/aemif.h
./arch/arm/mach-davinci/include/mach/nand.h
./arch/arm/mach-davinci/board-da830-evm.c
./drivers/mtd/nand/davinci_nand.c
I do not know the values for this boards for the new parameters.
How to proceed? Do you know this values? Or is it Ok, if I add in
arch/arm/mach-davinci/include/mach/aemif.h
a "#define AEMIF_VALUE_NOT USED 0xff" and if the new value is set to
this I don't change this setting in the register?
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2011-12-08 9:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 9:41 [PATCH] arm,davinci: configure davinci aemif chipselects through OF Heiko Schocher
2011-12-04 12:25 ` [PATCH] arm, davinci: " Sergei Shtylyov
2011-12-05 10:50 ` Heiko Schocher
2011-12-04 12:33 ` Sergei Shtylyov
2011-12-05 11:49 ` Heiko Schocher
2011-12-07 10:44 ` [PATCH] arm,davinci: " Nori, Sekhar
2011-12-08 7:47 ` [PATCH] arm, davinci: " Heiko Schocher
2011-12-08 8:19 ` [PATCH] arm,davinci: " Nori, Sekhar
2011-12-08 9:06 ` Heiko Schocher [this message]
2011-12-08 10:29 ` Nori, Sekhar
2011-12-08 15:48 ` [PATCH] arm, davinci: " Arnd Bergmann
2011-12-13 18:34 ` [PATCH] arm,davinci: " Nori, Sekhar
2011-12-14 14:35 ` [PATCH] arm, davinci: " Ben Gardiner
2011-12-15 17:10 ` [PATCH] arm,davinci: " Nori, Sekhar
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=4EE07E27.8090602@denx.de \
--to=hs@denx.de \
--cc=linux-arm-kernel@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).