public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PCI: mvebu: Mark driver as BROKEN
Date: Tue, 8 Aug 2023 09:27:01 +0200	[thread overview]
Message-ID: <20230808072701.gx6apjnnrppv7sit@pali> (raw)
In-Reply-To: <20230804134622.pmbymxtzxj2yfhri@pengutronix.de>

On Friday 04 August 2023 15:46:22 Uwe Kleine-König wrote:
> [Cc += linux-arm-kernel list]
> 
> 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.
> 
> While this is true there is really a problem on my platform with
> accessing the hard disks via that pci controller and a 88SE9215 SATA
> controller. While it seems to work in principle, it's incredible slow.

Exactly those are things which randomly does not work.

> I intend to bisect that, 6.1.x is still fine. Don't know when I find the
> time though, as there are a few things that are more important
> currently.
> 
> +1 on some information about what is already known about the breakage.
> 
> > Please revert this patch.
> > 
> > Thanks.
> > 
> > On Sat, Jan 14, 2023 at 05:41:25PM +0100, Pali Rohár wrote:
> > > People are reporting that pci-mvebu.c driver does not work with recent
> > > mainline kernel. There are more bugs which prevents its for daily usage.
> > > So lets mark it as broken for now, until somebody would be able to fix it
> > > in mainline kernel.
> > > 
> > > Signed-off-by: Pali Rohár <pali@kernel.org>
> > > 
> > > ---
> > > Bjorn: I would really appreciate if you take this change and send it in
> > > pull request for v6.2 release. There is no reason to wait more longer.
> > > 
> > > 
> > > I'm periodically receiving emails that driver does not work correctly
> > > anymore, PCIe cards are not detected or that they crashes during boot.
> > > 
> > > Some of the issues are handled in patches which are waiting on the list for
> > > a long time and nobody cares for them. Some others needs investigation.
> > > 
> > > I'm really tired in replying to those user emails as I cannot do more in
> > > this area. I have asked more people for help but either there were only
> > > promises without any action for more than year or simple no direction how
> > > to move forward or what to do with it.
> > > 
> > > So mark this driver as broken. Users would see the real current state
> > > and hopefully will stop reporting me old or new bugs.
> > > ---
> > >  drivers/pci/controller/Kconfig | 1 +
> > >  1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/drivers/pci/controller/Kconfig b/drivers/pci/controller/Kconfig
> > > index 1569d9a3ada0..b4a4d84a358b 100644
> > > --- a/drivers/pci/controller/Kconfig
> > > +++ b/drivers/pci/controller/Kconfig
> > > @@ -9,6 +9,7 @@ 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
> > > -- 
> > > 2.20.1
> > > 
> > 
> > -- 
> > RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> > FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
> > 
> 
> -- 
> Pengutronix e.K.                           | Uwe Kleine-König            |
> Industrial Linux Solutions                 | https://www.pengutronix.de/ |



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230114164125.1298-1-pali@kernel.org>
     [not found] ` <ZMzicVQEyHyZzBOc@shell.armlinux.org.uk>
2023-08-04 13:46   ` [PATCH] PCI: mvebu: Mark driver as BROKEN Uwe Kleine-König
2023-08-04 17:00     ` Uwe Kleine-König
2023-08-08  7:27     ` Pali Rohár [this message]
2023-08-08  7:38       ` Uwe Kleine-König
2023-08-08  7:56         ` Pali Rohár
     [not found] <20230808072605.n3rjfsxuogza7qth@pali>
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=20230808072701.gx6apjnnrppv7sit@pali \
    --to=pali@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-arm-kernel@lists.infradead.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