From: Vignesh R <vigneshr@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] ARM: dts: dra7xx: Update spi-max-frequency for QSPI
Date: Mon, 25 Jul 2016 19:16:12 +0530 [thread overview]
Message-ID: <be3fdd44-e3ad-8fa9-6844-022675a05982@ti.com> (raw)
In-Reply-To: <20160725133827.GG14698@bill-the-cat>
On Monday 25 July 2016 07:08 PM, Tom Rini wrote:
> On Mon, Jul 25, 2016 at 03:45:47PM +0530, Vignesh R wrote:
>
>> According to AM572x DM SPRS953A, QSPI max bus speed is 76.8MHz.
>> Therefore update the spi-max-frequency value of QSPI node for DRA74 and
>> DRA72 evm. This increase flash read speed by ~2MB/s.
>>
>> Signed-off-by: Vignesh R <vigneshr@ti.com>
>
> Reviewed-by: Tom Rini <trini@konsulko.com>
>
> And similar changes are taking place in Linux-land and the DTS will be
> updated there too, right? Thanks!
Yes, I will be updating Kernel DTS too...
--
Regards
Vignesh
next prev parent reply other threads:[~2016-07-25 13:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 10:15 [U-Boot] [PATCH 0/4] dra7xx: QSPI: Increase SPI bus speed Vignesh R
2016-07-25 10:15 ` [U-Boot] [PATCH 1/4] ARM: dra7xx: Change DPLL_PER_HS13 divider value Vignesh R
2016-07-25 13:38 ` Tom Rini
2016-07-29 8:42 ` Mugunthan V N
2016-07-29 18:18 ` Jagan Teki
2016-07-25 10:15 ` [U-Boot] [PATCH 2/4] spi: ti_qspi: dra7xx: Add support to use 76.8MHz clock Vignesh R
2016-07-25 13:38 ` Tom Rini
2016-07-27 6:35 ` Jagan Teki
2016-07-27 12:10 ` Vignesh R
2016-07-28 13:36 ` Jagan Teki
2016-07-29 8:42 ` Mugunthan V N
2016-07-25 10:15 ` [U-Boot] [PATCH 3/4] configs: dra7xx: Update QSPI speed to 76.8MHz Vignesh R
2016-07-25 13:38 ` Tom Rini
2016-07-27 6:36 ` Jagan Teki
2016-07-29 8:44 ` Mugunthan V N
2016-07-25 10:15 ` [U-Boot] [PATCH 4/4] ARM: dts: dra7xx: Update spi-max-frequency for QSPI Vignesh R
2016-07-25 13:38 ` Tom Rini
2016-07-25 13:46 ` Vignesh R [this message]
2016-07-28 13:39 ` Jagan Teki
2016-07-29 8:45 ` Mugunthan V N
2016-07-25 13:38 ` [U-Boot] [PATCH 0/4] dra7xx: QSPI: Increase SPI bus speed Tom Rini
2016-07-26 6:34 ` Vignesh R
2016-07-29 18:23 ` Jagan Teki
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=be3fdd44-e3ad-8fa9-6844-022675a05982@ti.com \
--to=vigneshr@ti.com \
--cc=u-boot@lists.denx.de \
/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