[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4656BEB6164FC34F8171C6538F1A595B2E981925@SHSMSX101.ccr.corp.intel.com>
Date: Mon, 1 Sep 2014 03:03:05 +0000
From: "Chen, Alvin" <alvin.chen@...el.com>
To: "Shevchenko, Andriy" <andriy.shevchenko@...el.com>,
"atull@...nsource.altera.com" <atull@...nsource.altera.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"Kweh, Hock Leong" <hock.leong.kweh@...el.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"Ong, Boon Leong" <boon.leong.ong@...el.com>,
"gnurou@...il.com" <gnurou@...il.com>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
"Westerberg, Mika" <mika.westerberg@...el.com>,
"dvhart@...ux.intel.com" <dvhart@...ux.intel.com>
Subject: RE: [PATCH 2/3] GPIO: gpio-dwapb: Support Debounce
> >
> > I don't understand the reason for adding dwapb_read and dwapb_write here.
> > The rest of the driver is using readl and writel. I'd rather not see
> > two different methods being used in the same driver for register access.
> > Maybe I'm missing something, but if we need to add dwapb_read/write,
> > then it should be used for all register access.
>
> Alan, it was my proposal. I rather agree that is better to convert all accesses to
> that.
OK, I will convert all readl&writel to dwapb_read&dwapb_write.
Powered by blists - more mailing lists