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

On Friday 04 August 2023 15:54:26 Russell King (Oracle) wrote:
> On Fri, Aug 04, 2023 at 12:35:13PM +0100, Russell King (Oracle) wrote:
> > Hi,
> > 
> > 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.
> 
> Further testing - same platform with a mini-PCIe SATA card:
> 
> 01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
> 
> with a WD10JPVX-60JC3T0 2.5" drive with hdparm -t:
> 
>  Timing buffered disk reads: 344 MB in  3.01 seconds = 114.16 MB/sec
> 
> which is about what is expected for spinny-rust 2.5" drives.
> 
> This was tested with ASPM and AER disabled. AER isn't supported anyway
> as pcie_init_service_irqs() fails with -ENODEV.

So another thing which is broken. Perfect!

> For further info, the Atheros WiFi card was:
> 
> 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter
> 
> -- 
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2023-08-08 16:08 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 [this message]
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
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=20230808072740.bn6ketsfatxw55ge@pali \
    --to=pali@kernel.org \
    --cc=bhelgaas@google.com \
    --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