[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D0F6F4317@AcuExch.aculab.com>
Date: Thu, 10 Apr 2014 08:46:14 +0000
From: David Laight <David.Laight@...LAB.COM>
To: "'hongbo.zhang@...escale.com'" <hongbo.zhang@...escale.com>,
"vkoul@...radead.org" <vkoul@...radead.org>,
"dan.j.williams@...el.com" <dan.j.williams@...el.com>,
"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>
CC: "scottwood@...escale.com" <scottwood@...escale.com>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"leo.li@...escale.com" <leo.li@...escale.com>
Subject: RE: [PATCH v3 2/8] DMA: Freescale: unify register access methods
From: hongbo.zhang@...escale.com
> Methods of accessing DMA contorller registers are inconsistent, some registers
^^
> are accessed by DMA_IN/OUT directly, while others are accessed by functions
> get/set_* which are wrappers of DMA_IN/OUT, and even for the BCR register, it
> is read by get_bcr but written by DMA_OUT.
> This patch unifies the inconsistent methods, all registers are accessed by
> get/set_* now.
David
Powered by blists - more mailing lists