From: Tony Lindgren <tony@atomide.com>
To: Roger Quadros <rogerq@ti.com>
Cc: Franklin S Cooper Jr <fcooper@ti.com>,
bcousson@baylibre.com, robh+dt@kernel.org, linux@armlinux.org.uk,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] ARM: dts: am335x-evm: am437xx: dra7xx: Enable NAND DMA prefetch by default
Date: Thu, 10 Aug 2017 09:57:14 -0700 [thread overview]
Message-ID: <20170810165713.GL8569@atomide.com> (raw)
In-Reply-To: <2fd38d80-16ce-8548-0f8a-38eaf820f87e@ti.com>
* Roger Quadros <rogerq@ti.com> [170808 03:04]:
> On 26/07/17 05:15, Franklin S Cooper Jr wrote:
> > Enable NAND DMA prefetch by default for AM335x, AM437x and DRA7x evms that
> > include NAND.
> >
> > The below commit went into additional details regarding performance numbers
> > seen between the two modes.
> >
> > commit aa7abd312c11 ("mtd: nand: omap2: Support parsing dma channel information from DT")
> >
> > Franklin S Cooper Jr (3):
> > ARM: dts: am335x-evm: Enable NAND dma prefetch by default
> > ARM: dts: am437xx: Enable NAND dma prefetch by default
> > ARM: dts: dra7xx: Enable NAND dma prefetch by default
>
> For all patches,
>
> Acked-by: Roger Quadros <rogerq@ti.com>
Applying all three into omap-for-v4.14/dt thanks.
Tony
prev parent reply other threads:[~2017-08-10 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 2:15 [PATCH 0/3] ARM: dts: am335x-evm: am437xx: dra7xx: Enable NAND DMA prefetch by default Franklin S Cooper Jr
2017-07-26 2:15 ` [PATCH 1/3] ARM: dts: am335x-evm: Enable NAND dma " Franklin S Cooper Jr
2017-07-26 2:15 ` [PATCH 2/3] ARM: dts: am437xx: " Franklin S Cooper Jr
2017-07-26 2:15 ` [PATCH 3/3] ARM: dts: dra7xx: " Franklin S Cooper Jr
2017-08-08 10:02 ` [PATCH 0/3] ARM: dts: am335x-evm: am437xx: dra7xx: Enable NAND DMA " Roger Quadros
2017-08-10 16:57 ` Tony Lindgren [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=20170810165713.GL8569@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=fcooper@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
/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).