mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Łukasz Majewski" <l.majewski@majess.pl>
To: Mark Brown <broonie@kernel.org>
Cc: linux-input@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [Regulator] Request for clarification - GPIO controlled regulator, USB VBUS,
Date: Wed, 4 Oct 2017 13:54:49 +0200	[thread overview]
Message-ID: <abe393e3-66fe-3c00-8b87-2375cc01d6f5@majess.pl> (raw)
In-Reply-To: <20171004112704.beqzaxwsb5tg4nbm@sirena.co.uk>

Hi Mark,

> On Wed, Oct 04, 2017 at 12:45:39PM +0200, Łukasz Majewski wrote:
>>> On Tue, Oct 03, 2017 at 06:58:00PM +0200, Łukasz Majewski wrote:
> 
>>>   Perhaps this is something
>>> that could be implemented generically for USB as it's a hotpluggable bus
> 
>> In this case we use VBUS as a power supply voltage. The problem with
>> regulator API used in this case is that we enable it on boot-up, but then we
>> cannot "symulate hotplug" anymore.
> 
> I don't really understand what you mean there, sorry. 

I do use "regulator-fixed" to control VBUS.

The USB driver used regulator_enable/disable to supply power of VBUS.


What I do want to achieve:

For testing purpose I would like to enable/disable this supply (VBUS) 
and force/restart of re-enumeration.

> The majority of
> regulator usage is to supply power, use as reference voltages or
> similar.
> 


-- 
Best regards.

Łukasz Majewski

  reply	other threads:[~2017-10-04 12:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 16:58 Łukasz Majewski
2017-10-03 19:16 ` Dmitry Torokhov
2017-10-03 20:25   ` Łukasz Majewski
2017-10-04 10:32 ` Mark Brown
2017-10-04 10:45   ` Łukasz Majewski
2017-10-04 11:27     ` Mark Brown
2017-10-04 11:54       ` Łukasz Majewski [this message]
2017-10-04 14:57         ` Mark Brown

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=abe393e3-66fe-3c00-8b87-2375cc01d6f5@majess.pl \
    --to=l.majewski@majess.pl \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®