mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Maurizio Casciano <mauriziocasciano7@gmail.com>
Cc: Hans de Goede <hansg@kernel.org>,
	linux-pm@vger.kernel.org,  linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] power: supply: core: Honor supplied-from with CONFIG_OF=y
Date: Wed, 9 Sep 2026 22:47:46 +0200	[thread overview]
Message-ID: <aqHFUSdrYUR1DJ6L@venus> (raw)
In-Reply-To: <CAO7O_xi-BYfGb428q1TO4ERp059-BOq78PZR5Ad-bs1ikVkmZQ@mail.gmail.com>

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

Hi,

On Tue, Sep 01, 2026 at 07:04:28PM +0200, Maurizio Casciano wrote:
> Thank you for the review.
> 
> I agree that firmware-node references should retain priority over the
> legacy name-based mechanism. The "supplied-from" property should only be
> used as a fallback when no "power-supplies" references are present,
> including the case where the consumer has no firmware node.
> 
> For v2 I will preserve the existing order as follows:
> 
> 1. honor an explicitly pre-populated supplied_from list;
> 2. resolve "power-supplies" firmware-node references when present;
> 3. fall back to the name-based "supplied-from" property only when no
>    references were specified.
> 
> Errors while resolving specified references, including -EPROBE_DEFER,
> will still be propagated rather than triggering the fallback.
> 
> I will wait for Sebastian's opinion before posting v2.

Ack.

Also FWIW the power-supply core has been migrated to be fully fwnode
based, so the CONFIG_OF is not really correct anymore anyways. Let's
have a single implementation for power_supply_check_supplies().

Greetings,

-- Sebastian

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

      reply	other threads:[~2026-09-09 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260901145156.3177187-1-mauriziocasciano7@gmail.com>
2026-09-01 16:07 ` Hans de Goede
2026-09-01 17:04   ` Maurizio Casciano
2026-09-09 20:47     ` Sebastian Reichel [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=aqHFUSdrYUR1DJ6L@venus \
    --to=sebastian.reichel@collabora.com \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mauriziocasciano7@gmail.com \
    --cc=stable@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®