linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jeff LaBundy <jeff@labundy.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Dario Binacchi <dario.binacchi@amarulasolutions.com>,
	Oliver Graute <oliver.graute@kococonnector.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: edt-ft5x06 - always do msleep(300) during initialization
Date: Sun, 4 Dec 2022 16:43:21 +0000	[thread overview]
Message-ID: <Y4zOKRhE1SY6NeD7@sirena.org.uk> (raw)
In-Reply-To: <Y4pCtm4J3HWhYl8/@nixie71>

[-- Attachment #1: Type: text/plain, Size: 456 bytes --]

On Fri, Dec 02, 2022 at 12:23:50PM -0600, Jeff LaBundy wrote:

> I think the right solution is to introduce a variant of regulator_enable()
> which does not return until a delay passes, where that delay is specified
> in the regulator's child node. Unless something like this exists?

regulator_enable() does not return until the regulator is ready,
if it returns earlier that is a bug in the driver for the
regulator or how it is configured on the board.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2022-12-04 16:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 10:57 [PATCH] Input: edt-ft5x06 - always do msleep(300) during initialization Rasmus Villemoes
2022-12-02 18:23 ` Jeff LaBundy
2022-12-02 20:34   ` Dmitry Torokhov
2022-12-04 16:43   ` Mark Brown [this message]
2022-12-05  8:59   ` Rasmus Villemoes
2022-12-06  3:00     ` Jeff LaBundy
2023-01-03 10:54       ` Rasmus Villemoes

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=Y4zOKRhE1SY6NeD7@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jeff@labundy.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=oliver.graute@kococonnector.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).