Linux Power Management development
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ulf Hansson <ulfh@kernel.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] pmdomain: core: switch to dynamic root device
Date: Tue, 9 Jun 2026 18:12:47 +0200	[thread overview]
Message-ID: <aig7f5rCZCbRyR9B@hovoldconsulting.com> (raw)
In-Reply-To: <CAMuHMdUHabMGJyJ7e7yp7DLC+JJc9k6NK9p4anj2wRKNuwZUng@mail.gmail.com>

Hi Geert,

On Tue, Jun 09, 2026 at 12:53:59PM +0200, Geert Uytterhoeven wrote:

> On Fri, 24 Apr 2026 at 12:41, Johan Hovold <johan@kernel.org> wrote:
> > Driver core expects devices to be dynamically allocated and will, for
> > example, complain loudly if a device that lacks a release function is
> > ever freed.
> >
> > Use root_device_register() to allocate and register the root device
> > instead of open coding using a static device.
> >
> > Signed-off-by: Johan Hovold <johan@kernel.org>
> 
> Thanks for your patch, which is now commit a96e40f4afdcb52a
> ("pmdomain: core: switch to dynamic root device") in pmdomain/next.
> On e.g. R-Car H1, R-Car M2-W, and R-Car H3, this causes scary messages
> when systemd-journald.service is started:
> 
>     synth uevent: /always-on: failed to send uevent
>     genpd_provider always-on: uevent: failed to send synthetic uevent: -22
>     synth uevent: /ca15-cpu0: failed to send uevent
>     genpd_provider ca15-cpu0: uevent: failed to send synthetic uevent: -22
>     [...]
> 
> Reverting the commit fixes the issue.

Thanks for the report and sorry about the breakage.

I mistakenly convinced myself that this would not be an issue due to the
pmdomain code making sure that the bus has been registered but missed
the two-step initialisation.

I just sent a fix here if you want to give it a spin:

	https://lore.kernel.org/lkml/20260609160634.246526-1-johan@kernel.org/

Johan

      parent reply	other threads:[~2026-06-09 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24 10:40 [PATCH] pmdomain: core: switch to dynamic root device Johan Hovold
2026-06-03 10:14 ` Ulf Hansson
2026-06-09 10:53 ` Geert Uytterhoeven
2026-06-09 11:02   ` Geert Uytterhoeven
2026-06-09 16:12   ` Johan Hovold [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=aig7f5rCZCbRyR9B@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=ulfh@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