linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wadim Egorov <W.Egorov@phytec.de>
To: Mark Brown <broonie@kernel.org>, Nishanth Menon <nm@ti.com>
Cc: jerome Neanne <jneanne@baylibre.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"kristo@kernel.org" <kristo@kernel.org>,
	"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will@kernel.org" <will@kernel.org>,
	"lee@kernel.org" <lee@kernel.org>,
	"tony@atomide.com" <tony@atomide.com>,
	"vigneshr@ti.com" <vigneshr@ti.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"geert+renesas@glider.be" <geert+renesas@glider.be>,
	"dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>,
	"marcel.ziswiler@toradex.com" <marcel.ziswiler@toradex.com>,
	"vkoul@kernel.org" <vkoul@kernel.org>,
	"biju.das.jz@bp.renesas.com" <biju.das.jz@bp.renesas.com>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"jeff@labundy.com" <jeff@labundy.com>, "afd@ti.com" <afd@ti.com>,
	"khilman@baylibre.com" <khilman@baylibre.com>,
	"narmstrong@baylibre.com" <narmstrong@baylibre.com>,
	"msp@baylibre.com" <msp@baylibre.com>,
	"j-keerthy@ti.com" <j-keerthy@ti.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v7 1/6] DONOTMERGE: arm64: dts: ti: Add TI TPS65219 PMIC support for AM642 SK board.
Date: Wed, 28 Dec 2022 10:16:27 +0000	[thread overview]
Message-ID: <c2a0f9fb-3b54-0a3f-2bfa-9575a9ae937f@phytec.de> (raw)
In-Reply-To: <Y5x1oAzezZGqyZSx@sirena.org.uk>

Am 16.12.22 um 14:41 schrieb Mark Brown:
> On Thu, Dec 15, 2022 at 03:41:49PM -0600, Nishanth Menon wrote:
>
>> Yeah - this happens to be SDcard supply (at least in my case).. I'd
>> rather not change the mmc host or core layer to handle a case where
>> LDO happened to be in bypass. it is a regulator driver's problem, IMHO
>> how to provide the stated voltage OR fail to transition the voltage.
> Well, if the regulator is in bypass mode then it is by definition not
> regulating and so it's like programming the voltage while switched off,
> setting the target for when it starts regulating again.  It's a weirder
> use case but it does feel like the consistent thing to do at least.
> The driver shouldn't enter/leave bypass without being explicitly told to
> so since there'll be a performance impact.
>
>> b) If I wanted the LDO to poweroff the bypass bit at start (define the
>>     startup hardware condition), I dont seem to have a description for
>>     that either.
> That's something we could add in constraints, though the actual process
> of implementing it might get messy if there's restrictions like having
> to power off (though from further down the thread I see that might not
> apply to this device).

Just for the record:

My reported problem was actually not the LDO1/bypass situation, but an issue in 
the process of resolving the regulator supplies.

It was resolved by
   commit 0debed5b117d ("regulator: core: Fix resolve supply lookup issue")

Now everything seems to work with my setup with LDO1 supplied by a fixed 
regulator and LDO1 acting in bypass mode on our hardware.

Regards,
Wadim


  reply	other threads:[~2022-12-28 10:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 15:23 [PATCH v7 0/6] Add support for TI TPS65219 PMIC Jerome Neanne
2022-11-04 15:23 ` [PATCH v7 1/6] DONOTMERGE: arm64: dts: ti: Add TI TPS65219 PMIC support for AM642 SK board Jerome Neanne
2022-12-15 15:09   ` Wadim Egorov
2022-12-15 15:51     ` jerome Neanne
2022-12-15 16:09       ` Mark Brown
2022-12-15 17:54         ` Nishanth Menon
2022-12-15 18:22           ` Mark Brown
2022-12-15 21:41             ` Nishanth Menon
2022-12-16  6:21               ` Vignesh Raghavendra
2022-12-16  7:28                 ` jerome Neanne
2022-12-16 13:41               ` Mark Brown
2022-12-28 10:16                 ` Wadim Egorov [this message]
2022-11-04 15:23 ` [PATCH v7 2/6] DONOTMERGE: arm64: dts: ti: Add pinmux and irq mapping for TPS65219 external interrupts Jerome Neanne
2022-11-04 15:23 ` [PATCH v7 3/6] DONOTMERGE: arm64: dts: ti: k3-am642-sk: Enable tps65219 power-button Jerome Neanne
2022-11-04 15:23 ` [PATCH v7 4/6] mfd: tps65219: Add driver for TI TPS65219 PMIC Jerome Neanne
2022-11-15 22:26   ` Kevin Hilman
2022-11-15 23:14   ` Kevin Hilman
2022-11-16 13:58     ` Lee Jones
2022-11-16 18:11   ` Lee Jones
2022-11-04 15:23 ` [PATCH v7 5/6] Input: Add tps65219 interrupt driven powerbutton Jerome Neanne
2022-11-17 11:53   ` Lee Jones
2022-11-04 15:23 ` [PATCH v7 6/6] arm64: defconfig: Add tps65219 as modules Jerome Neanne
2022-11-15 22:23   ` Kevin Hilman
2022-11-17 16:00     ` Kevin Hilman
2022-12-05 18:08 ` [PATCH v7 0/6] Add support for TI TPS65219 PMIC Francesco Dolcini
2022-12-06 19:22   ` jerome Neanne
2023-05-22 11:57     ` jerome Neanne

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=c2a0f9fb-3b54-0a3f-2bfa-9575a9ae937f@phytec.de \
    --to=w.egorov@phytec.de \
    --cc=afd@ti.com \
    --cc=arnd@arndb.de \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=j-keerthy@ti.com \
    --cc=jeff@labundy.com \
    --cc=jneanne@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=marcel.ziswiler@toradex.com \
    --cc=msp@baylibre.com \
    --cc=narmstrong@baylibre.com \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=tony@atomide.com \
    --cc=vigneshr@ti.com \
    --cc=vkoul@kernel.org \
    --cc=will@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).