From: Yingjoe Chen <yingjoe.chen@mediatek.com> To: Chuanhong Guo <gch981213@gmail.com> Cc: Vignesh Raghavendra <vigneshr@ti.com>, Tudor Ambarus <tudor.ambarus@microchip.com>, Richard Weinberger <richard@nod.at>, linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org, Miquel Raynal <miquel.raynal@bootlin.com>, Matthias Brugger <matthias.bgg@gmail.com>, linux-mtd@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2] mtd: mtk-quadspi: add support for DMA reading Date: Mon, 10 Feb 2020 16:30:55 +0800 Message-ID: <1581323455.2213.6.camel@mtksdaap41> (raw) In-Reply-To: <20200208084022.193231-1-gch981213@gmail.com> On Sat, 2020-02-08 at 16:40 +0800, Chuanhong Guo wrote: > PIO reading mode on this controller is pretty inefficient > (one cmd+addr+dummy sequence reads only one byte) > This patch adds support for reading using DMA mode which increases > reading speed from 1MB/s to 4MB/s > > DMA busy checking is implemented with readl_poll_timeout because > I don't have access to IRQ-related docs. The speed increment comes > from those saved cmd+addr+dummy clocks. Hi Chuanhong, Thanks for your patch, I'm checking with Guochun to see if we could release IRQ related information to you. > This controller requires that DMA source/destination address and > reading length should be 16-byte aligned. We use a bounce buffer if > one of them is not aligned, read more than what we need, and copy > data from corresponding buffer offset. I've checked with our HW guys. The limitation is on DRAM only. So for read we should check buffer and length to make sure it is aligned, but don't need to check from. Joe.C _______________________________________________ Linux-mediatek mailing list Linux-mediatek@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply index Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-08 8:40 Chuanhong Guo 2020-02-10 8:30 ` Yingjoe Chen [this message] 2020-02-11 6:55 ` Chuanhong Guo 2020-02-15 7:06 ` Chuanhong Guo
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=1581323455.2213.6.camel@mtksdaap41 \ --to=yingjoe.chen@mediatek.com \ --cc=gch981213@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=linux-mtd@lists.infradead.org \ --cc=matthias.bgg@gmail.com \ --cc=miquel.raynal@bootlin.com \ --cc=richard@nod.at \ --cc=tudor.ambarus@microchip.com \ --cc=vigneshr@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
Linux-mediatek Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-mediatek/0 linux-mediatek/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-mediatek linux-mediatek/ https://lore.kernel.org/linux-mediatek \ linux-mediatek@lists.infradead.org public-inbox-index linux-mediatek Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.infradead.lists.linux-mediatek AGPL code for this site: git clone https://public-inbox.org/public-inbox.git