From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Simon Glass <sjg@chromium.org>
Cc: Wadim Egorov <w.egorov@phytec.de>,
u-boot@lists.denx.de, upstream@lists.phytec.de,
trini@konsulko.com, jh80.chung@samsung.com,
ilias.apalodimas@linaro.org, thomas.petazzoni@bootlin.com,
ian.ray@gehealthcare.com, dario.binacchi@amarulasolutions.com,
aford173@gmail.com, seanga2@gmail.com, nm@ti.com,
francesco@dolcini.it
Subject: Re: [PATCH] Revert "power-domain: Add refcounting"
Date: Tue, 22 Apr 2025 10:45:15 +0200 [thread overview]
Message-ID: <87plh4k2jo.fsf@bootlin.com> (raw)
In-Reply-To: <CAFLszThLdBepQ+utC33iOJDO0da3u7o3zrH_nFKkJt8aPcpbdg@mail.gmail.com> (Simon Glass's message of "Fri, 18 Apr 2025 11:19:28 -0600")
Hi Simon,
>> This sadly needs to get in, there have been 3 or 4 reports already, as
>> many boards are broken. We need to find another way to add refcounting
>> (otherwise some imx8* features will stay broken), but it requires more
>> thinking time.
>>
>> Acked-by: Miquel Raynal <miquel.raynal@bootlin.com>
>
> We had this discussion on your patch and you ended up with a
> 'low-level' function to provide the base functionality. But it would
> be easier if you retained the current behaviour and then added
> ref-counting to two new functions. Then people can migrate.
It's not the fact that people are using refcounting which breaks. It is
the fact that the device model does not support well the fact that one
DT node might be used to picture several devices. The clock subsystem
handles that by registering all clocks manually, and at some point
abuses one of the uclass internal structures (there is a FIXME about
that). It's not even the drivers that break.
> Of course, people perhaps won't migrate. This sort of thing is quite
> tricky. But I still think this would be an easier route. You could
> perhaps even add a Kconfig option like POWER_DOMAIN_NO_REF_COUNT which
> uses the current behaviour.
I now have an idea how to improve the power domain uclass to make it
fit, let's see if that works, otherwise I might fallback to this
solution indeed.
Thanks,
Miquèl
next prev parent reply other threads:[~2025-04-22 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 11:53 [PATCH] Revert "power-domain: Add refcounting" Wadim Egorov
2025-04-18 7:10 ` Miquel Raynal
2025-04-18 17:19 ` Simon Glass
2025-04-22 8:45 ` Miquel Raynal [this message]
2025-04-18 17:12 ` Tom Rini
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=87plh4k2jo.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=aford173@gmail.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=francesco@dolcini.it \
--cc=ian.ray@gehealthcare.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jh80.chung@samsung.com \
--cc=nm@ti.com \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.de \
/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