From: Stefan Wahren <stefan.wahren@i2se.com> To: Florian Fainelli <f.fainelli@gmail.com>, Nicolas Saenz Julienne <nsaenz@kernel.org> Cc: Ray Jui <rjui@broadcom.com>, Scott Branden <sbranden@broadcom.com>, bcm-kernel-feedback-list@broadcom.com, Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>, Saravana Kannan <saravanak@google.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, soc@kernel.org, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] ARM: multi_v7_defconfig: Make NOP_USB_XCEIV driver built-in Date: Mon, 12 Jul 2021 07:04:01 +0200 [thread overview] Message-ID: <b654ecdf-20f1-1a7d-2955-901e5579345d@i2se.com> (raw) In-Reply-To: <d3154d8d-6f4c-b59b-add1-f3e75462309a@gmail.com> Hi Florian, Am 11.07.21 um 23:27 schrieb Florian Fainelli: > > > On 7/10/2021 4:04 AM, Stefan Wahren wrote: >> The usage of usb-nop-xceiv PHY on Raspberry Pi boards with BCM283x has >> been a "regression source" a lot of times. The last case is breakage of >> USB mass storage boot has been commit e590474768f1 ("driver core: Set >> fw_devlink=on by default") for multi_v7_defconfig. As long as >> NOP_USB_XCEIV is configured as module, the dwc2 USB driver defer probing >> endlessly and prevent booting from USB mass storage device. So make >> the driver built-in as in bcm2835_defconfig and arm64/defconfig. > > Should not that be fixed somehow? maybe that why send this bug report, but never get a feedback [1] My spare time is too limited to fight multiple regressions on Raspberry Pi, so i decided send at least this solution. [1] - https://www.spinics.net/lists/arm-kernel/msg905208.html > >> >> Reported-by: Ojaswin Mujoo <ojaswin98@gmail.com> >> Fixes: e590474768f1 ("driver core: Set fw_devlink=on by default") >> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com> >> ---
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren@i2se.com> To: Florian Fainelli <f.fainelli@gmail.com>, Nicolas Saenz Julienne <nsaenz@kernel.org> Cc: Ray Jui <rjui@broadcom.com>, Scott Branden <sbranden@broadcom.com>, bcm-kernel-feedback-list@broadcom.com, Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>, Saravana Kannan <saravanak@google.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, soc@kernel.org, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] ARM: multi_v7_defconfig: Make NOP_USB_XCEIV driver built-in Date: Mon, 12 Jul 2021 07:04:01 +0200 [thread overview] Message-ID: <b654ecdf-20f1-1a7d-2955-901e5579345d@i2se.com> (raw) Message-ID: <20210712050401.NfZJ4tINRdfV7CDuCN5gdHvVZ_HDbouRa6wEq-KBdxE@z> (raw) In-Reply-To: <d3154d8d-6f4c-b59b-add1-f3e75462309a@gmail.com> Hi Florian, Am 11.07.21 um 23:27 schrieb Florian Fainelli: > > > On 7/10/2021 4:04 AM, Stefan Wahren wrote: >> The usage of usb-nop-xceiv PHY on Raspberry Pi boards with BCM283x has >> been a "regression source" a lot of times. The last case is breakage of >> USB mass storage boot has been commit e590474768f1 ("driver core: Set >> fw_devlink=on by default") for multi_v7_defconfig. As long as >> NOP_USB_XCEIV is configured as module, the dwc2 USB driver defer probing >> endlessly and prevent booting from USB mass storage device. So make >> the driver built-in as in bcm2835_defconfig and arm64/defconfig. > > Should not that be fixed somehow? maybe that why send this bug report, but never get a feedback [1] My spare time is too limited to fight multiple regressions on Raspberry Pi, so i decided send at least this solution. [1] - https://www.spinics.net/lists/arm-kernel/msg905208.html > >> >> Reported-by: Ojaswin Mujoo <ojaswin98@gmail.com> >> Fixes: e590474768f1 ("driver core: Set fw_devlink=on by default") >> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com> >> --- _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-12 5:04 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-10 11:04 [PATCH] ARM: multi_v7_defconfig: Make NOP_USB_XCEIV driver built-in Stefan Wahren 2021-07-10 11:04 ` Stefan Wahren 2021-07-11 21:27 ` Florian Fainelli 2021-07-11 21:27 ` Florian Fainelli 2021-07-12 5:04 ` Stefan Wahren [this message] 2021-07-12 5:04 ` Stefan Wahren 2021-07-16 21:22 ` patchwork-bot+linux-soc 2021-07-16 21:24 ` Arnd Bergmann 2021-07-16 21:24 ` Arnd Bergmann
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=b654ecdf-20f1-1a7d-2955-901e5579345d@i2se.com \ --to=stefan.wahren@i2se.com \ --cc=arnd@arndb.de \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=f.fainelli@gmail.com \ --cc=gregkh@linuxfoundation.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-rpi-kernel@lists.infradead.org \ --cc=nsaenz@kernel.org \ --cc=olof@lixom.net \ --cc=rjui@broadcom.com \ --cc=saravanak@google.com \ --cc=sbranden@broadcom.com \ --cc=soc@kernel.org \ /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: linkBe 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).