From: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: "linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org"
<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH V3 0/4] ARM: tegra: Enable SLINK controller driver
Date: Wed, 31 Oct 2012 14:21:40 +0530 [thread overview]
Message-ID: <5090E69C.4080108@nvidia.com> (raw)
In-Reply-To: <509038BA.30600-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On Wednesday 31 October 2012 01:59 AM, Stephen Warren wrote:
> On 10/30/2012 01:05 AM, Laxman Dewangan wrote:
>> This series modify the dts file to add the slink addresses,
>> make AUXDATA in board dt files, enable slink4 for tegra30-cardhu and
>> enable slink controller defconfig.
> This series only instantiates the SPI controller, and not any SPI
> devices. I tried to solve this:
>
>> diff --git a/arch/arm/boot/dts/tegra30-cardhu.dtsi b/arch/arm/boot/dts/tegra30-cardhu.dtsi
>> index 700f0a3..3689853 100644
>> --- a/arch/arm/boot/dts/tegra30-cardhu.dtsi
>> +++ b/arch/arm/boot/dts/tegra30-cardhu.dtsi
>> @@ -278,6 +278,11 @@
>> spi@7000da00 {
>> status = "okay";
>> spi-max-frequency =<25000000>;
>> + flash@0 {
>> + reg =<0>;
>> + compatible = "atmel,at25df321a";
>> + spi-max-frequency =<25000000>;
>> + };
>> };
>>
>> ahub {
> However, this didn't work. Has the driver been tested? I'm seeing the
> exact same problems I saw with the old driver, namely that the SPI flash
> chip can't be identified; I think the ID bytes are read back as 0, and
> hence drivers/mtd/devices/m25p80.c falls back to identifying the device
> as mr25h256. Attempting to hexdump -C /dev/mtd0 gives me 32K of zeros,
> whereas the device is 4M and full of non-zero data according to U-Boot.
>
> Do you know what the problem is here? Can you please update the patch
> series so that the SPI flash is instantiated and works correctly?
I will send the new patch series for taking care of the issue.
In Cardhu, there is 2 different type of flash, Winbond and Atmel.
There is hw rework require in Cardhu A02 to enable the serial flash and
it is already taken care in Cardhu A04. I will forward the hw rework
details to you in internal mail communication.
Also Serial flash is in CS1, not in CS0. So even if you have hw rework,
above change will not work.
I had tested on different way earlier (dynamic allocating master for
serial flash) and also tested on above method.
For this I enable MTD, MTD_CHAR and MTD_M25P80.
Debug prints as:
[ 1.279424] m25p_probe
[ 1.282536] m25p80 spi32766.1: w25q32 (4096 Kbytes)
[ 1.287418] mtd .name = spi32766.1, .size = 0x400000 (4MiB)
.erasesize = 0x00
001000 (4KiB) .numeraseregions = 0
[ 1.298120] m25p_probe() returns 0
next prev parent reply other threads:[~2012-10-31 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 7:05 [PATCH V3 0/4] ARM: tegra: Enable SLINK controller driver Laxman Dewangan
2012-10-30 7:05 ` [PATCH V3 1/4] ARM: tegra: dts: add slink controller dt entry Laxman Dewangan
[not found] ` <1351580726-17350-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-10-30 7:05 ` [PATCH V3 2/4] ARM: tegra: Add OF_DEV_AUXDATA for SLINK driver in board dt Laxman Dewangan
2012-10-30 7:05 ` [PATCH V3 3/4] ARM: tegra: dts: cardhu: enable SLINK4 Laxman Dewangan
2012-10-30 20:29 ` [PATCH V3 0/4] ARM: tegra: Enable SLINK controller driver Stephen Warren
[not found] ` <509038BA.30600-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-10-31 8:51 ` Laxman Dewangan [this message]
2012-10-31 16:06 ` Stephen Warren
2012-10-31 17:33 ` Laxman Dewangan
2012-10-30 7:05 ` [PATCH V3 4/4] ARM: tegra: config: enable spi driver for Tegra SLINK controller Laxman Dewangan
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=5090E69C.4080108@nvidia.com \
--to=ldewangan-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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).