devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jelle van der Waa <jelle@vdwaa.nl>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] input: touchscreen: add driver for Zeitec ZET6223
Date: Thu, 9 Feb 2017 13:38:48 -0800	[thread overview]
Message-ID: <20170209213848.GE8862@dtor-ws> (raw)
In-Reply-To: <20170201224734.GF40720@dtor-ws>

On Wed, Feb 01, 2017 at 02:47:34PM -0800, Dmitry Torokhov wrote:
> On Wed, Feb 01, 2017 at 08:35:55PM +0100, Jelle van der Waa wrote:
> > On 02/01/17 at 11:30am, Dmitry Torokhov wrote:
> > > On Wed, Feb 01, 2017 at 11:23:31AM -0800, Dmitry Torokhov wrote:
> > > > On Wed, Feb 01, 2017 at 11:20:53AM -0800, Dmitry Torokhov wrote:
> > > > > On Wed, Feb 01, 2017 at 08:10:59PM +0100, Jelle van der Waa wrote:
> > > > > > On 01/31/17 at 12:19am, Dmitry Torokhov wrote:
> > > > > > > Hi Jelle,
> > > > > > > 
> > > > > > > On Wed, Jan 18, 2017 at 02:49:46PM -0800, Dmitry Torokhov wrote:
> > > > > > > > On Wed, Jan 18, 2017 at 09:57:14PM +0100, Jelle van der Waa wrote:
> > > > > > > > > > I also have been looking at you previosu submission and had some draft
> > > > > > > > > > changes. I reconciled them in the patch below, if it still works for you
> > > > > > > > > > then I'll fold everything together and apply. Please let me know.
> > > > > > > > > 
> > > > > > > > > I'll find some time to test the patch below, I've one small suggestion
> > > > > > > > > to the patch below.
> > > > > > > 
> > > > > > > It would be very helpful if you let me know if the patch actually works
> > > > > > > on the hardware: the merge window for 4.11 will be opening fairly soon.
> > > > > > 
> > > > > > Sorry, I had a busy week and at first it didn't work since I didn't have
> > > > > > a regulator and I think the code for the regular might be wrong.
> > > > > > 
> > > > > > I think that you want the regulators to be optional, but
> > > > > > devm_regulator_get_optional errors out when no vcc/vio is configured.
> > > > > > Changing it to devm_regulator_get makes the driver work. I guess this is
> > > > > > since devm_regulator_get_optional doesn't allow the creation of a dummy
> > > > > > device while devm_regulator_get does.
> > > > > 
> > > > > Ah, yes, these should have been non-optional. I'll fix it up and apply
> > > > > then.
> > > > 
> > > > Hmm.. but no, we only acess regulators if they are non-NULL in
> > > > zet6223_power_on(). I used devm_regulator_get_optional() to avoid
> > > > needless sleep in zet6223_power_on() when we do not have regulators
> > > > defined. Let me look some more...
> > > 
> > > What is the error you are getting from devm_regulator_get_optional()?
> > > What kind of system is that? Do you have system with full constraints?
> > 
> > The system is an ARM tablet, I don't know what regulator it uses for the
> > touchscreen (since I don't have any schematics).
> > 
> > The error I get is:
> > 
> > [    1.274337] zet6223 1-0076: failed to get 'vio' regulator: -19
> 
> OK, I see what is going on. I CCed you on a mail to Mark Brown regarding
> regulator_get_optional(), depending on his response we'll know the way
> forward.

OK, I changed them to be non-optional: I think we can spare 30 msec on
startup for now, we may revisit later if/when we get new regulator API
to check when regulators were turned off/on last.

I'll queue it for 4.11.

Thanks.

-- 
Dmitry

      reply	other threads:[~2017-02-09 21:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23 16:32 [PATCH 1/2] input: touchscreen: add driver for Zeitec ZET6223 Jelle van der Waa
2016-12-23 16:32 ` [PATCH 2/2] devicetree: add vendor prefix for Zeitec Jelle van der Waa
2017-01-03 15:25   ` Rob Herring
     [not found] ` <20161223163214.7716-1-jelle-oJJ1AqDjjO4@public.gmane.org>
2017-01-03 15:24   ` [PATCH 1/2] input: touchscreen: add driver for Zeitec ZET6223 Rob Herring
2017-01-14 19:14   ` Dmitry Torokhov
2017-01-18 20:57     ` Jelle van der Waa
2017-01-18 22:49       ` Dmitry Torokhov
2017-01-31  8:19         ` Dmitry Torokhov
2017-02-01 19:10           ` Jelle van der Waa
     [not found]             ` <20170201191058.GA8453-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-01 19:20               ` Dmitry Torokhov
2017-02-01 19:23                 ` Dmitry Torokhov
2017-02-01 19:30                   ` Dmitry Torokhov
2017-02-01 19:35                     ` Jelle van der Waa
     [not found]                       ` <20170201193554.GB8453-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-01 22:47                         ` Dmitry Torokhov
2017-02-09 21:38                           ` Dmitry Torokhov [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=20170209213848.GE8862@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jelle@vdwaa.nl \
    --cc=linux-input@vger.kernel.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).