linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Nishanth Menon <nm@ti.com>, jerome Neanne <jneanne@baylibre.com>
Cc: Lee Jones <lee@kernel.org>,
	lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
	kristo@kernel.org, dmitry.torokhov@gmail.com,
	krzysztof.kozlowski+dt@linaro.org, catalin.marinas@arm.com,
	will@kernel.org, tony@atomide.com, vigneshr@ti.com,
	bjorn.andersson@linaro.org, shawnguo@kernel.org,
	geert+renesas@glider.be, dmitry.baryshkov@linaro.org,
	marcel.ziswiler@toradex.com, vkoul@kernel.org,
	biju.das.jz@bp.renesas.com, arnd@arndb.de, jeff@labundy.com,
	afd@ti.com, narmstrong@baylibre.com, msp@baylibre.com,
	j-keerthy@ti.com, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-input@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v6 4/6] mfd: tps65219: Add driver for TI TPS65219 PMIC
Date: Mon, 07 Nov 2022 13:14:51 -0800	[thread overview]
Message-ID: <7heduewjp0.fsf@baylibre.com> (raw)
In-Reply-To: <20221105000104.rtj3r6ufqwqmepon@keenly>

Nishanth Menon <nm@ti.com> writes:

> On 13:58-20221104, jerome Neanne wrote:
>> 
> [...]
>
>> 
>> > 
>> > Can you try an compile with W=1 please.
>> This raise one warning on mfd:
>> drivers/mfd/tps65219.c:28:12: warning: ‘tps65219_soft_shutdown’ defined but
>> not used [-Wunused-function]
>>    28 | static int tps65219_soft_shutdown(struct tps65219 *tps)
>>       |            ^~~~~~~~~~~~~~~~~~~~~~
>> soft_shutdown has been validated and is used in TI baseline even if not
>> hooked in upstream version further to this review:
>> https://lore.kernel.org/lkml/20220825150224.826258-5-msp@baylibre.com/
>> 
>> It was a TI requirement to implement it...
>> Let me know if you want me to remove this function or if we can keep it like
>> this.
>
> There are platforms without psci, correct? I think the comment was to
> drop the force override with system-power-controller property,
>
> if (!pm_power_off) {
> 	tps65219_i2c_client = client;
> 	pm_power_off = &tps65219_pm_power_off;
> }
>
> Could still be valid for such platforms, no? I do see that the
> capability that the PMIC has - which is software shutdown is a valid
> feature that we support in many different PMIC drivers. Is'nt the job of
> the driver to introduce the functionality in a manner that is
> appropriate to the OS framework?

Yeah, I think Nishanth is right here.

We should probably keep the `if (!pm_power_off)` part so the PMIC will
be used if PSCI is not, but it also allows an easy way to test/use the PMIC
shutdown functionality downstream if needed.

Kevin

  reply	other threads:[~2022-11-07 21:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 14:05 [PATCH v6 0/6] Add support for TI TPS65219 PMIC Jerome Neanne
2022-10-11 14:05 ` [PATCH v6 1/6] DONOTMERGE: arm64: dts: ti: Add TI TPS65219 PMIC support for AM642 SK board Jerome Neanne
2022-10-11 14:05 ` [PATCH v6 2/6] DONOTMERGE: arm64: dts: ti: Add pinmux and irq mapping for TPS65219 external interrupts Jerome Neanne
2022-10-11 14:05 ` [PATCH v6 3/6] DONOTMERGE: arm64: dts: ti: k3-am642-sk: Enable tps65219 power-button Jerome Neanne
2022-10-11 14:05 ` [PATCH v6 4/6] mfd: tps65219: Add driver for TI TPS65219 PMIC Jerome Neanne
2022-10-31 11:00   ` Lee Jones
2022-11-04 12:58     ` jerome Neanne
2022-11-04 13:56       ` Lee Jones
2022-11-04 14:04         ` jerome Neanne
2022-11-05  0:01       ` Nishanth Menon
2022-11-07 21:14         ` Kevin Hilman [this message]
2022-11-09 21:59           ` Andrew Davis
2022-11-10  7:12             ` jerome Neanne
2022-11-10 17:00               ` Kevin Hilman
2022-11-10 17:44                 ` Andrew Davis
2022-11-10 20:16                   ` Kevin Hilman
2022-10-11 14:05 ` [PATCH v6 5/6] Input: Add tps65219 interrupt driven powerbutton Jerome Neanne
2022-10-12  9:48   ` jerome Neanne
2022-10-11 14:05 ` [PATCH v6 6/6] arm64: defconfig: Add tps65219 as modules Jerome Neanne
2022-10-11 14:48   ` Krzysztof Kozlowski
2022-10-12  8:39     ` jerome Neanne
2022-10-12 13:00       ` Krzysztof Kozlowski
2022-10-12 17:56         ` Kevin Hilman
2022-10-13 12:32           ` Krzysztof Kozlowski
2022-10-13 13:22             ` 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=7heduewjp0.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=afd@ti.com \
    --cc=arnd@arndb.de \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=bjorn.andersson@linaro.org \
    --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=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).