All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jon-hunter@ti.com>
To: Christoph Fritz <chf.fritz@googlemail.com>
Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
	Daniel Mack <daniel@zonque.org>,
	linux-omap@vger.kernel.org
Subject: Re: ARM: dts: omap3: NAND support - how?
Date: Thu, 18 Apr 2013 18:26:41 -0500	[thread overview]
Message-ID: <51708131.2040208@ti.com> (raw)
In-Reply-To: <51708097.6070102@ti.com>


On 04/18/2013 06:24 PM, Jon Hunter wrote:
> 
> On 04/18/2013 05:48 PM, Christoph Fritz wrote:
>> On Thu, 2013-04-18 at 17:28 -0500, Jon Hunter wrote:
>>> On 04/18/2013 03:23 PM, Christoph Fritz wrote:
>>
>>
>>>> OMAP3_EVM # md 0x6E000060 7
>>>> 6e000060: 00001800 00141400 00141400 0f010f01    ................
>>>> 6e000070: 010c1414 1f0f0a80 00000870             ........p...
>>
>>>
>>> I don't see any other errors in the log. So I am wondering if the
>>> chip-select mapping is setup correctly. Can you share a dump of the gpmc
>>> registers from u-boot?
>>
>> I already did, please see the "md 0x6E000060 7" from above. Below is my
>> work-sheet how I configured the values:
> 
> Sorry I missed that.
> 
>> ---
>>
>> To get the values right for dt-GPMC-NAND-Config, here are the GPMC
>> config registers for chip-select 0, they are taken from u-boot
>> by doing "md 0x6E000060 7" on the u-boot shell:
>>
>> 	GPMC_CONFIG1: 0x6e000060: 0x00001800
>> 	GPMC_CONFIG2: 0x6e000064: 0x00141400
>> 	GPMC_CONFIG3: 0x6e000068: 0x00141400
>> 	GPMC_CONFIG4: 0x6e00006c: 0x0F010F01
>> 	GPMC_CONFIG5: 0x6e000070: 0x010C1414
>> 	GPMC_CONFIG6: 0x6e000074: 0x1F0F0A80
>> 	GPMC_CONFIG7: 0x6e000078: 0x00000870


I would advise you dump the gpmc registers at the end of the gpmc probe.
I am sure you will see something completely different to the above based
upon your dt configuration.

Cheers
Jon

  reply	other threads:[~2013-04-18 23:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 19:03 ARM: dts: omap3: NAND support - how? Christoph Fritz
2013-04-18 19:39 ` Jon Hunter
2013-04-18 20:23   ` Christoph Fritz
2013-04-18 22:28     ` Jon Hunter
2013-04-18 22:48       ` Christoph Fritz
2013-04-18 23:24         ` Jon Hunter
2013-04-18 23:26           ` Jon Hunter [this message]
2013-04-19  9:01             ` Christoph Fritz
2013-04-19 12:02               ` Christoph Fritz
2013-04-19 14:00                 ` Jon Hunter
2013-04-19 14:53                   ` Christoph Fritz
2013-04-19 15:36                     ` Jon Hunter
2013-04-19 15:48                       ` Tony Lindgren
2013-04-19 15:56                         ` Jon Hunter
2013-04-19 16:15                           ` Tony Lindgren
2013-04-19 16:29                       ` [PATCH] ARM: OMAP2+: nand: reorganize gpmc timing values Christoph Fritz
2013-04-19 16:29                         ` Christoph Fritz
2013-05-16 15:49                         ` Tony Lindgren
2013-05-16 15:49                           ` Tony Lindgren
2013-04-19 12:57               ` ARM: dts: omap3: NAND support - how? Jon Hunter
2013-04-19 13:06                 ` Christoph Fritz

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=51708131.2040208@ti.com \
    --to=jon-hunter@ti.com \
    --cc=chf.fritz@googlemail.com \
    --cc=daniel@zonque.org \
    --cc=javier.martinez@collabora.co.uk \
    --cc=linux-omap@vger.kernel.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 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.