linux-kernel - Re: Raspberry Pi 4B: Failed to create device link with soc:firmware:gpio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f13906c0-1a0c-dfa4-dcd3-96ebc82aabd8@gmail.com>
Date:   Sun, 26 Feb 2023 11:13:53 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Saravana Kannan <saravanak@...gle.com>
Cc:     Stefan Wahren <stefan.wahren@...e.com>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel <linux-kernel@...r.kernel.org>,
        Android Kernel Team <kernel-team@...roid.com>
Subject: Re: Raspberry Pi 4B: Failed to create device link with
 soc:firmware:gpio



On 2/25/2023 5:58 PM, Florian Fainelli wrote:
> 
> 
> On 2/25/2023 4:01 PM, Saravana Kannan wrote:
>> On Sat, Feb 25, 2023 at 7:38 AM Florian Fainelli 
>> <f.fainelli@...il.com> wrote:
>>>
>>> Hi Saravana,
>>>
>>> Using v6.2-10217-ga93e884edf61v my Raspberry Pi 4B issues the following
>>> for the "extended GPIO" provider:
>>>
>>> [    5.969855] uart-pl011 fe201000.serial: Failed to create device link
>>> with soc:firmware:gpio
>>
>> Outside of this error, is it actually breaking anything? 
> 
> There is just this warning, there does not appear to be a functional issue.
> 
>> Also, can you
>> pull in this patch and tell me what it says? I want to know what the
>> flags are.
>> https://lore.kernel.org/lkml/20230225064148.274376-1-saravanak@google.com/

Pulling in this patch results in the following being printed:

[   14.866835] uart-pl011 fe201000.serial: Failed to create device link 
(0x180) with soc:firmware:gpio

>>
>> Can you also change every pr_debug and dev_dbg in drivers/base/core.c
>> to an info and then give me the logs as an attachment?
> 
> Sure will do.

Please find the log here:

https://gist.github.com/4e7e5e09ebfb3994505c917a8c0892d6

Thanks
-- 
Florian