devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Gerhold <stephan@gerhold.net>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org,
	Simon Budig <simon.budig@kernelconcepts.de>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Ondrej Jirman <megous@megous.com>
Subject: Re: [PATCH 2/2] Input: edt-ft5x06 - add support for iovcc-supply
Date: Mon, 11 Jan 2021 11:10:01 +0100	[thread overview]
Message-ID: <X/wj+bxe/IlznCj6@gerhold.net> (raw)
In-Reply-To: <20210111094538.yg3otwgesgyemktp@pengutronix.de>

On Mon, Jan 11, 2021 at 10:45:38AM +0100, Marco Felsch wrote:
> On 21-01-11 10:26, Stephan Gerhold wrote:
> > On Mon, Jan 11, 2021 at 09:36:12AM +0100, Marco Felsch wrote:
> > > On 21-01-08 20:23, Stephan Gerhold wrote:
> > > > diff --git a/drivers/input/touchscreen/edt-ft5x06.c b/drivers/input/touchscreen/edt-ft5x06.c
> > > > index 2eefbc2485bc..bf2e208112fe 100644
> > > > --- a/drivers/input/touchscreen/edt-ft5x06.c
> > > > +++ b/drivers/input/touchscreen/edt-ft5x06.c
> > > > @@ -103,7 +103,7 @@ struct edt_ft5x06_ts_data {
> > > >  	struct touchscreen_properties prop;
> > > >  	u16 num_x;
> > > >  	u16 num_y;
> > > > -	struct regulator *vcc;
> > > > +	struct regulator_bulk_data regulators[2];
> > > 
> > > Is there an enabling order we must follow?
> > > 
> > 
> > I don't know, sadly. The datasheets I was able to find do not mention
> > anything about this; the power-on sequence only includes the VDD line.
> 
> I've goolged a bit :)
> 
> Check this: https://focuslcds.com/content/FT5X26.pdf, page 12 of 32
> 

Thanks! I looked at several datasheets, that's probably one of the few I
did not look at. :(

> There it is mentioned that we need to enable it first and add a 10us
> delay till we can enable the vdd line. So unfortunately the bulk_api
> can't be used as it is today. Another solution could be to extended the
> bulk api to respect on/off delays.
> 

I think for two regulators like here it's still manageable to
get/enable/disable/put them separately, so I will just revert the bulk
API change in v2.

Thanks again!
Stephan

  reply	other threads:[~2021-01-11 10:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 19:23 [PATCH 1/2] dt-bindings: input: touchscreen: edt-ft5x06: add iovcc-supply Stephan Gerhold
2021-01-08 19:23 ` [PATCH 2/2] Input: edt-ft5x06 - add support for iovcc-supply Stephan Gerhold
2021-01-11  8:36   ` Marco Felsch
2021-01-11  9:26     ` Stephan Gerhold
2021-01-11  9:45       ` Marco Felsch
2021-01-11 10:10         ` Stephan Gerhold [this message]
2021-01-11 15:46           ` Stephan Gerhold
2021-01-11 10:22       ` Andy Shevchenko
2021-01-11 10:43         ` Stephan Gerhold
2021-01-13 15:25 ` [PATCH 1/2] dt-bindings: input: touchscreen: edt-ft5x06: add iovcc-supply Rob Herring

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=X/wj+bxe/IlznCj6@gerhold.net \
    --to=stephan@gerhold.net \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=megous@megous.com \
    --cc=robh+dt@kernel.org \
    --cc=simon.budig@kernelconcepts.de \
    /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).