Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: mvebu: Mark driver as BROKEN
Date: Tue, 8 Aug 2023 09:31:54 +0200	[thread overview]
Message-ID: <20230808073154.bstm3xwtjalyq3qb@pali> (raw)
In-Reply-To: <20230804170655.GA147757@bhelgaas>

On Friday 04 August 2023 12:06:55 Bjorn Helgaas wrote:
> [+cc Krzysztof]
> 
> On Fri, Aug 04, 2023 at 12:35:13PM +0100, Russell King (Oracle) wrote:
> > So it seems this patch got applied, but it wasn't Cc'd to
> > linux-arm-kernel or anyone else, so those of us with platforms never
> > had a chance to comment on it.
> > 
> > *** This change causes a regression to working setups. ***
> > 
> > It appears that the *only* reason this patch was proposed is to stop a
> > kernel developer receiving problem reports from a set of users, but
> > completely ignores that there is another group of users where this works
> > fine - and thus the addition of this patch causes working setups to
> > regress.
> > 
> > Because one is being bothered with problem reports is not a reason to
> > mark a driver broken - and especially not doing so in a way that those
> > who may be affected don't get an opportunity to comment on the patch!
> > Also, there is _zero_ information provided on what the reported problems
> > actually are, so no one else can guess what these issues are.
> > 
> > However, given that there are working setups and this change causes
> > those to regress, it needs to be reverted.
> > 
> > For example, I have an Atheros PCIe WiFi card in an Armada 388 Clearfog
> > platform, and this works fine.
> > 
> > Uwe has a SATA controller for a bunch of disks in an Armada 370 based
> > NAS platform that is connected to PCIe, and removing PCIe support
> > effectively makes his platform utterly useless.
> > 
> > Please revert this patch.
> 
> Sorry for the inconvenience.
> 
> I was under the mistaken impression that making the driver depend on
> CONFIG_BROKEN would keep the driver available but only if the user
> explicitly requested it, similar to how 
> CONFIG_COMPILE_TEST works.  But obviously that's not the case, so
> we'll revert the change.
> 
> I queued up the revert below, including a note in the Kconfig help
> text about the known issues.
> 
> commit 814b6bb15367 ("Revert "PCI: mvebu: Mark driver as BROKEN"")
> Author: Bjorn Helgaas <bhelgaas@google.com>
> Date:   Fri Aug 4 11:54:43 2023 -0500
> 
>     Revert "PCI: mvebu: Mark driver as BROKEN"
>     
>     b3574f579ece ("PCI: mvebu: Mark driver as BROKEN") made it impossible to
>     enable the pci-mvebu driver.  The driver does have known problems, but as
>     Russell and Uwe reported, it does work in some configurations, so removing
>     it broke some working setups.
>     
>     Revert b3574f579ece so pci-mvebu is available.  Mention the known problems
>     in the Kconfig help text.
>     
>     Reported-by: Russell King (Oracle) <linux@armlinux.org.uk>
>     Link: https://lore.kernel.org/r/ZMzicVQEyHyZzBOc@shell.armlinux.org.uk
>     Reported-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>     Link: https://lore.kernel.org/r/20230804134622.pmbymxtzxj2yfhri@pengutronix.de
>     Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> 

What you are trying to achieve with this patch now? Do you think that it
is really correct to show that everything is working for everybody
correctly? Use a common sense here.

Or this is a way how kernel people are fixing bugs?

Now I'm starting understand why majority of HW industry say to not use
"unsupported mainline kernel" and instead use our prepared patched
kernels...

> diff --git a/drivers/pci/controller/Kconfig b/drivers/pci/controller/Kconfig
> index 8d49bad7f847..478f158b2dfb 100644
> --- a/drivers/pci/controller/Kconfig
> +++ b/drivers/pci/controller/Kconfig
> @@ -179,13 +179,15 @@ config PCI_MVEBU
>  	depends on MVEBU_MBUS
>  	depends on ARM
>  	depends on OF
> -	depends on BROKEN
>  	select PCI_BRIDGE_EMUL
>  	help
>  	 Add support for Marvell EBU PCIe controller. This PCIe controller
>  	 is used on 32-bit Marvell ARM SoCs: Dove, Kirkwood, Armada 370,
>  	 Armada XP, Armada 375, Armada 38x and Armada 39x.
>  
> +	 This driver has known problems that may cause crashes during boot
> +	 and failure to detect PCIe devices in some cases.
> +
>  config PCIE_MEDIATEK
>  	tristate "MediaTek PCIe controller"
>  	depends on ARCH_AIROHA || ARCH_MEDIATEK || COMPILE_TEST

  parent reply	other threads:[~2023-08-08 16:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 16:41 [PATCH] PCI: mvebu: Mark driver as BROKEN Pali Rohár
2023-01-15 22:02 ` Luís Mendes
2023-02-06 22:45 ` Pali Rohár
2023-02-09  9:02 ` Lorenzo Pieralisi
2023-08-04 11:35 ` Russell King (Oracle)
2023-08-04 13:46   ` Uwe Kleine-König
2023-08-04 17:00     ` Uwe Kleine-König
2023-08-08  7:27     ` Pali Rohár
2023-08-08  7:38       ` Uwe Kleine-König
2023-08-08  7:56         ` Pali Rohár
2023-08-04 14:54   ` Russell King (Oracle)
2023-08-08  7:27     ` Pali Rohár
2023-08-08  8:31       ` Russell King (Oracle)
2023-08-04 17:06   ` Bjorn Helgaas
2023-08-04 19:44     ` Russell King (Oracle)
2023-08-06 22:06       ` Luís Mendes
2023-08-08  7:31     ` Pali Rohár [this message]
2023-08-08  8:01       ` Uwe Kleine-König
2023-08-08 19:01         ` Pali Rohár
2023-08-08  8:32       ` Russell King (Oracle)
2023-08-08  7:26   ` Pali Rohár
2023-08-08  8:28     ` Russell King (Oracle)
2023-08-08  8:42       ` Russell King (Oracle)
2023-08-08 19:07         ` Pali Rohár
2023-08-08 19:06       ` Pali Rohár
2023-08-08 19:29         ` Russell King (Oracle)
2023-08-08 19:41         ` Bjorn Helgaas
2023-08-08 16:26     ` Bjorn Helgaas
2023-08-08 19:20       ` Pali Rohár
2023-08-08 19:54         ` Russell King (Oracle)

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=20230808073154.bstm3xwtjalyq3qb@pali \
    --to=pali@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lpieralisi@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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