[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPDyKFrfe8joPPiUqkRv9BHmewwphWQshZzpBPbQiZ53z1CZow@mail.gmail.com>
Date: Thu, 2 Sep 2021 00:11:38 +0200
From: Ulf Hansson <ulf.hansson@...aro.org>
To: Saravana Kannan <saravanak@...gle.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Android Kernel Team <kernel-team@...roid.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1] driver core: fw_devlink: Don't create device links for
devices not on a bus
[...]
> fw_devlink trying to interpret DT dependencies can sometimes end up in
> this situation for some uncommon cases. But it's not helping [1] or
> [2], so for now let's drop this patch. I'll come back to this if I
> need this to fix any real issue.
Just to be clear, the issue is really there, with the psci power
domain, for example.
I am working with an ARM vendor on a platform that has a child node
below the common soc node and which child node is a consumer of the
psci power domain provider node. We fail to get the ->sync_state() to
be called, for reasons that have been explained by now, I think.
The reason for explaining the problem with a superficial example was
to try to easier point out the problem.
That said, I would certainly appreciate your help to get this fixed,
in one way or the other.
>
> -Saravana
Kind regards
Uffe
Powered by blists - more mailing lists