mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Lee Jones <lee@kernel.org>
Cc: Brian Mak <makb@juniper.net>,
	Herve Codina <herve.codina@bootlin.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] mfd: core: Preserve OF node when ACPI handle is present
Date: Fri, 6 Mar 2026 16:35:20 +0200	[thread overview]
Message-ID: <aarmKE49wgbIblRb@ashevche-desk.local> (raw)
In-Reply-To: <20260306133806.GM183676@google.com>

On Fri, Mar 06, 2026 at 01:38:06PM +0000, Lee Jones wrote:
> On Thu, 26 Feb 2026, Brian Mak wrote:

...

> > +	/*
> > +	 * FIXME: The fwnode design doesn't allow proper stacking/sharing. This
> 
> So when will this be fixed exactly?

I don't know, it's a huge task that requires of redesigning how struct
fwnode_handle looks like and how it cohabits with struct device. Do you
you think that NOTE will be more appropriate, because it may span several
releases.

> > +	 * should eventually turn into a device fwnode API call that will allow
> > +	 * prepending to a list of fwnodes (with ACPI taking precedence).
> > +	 *
> > +	 * set_primary_fwnode() is used here, instead of device_set_node(), as
> > +	 * device_set_node() will overwrite the existing fwnode, which may be an
> > +	 * OF node that was populated earlier. To support a use case where ACPI
> > +	 * and OF is used in conjunction, we call set_primary_fwnode() instead.
> > +	 */
> > +	if (adev)
> > +		set_primary_fwnode(&pdev->dev, acpi_fwnode_handle(adev));
> > +	else
> > +		set_primary_fwnode(&pdev->dev, acpi_fwnode_handle(parent));
> >  }

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-03-06 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 22:45 Brian Mak
2026-02-27  5:40 ` Andy Shevchenko
2026-03-06 13:38 ` Lee Jones
2026-03-06 14:35   ` Andy Shevchenko [this message]
2026-03-10  9:21     ` Lee Jones
2026-03-10 10:25       ` Andy Shevchenko
2026-03-11 17:00         ` Brian Mak
2026-03-11 17:20           ` Andy Shevchenko

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=aarmKE49wgbIblRb@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=herve.codina@bootlin.com \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=makb@juniper.net \
    --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®