From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jiaqing Zhao <jiaqing.zhao@linux.intel.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v2] Revert "8250: add support for ASIX devices with a FIFO bug"
Date: Mon, 19 Jun 2023 15:42:13 +0200 [thread overview]
Message-ID: <2023061950-unrigged-dosage-59e2@gregkh> (raw)
In-Reply-To: <20230619100818.778176-1-jiaqing.zhao@linux.intel.com>
On Mon, Jun 19, 2023 at 10:08:19AM +0000, Jiaqing Zhao wrote:
> Commit eb26dfe8aa7e ("8250: add support for ASIX devices with a FIFO
> bug") merged on Jul 13, 2012 adds a quirk for PCI_VENDOR_ID_ASIX
> (0x9710). But that ID is the same as PCI_VENDOR_ID_NETMOS defined in
> 1f8b061050c7 ("[PATCH] Netmos parallel/serial/combo support") merged
> on Mar 28, 2005. In pci_serial_quirks array, the NetMos entry always
> takes precedence over the ASIX entry even since it was initially
> merged, code in that commit is always unreachable.
>
> In my tests adding the FIFO workaround to pci_netmos_init() makes no
> difference, and the vendor driver also does not have such workaround.
> Given that the code was never used for over a decade, it's safe to
> revert it.
>
> Also, the real PCI_VENDOR_ID_ASIX should be 0x125b, which is used on
> their newer AX99100 PCIe serial controllers released on 2016. The FIFO
> workaround should not be intended for these newer controllers, and it
> was never implemented in vendor driver.
>
> This reverts commit eb26dfe8aa7eeb5a5aa0b7574550125f8aa4c3b3.
>
> Signed-off-by: Jiaqing Zhao <jiaqing.zhao@linux.intel.com>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Fails to apply to my tree :(
Can you rebase this against the tty-next branch of my tty.git tree on
kernel.org?
thanks,
greg k-h
prev parent reply other threads:[~2023-06-19 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 10:08 [PATCH v2] Revert "8250: add support for ASIX devices with a FIFO bug" Jiaqing Zhao
2023-06-19 13:42 ` Greg Kroah-Hartman [this message]
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=2023061950-unrigged-dosage-59e2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jiaqing.zhao@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.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: 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