From: Padma Venkat <padma.kvr@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-spi@vger.kernel.org,
Kukjin Kim <kgene.kim@samsung.com>
Subject: Re: [PATCH] spi: s3c64xx: add support for exynos7 SPI controller
Date: Tue, 25 Nov 2014 08:37:33 +0530 [thread overview]
Message-ID: <CAAgF-Bca7_TGW_rJo5ywLLX6hzDxESd4PAeuwyCf9hE1q3QP6Q@mail.gmail.com> (raw)
In-Reply-To: <CAAgF-BfOUSTNX=ieLihAXVXuwd3NzPHG3FpmhqZwnpQpeveDig@mail.gmail.com>
Hi Mark,
>>> OK. I don't have provision to test on this board. I will try to test
>>> on older boards by disabling manual mode.
>>>
>>
>> I tested on exynos5420 peach-pit by enabling auto mode. I used dd
>> command to read 1MB data from spi flash and I compared the result with
>> manual mode. Both are same.
>
> I also tested this patch with Javier Martinez Canillas patches for
> enabling spidev nodes from
> http://www.spinics.net/lists/linux-samsung-soc/msg39057.html.
>
> I read 4MB flashdata from spi by enabling auto mode and compared the
> result. They look same.
Do want some extra tests need to be done for this patch or is it okey?
>
>>
>>> Thanks
>>> padma
>>>
>>
>
next prev parent reply other threads:[~2014-11-25 3:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 9:51 [PATCH] spi: s3c64xx: add support for exynos7 SPI controller Padmavathi Venna
2014-11-06 10:26 ` Mark Brown
[not found] ` <20141106102636.GT8509-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-11-07 8:31 ` Padma Venkat
2014-11-07 10:13 ` Mark Brown
2014-11-10 4:50 ` Padma Venkat
[not found] ` <CAAgF-Bd=S7-PoA7GZoy87W9Dem3OXVhc1tL-eyWEAHvF0LPTKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-14 11:16 ` Padma Venkat
[not found] ` <CAAgF-BcARoRZv=BPqQWyp6rJQQ=CE0FEUz_2vgQSpeZyLwbkBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-21 7:08 ` Padma Venkat
2014-11-25 3:07 ` Padma Venkat [this message]
[not found] ` <1415267509-16653-1-git-send-email-padma.v-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-11-26 19:01 ` Mark Brown
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=CAAgF-Bca7_TGW_rJo5ywLLX6hzDxESd4PAeuwyCf9hE1q3QP6Q@mail.gmail.com \
--to=padma.kvr@gmail.com \
--cc=broonie@kernel.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@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 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).