Devicetree
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Kevin Hilman <khilman@baylibre.com>,
	Fabien Parent <fparent@baylibre.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	robh+dt@kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: davinci: da850-evm: fix read access to SPI flash
Date: Wed, 18 Jan 2017 15:28:21 +0530	[thread overview]
Message-ID: <b349792e-0465-acac-5fe9-e9b4ae666ce7@ti.com> (raw)
In-Reply-To: <m237gh2ozw.fsf@baylibre.com>

On Wednesday 18 January 2017 05:55 AM, Kevin Hilman wrote:
> Fabien Parent <fparent@baylibre.com> writes:
> 
>> Read access to the SPI flash are broken on da850-evm, i.e. the data
>> read is not what is actually programmed on the flash.
>> According to the datasheet for the M25P64 part present on the da850-evm,
>> if the SPI frequency is higher than 20MHz then the READ command is not
>> usable anymore and only the FAST_READ command can be used to read data.
>>
>> This commit specifies in the DTS that we should use FAST_READ command
>> instead of the READ command.
>>
>> Signed-off-by: Fabien Parent <fparent@baylibre.com>
> 
> Tested on da850-evm on top of v4.10-rc3.  This gets the DT boot
> functionatliy in line with the legacy (board-file) boot.
> 
> Tested-by: Kevin Hilman <khilman@baylibre.com>

Applied with Kevin's Tested-by and also marked for stable. Sending pull
request for v4.10-rc shortly.

Thanks,
Sekhar

      reply	other threads:[~2017-01-18  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 12:57 [PATCH] ARM: davinci: da850-evm: fix read access to SPI flash Fabien Parent
     [not found] ` <20170117125742.9536-1-fparent-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2017-01-18  0:25   ` Kevin Hilman
2017-01-18  9:58     ` Sekhar Nori [this message]

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=b349792e-0465-acac-5fe9-e9b4ae666ce7@ti.com \
    --to=nsekhar@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fparent@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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