[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75VcELo3f5VYqGbgjgBzOZOj360+EPmRF5Oh3VqBAF8TeHw@mail.gmail.com>
Date: Fri, 10 Jan 2020 09:35:30 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: fengping yu <fengping.yu@...iatek.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Olof Johansson <olof@...om.net>,
Aisheng Dong <aisheng.dong@....com>,
Anson Huang <Anson.Huang@....com>,
Maxime Ripard <mripard@...nel.org>,
Leonard Crestez <leonard.crestez@....com>,
Dinh Nguyen <dinguyen@...nel.org>,
Marcin Juszkiewicz <marcin.juszkiewicz@...aro.org>,
Valentin Schneider <valentin.schneider@....com>,
Arnd Bergmann <arnd@...db.de>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Mark Brown <broonie@...nel.org>,
Thierry Reding <treding@...dia.com>,
YueHaibing <yuehaibing@...wei.com>,
Stefan Agner <stefan@...er.cn>, Jacky Bai <ping.bai@....com>,
Marco Felsch <m.felsch@...gutronix.de>,
linux-input <linux-input@...r.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>,
devicetree <devicetree@...r.kernel.org>,
wsd_upstream@...iatek.com
Subject: Re: [PATCH V2 2/2] drivers: input: keyboard
On Fri, Jan 10, 2020 at 3:34 AM Dmitry Torokhov
<dmitry.torokhov@...il.com> wrote:
> On Wed, Jan 08, 2020 at 02:29:23PM +0800, fengping yu wrote:
> > From: "fengping.yu" <fengping.yu@...iatek.com>
...
> > +static void kpd_get_keymap_state(void __iomem *kp_base, u16 state[])
> > +{
> > + state[0] = readw(kp_base + KP_MEM1);
> > + state[1] = readw(kp_base + KP_MEM2);
> > + state[2] = readw(kp_base + KP_MEM3);
> > + state[3] = readw(kp_base + KP_MEM4);
> > + state[4] = readw(kp_base + KP_MEM5);
>
> Please use memcpy_formio() here.
Actually it's not an equivalent and may have side effects.
I already told somewhere that we lack of
mem*_*io{32,16,8}() implementation.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists