From: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: DEVICETREE <devicetree@vger.kernel.org>,
LINUXINPUT <linux-input@vger.kernel.org>,
LINUXKERNEL <linux-kernel@vger.kernel.org>,
RTCLINUX <rtc-linux@googlegroups.com>,
David Dajun Chen <david.chen@diasemi.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
Lee Jones <lee.jones@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>, Rob Herring <robh+dt@kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
"Support Opensource" <Support.Opensource@diasemi.com>
Subject: RE: [PATCH RFC V1 2/3] onkey: da9063: Add DA9062 OnKey capability to DA9063 OnKey driver
Date: Mon, 20 Jul 2015 13:05:43 +0000 [thread overview]
Message-ID: <6ED8E3B22081A4459DAC7699F3695FB7014B251D0A@SW-EX-MBX02.diasemi.com> (raw)
In-Reply-To: <20150717225042.GF39282@dtor-ws>
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@diasemi.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@diasemi.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
prev parent reply other threads:[~2015-07-20 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 13:07 [PATCH RFC V1 0/3] da9062: Add DA9062 OnKey support using the existing DA9063 OnKey driver S Twiss
2015-07-14 13:07 ` [PATCH RFC V1 1/3] mfd: da9062: Support for the DA9063 OnKey in the DA9062 core S Twiss
2015-07-14 13:07 ` [PATCH RFC V1 3/3] devicetree: da9062: Add device tree bindings for DA9062 OnKey S Twiss
2015-07-14 13:07 ` [PATCH RFC V1 2/3] onkey: da9063: Add DA9062 OnKey capability to DA9063 OnKey driver S Twiss
2015-07-17 22:50 ` Dmitry Torokhov
2015-07-20 13:05 ` Opensource [Steve Twiss] [this message]
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=6ED8E3B22081A4459DAC7699F3695FB7014B251D0A@SW-EX-MBX02.diasemi.com \
--to=stwiss.opensource@diasemi.com \
--cc=Support.Opensource@diasemi.com \
--cc=david.chen@diasemi.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).