From: Saravana Kannan <saravanak@google.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Android Kernel Team <kernel-team@android.com>
Subject: Re: Raspberry Pi 4B: Failed to create device link with soc:firmware:gpio
Date: Sat, 25 Feb 2023 16:01:28 -0800 [thread overview]
Message-ID: <CAGETcx-KLfxKae6-Kc74gOu2fiuu+5528j_TNEaY21U3_yZO0w@mail.gmail.com> (raw)
In-Reply-To: <03b70a8a-0591-f28b-a567-9d2f736f17e5@gmail.com>
On Sat, Feb 25, 2023 at 7:38 AM Florian Fainelli <f.fainelli@gmail.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? 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/
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?
> The kernel configuration I am using can be found here:
>
> https://gist.github.com/ffainelli/4eb83740c25b10f75b54560f8c8febb1
>
> And the DTS is arch/arm*/boot/dts/bcm2711-rpi-4-b.dts
Ah, is this yet another case of a DTS that's not upstream? Don't
worry, I'll still look at it as it might point to some existing
upstream issue too.
Thanks,
Saravana
next prev parent reply other threads:[~2023-02-26 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 15:38 Raspberry Pi 4B: Failed to create device link with soc:firmware:gpio Florian Fainelli
2023-02-26 0:01 ` Saravana Kannan [this message]
2023-02-26 1:58 ` Florian Fainelli
2023-02-26 19:13 ` Florian Fainelli
2023-03-01 7:49 ` Saravana Kannan
2023-03-01 16:57 ` Stefan Wahren
2023-03-01 18:00 ` Saravana Kannan
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=CAGETcx-KLfxKae6-Kc74gOu2fiuu+5528j_TNEaY21U3_yZO0w@mail.gmail.com \
--to=saravanak@google.com \
--cc=f.fainelli@gmail.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.wahren@i2se.com \
/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;
as well as URLs for NNTP newsgroup(s).