[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6ED8E3B22081A4459DAC7699F3695FB7014B251D0A@SW-EX-MBX02.diasemi.com>
Date: Mon, 20 Jul 2015 13:05:43 +0000
From: "Opensource [Steve Twiss]" <stwiss.opensource@...semi.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
CC: DEVICETREE <devicetree@...r.kernel.org>,
LINUXINPUT <linux-input@...r.kernel.org>,
LINUXKERNEL <linux-kernel@...r.kernel.org>,
RTCLINUX <rtc-linux@...glegroups.com>,
David Dajun Chen <david.chen@...semi.com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
"Kumar Gala" <galak@...eaurora.org>,
Lee Jones <lee.jones@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Pawel Moll <pawel.moll@....com>,
Rob Herring <robh+dt@...nel.org>,
Samuel Ortiz <sameo@...ux.intel.com>,
"Support Opensource" <Support.Opensource@...semi.com>
Subject: RE: [PATCH RFC V1 2/3] onkey: da9063: Add DA9062 OnKey capability
to DA9063 OnKey driver
On 17 July 2015 23:51, Dmitry Torokhov wrote:
> Hi Steve,
> On Tue, Jul 14, 2015 at 02:07:50PM +0100, S Twiss wrote:
> > From: S Twiss <stwiss.opensource@...semi.com>
> > Add DA9062 OnKey support into the existing DA9063 OnKey driver component by
> > using generic access tables for common register and bit mask definitions.
> >
> > The following change will add generic register and bit mask support to the
> > DA9063 OnKey.
> >
> > The following alterations have been made to the DA9063 OnKey:
> >
> > - Addition of a da9063_compatible_onkey_regmap structure to hold all
> > generic registers and bitmasks for this type of OnKey component.
> > - Addition of an struct of_device_id table for DA9063 and DA9062
> > defaults
> > - Refactoring functions to use struct da9063_compatible_onkey accesses
> > to generic registers/masks instead of using defines from registers.h
> > - Re-work of da9063_onkey_probe() to use of_match_node() and
> > dev_get_regmap() to provide initialisation of generic registers and
> > masks and access to regmap
> >
> > Signed-off-by: Steve Twiss <stwiss.opensource@...semi.com>
>
> Looks generally good, just a few comments.
>
Hi Dmitry,
Thanks for taking the time to review this.
[...]
> > diff --git a/drivers/input/misc/Kconfig b/drivers/input/misc/Kconfig
> > index d4f0a81..42860f9 100644
> > --- a/drivers/input/misc/Kconfig
> > +++ b/drivers/input/misc/Kconfig
> > @@ -612,10 +612,10 @@ config INPUT_DA9055_ONKEY
> >
> > config INPUT_DA9063_ONKEY
> > tristate "Dialog DA9063 OnKey"
>
> "Dialog DA9062/63 OnKey" maybe?
Yep.
I can do that.
[...]
> >
> > -struct da9063_onkey {
> > - struct da9063 *hw;
> > +struct da9063_compatible_onkey_regmap {
>
> Maybe call it da906x_chip_config?
I will do this.
> > + /* REGS */
> > + int onkey_status;
> > + int onkey_pwr_signalling;
> > + int onkey_fault_log;
> > + int onkey_shutdown;
> > + /* MASKS */
> > + int onkey_nonkey_mask;
> > + int onkey_nonkey_lock_mask;
> > + int onkey_key_reset_mask;
> > + int onkey_shutdown_mask;
> > + /* NAMES */
> > + char *name;
>
> const char *?
>
Sure -- I'll change that.
> > +};
> > +
> > +struct da9063_compatible_onkey {
>
> If you did not rename the structure your diff would be smaller.
Yep. I can rename this back to what it was previously.
[...]
I'll submit a PATCH V2 with those changes.
Regards,
Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists