From: "Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
alexandre.belloni@bootlin.com, nick@shmanahar.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/3] Input: atmel_mxt_ts: Add support for optional regulators
Date: Fri, 14 Dec 2018 16:11:49 +0100 [thread overview]
Message-ID: <2132818.BxtBPRaDeS@acerlaptop> (raw)
In-Reply-To: <20181209042612.GD211094@dtor-ws>
Dnia niedziela, 9 grudnia 2018 05:26:12 CET Dmitry Torokhov pisze:
> On Fri, Dec 07, 2018 at 03:28:55PM +0100, Paweł Chmiel wrote:
> > This patch adds optional regulators, which can be used to power
> > up touchscreen. After enabling regulators, we need to wait 150msec.
> > This value is taken from official driver.
> >
> > It was tested on Samsung Galaxy i9000 (based on Samsung S5PV210 SOC).
> >
> > Signed-off-by: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com>
> > ---
> > Changes from v3:
> > - Fix checkpatch issues
> > - Drop sentence punctuation from subject of one of patches
> >
> > Changes from v2:
> > - Move code enabling regulators into separate method,
> > to make code more readable.
> >
> > Changes from v1:
> > - Enable regulators only if reset_gpio is present.
> > - Switch from devm_regulator_get_optional to devm_regulator_get
> > ---
> > drivers/input/touchscreen/atmel_mxt_ts.c | 65 +++++++++++++++++++++---
> > 1 file changed, 59 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c b/drivers/input/touchscreen/atmel_mxt_ts.c
> > index d3aacd534e9c..1dc8ad0da5af 100644
> > --- a/drivers/input/touchscreen/atmel_mxt_ts.c
> > +++ b/drivers/input/touchscreen/atmel_mxt_ts.c
> > @@ -27,6 +27,7 @@
> > #include <linux/interrupt.h>
> > #include <linux/of.h>
> > #include <linux/property.h>
> > +#include <linux/regulator/consumer.h>
> > #include <linux/slab.h>
> > #include <linux/gpio/consumer.h>
> > #include <asm/unaligned.h>
> > @@ -194,10 +195,10 @@ enum t100_type {
> >
> > /* Delay times */
> > #define MXT_BACKUP_TIME 50 /* msec */
> > -#define MXT_RESET_GPIO_TIME 20 /* msec */
> > #define MXT_RESET_INVALID_CHG 100 /* msec */
> > #define MXT_RESET_TIME 200 /* msec */
> > #define MXT_RESET_TIMEOUT 3000 /* msec */
> > +#define MXT_REGULATOR_DELAY 150 /* msec */
> > #define MXT_CRC_TIMEOUT 1000 /* msec */
> > #define MXT_FW_RESET_TIME 3000 /* msec */
> > #define MXT_FW_CHG_TIMEOUT 300 /* msec */
> > @@ -323,6 +324,8 @@ struct mxt_data {
> > struct t7_config t7_cfg;
> > struct mxt_dbg dbg;
> > struct gpio_desc *reset_gpio;
> > + struct regulator *vdd_reg;
> > + struct regulator *avdd_reg;
> >
> > /* Cached parameters from object table */
> > u16 T5_address;
> > @@ -3038,6 +3041,38 @@ static const struct dmi_system_id chromebook_T9_suspend_dmi[] = {
> > { }
> > };
> >
> > +static int mxt_regulator_enable(struct mxt_data *data)
> > +{
> > + int error;
> > +
> > + if (data->reset_gpio) {
> > + error = regulator_enable(data->vdd_reg);
> > + if (error) {
> > + dev_err(&data->client->dev,
> > + "Failed to enable vdd regulator: %d\n", error);
> > + return error;
> > + }
> > +
> > + error = regulator_enable(data->avdd_reg);
> > + if (error) {
> > + dev_err(&data->client->dev,
> > + "Failed to enable avdd regulator: %d\n", error);
>
> This leaves vdd regulator enabled.
Will be fixed in v5 version (will be today)
Thanks for review.
>
> Thanks.
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-14 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 14:28 [PATCH v4 0/3] Input: atmel_mxt_ts: Add support for optional regulators Paweł Chmiel
2018-12-07 14:28 ` [PATCH v4 1/3] " Paweł Chmiel
2018-12-09 4:26 ` Dmitry Torokhov
2018-12-14 15:11 ` Paweł Chmiel [this message]
2018-12-07 14:28 ` [PATCH v4 2/3] Input: atmel_mxt_ts: Wait for device be ready for communication Paweł Chmiel
2018-12-07 14:28 ` [PATCH v4 3/3] Input: atmel_mxt_ts: Document optional voltage regulators Paweł Chmiel
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=2132818.BxtBPRaDeS@acerlaptop \
--to=pawel.mikolaj.chmiel@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nick@shmanahar.org \
--cc=robh+dt@kernel.org \
/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).