[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210428084059.ue34zgzjod7jawh3@bogus>
Date: Wed, 28 Apr 2021 09:40:59 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: Saravana Kannan <saravanak@...gle.com>,
Sudeep Holla <sudeep.holla@....com>,
Cristian Marussi <cristian.marussi@....com>,
Jim Quinlan <james.quinlan@...adcom.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Al Cooper <alcooperx@...il.com>,
Michael Walle <michael@...le.cc>,
Jon Hunter <jonathanh@...dia.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Guenter Roeck <linux@...ck-us.net>,
Android Kernel Team <kernel-team@...roid.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 3/3] Revert "Revert "driver core: Set fw_devlink=on by
default""
On Tue, Apr 27, 2021 at 09:47:08AM -0700, Florian Fainelli wrote:
> On 4/27/2021 9:24 AM, Saravana Kannan wrote:
[...]
> > The part that's confusing to me is that the mbox node is disabled in
> > the DT you attached. fw_devlink is smart enough to ignore disabled
> > nodes. Is it getting enabled by the bootloader? Can you please try
> > deleting the reference to the brcm_scmi_mailbox from the scmi node and
> > see if it helps? Or leave it really disabled?
>
> Removing the 'mboxes' phandle works, see my other reply to Sudeep and I
> should have captured the DT from the Linux prompt after it has been
> finalized and where the mbox node is marked as enabled unfortunately.
I know Saravana has compiled the list of workarounds in preferred order
which excludes this which is good. Anyways I will convey my point. Disabling
mailbox controller node may not be always available option as it could be
providing multiple channels and the stale mboxes reference in SCMI might
be just one of the consumer. Removing mboxes seems only reasonable solution
to me in such scenario.
--
Regards,
Sudeep
Powered by blists - more mailing lists