Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp4393378pxv; Mon, 5 Jul 2021 23:08:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwhspaEkzFe9eNhxSENUTdsnbXLwznjpJtyTbG9oRlj4aveuRZrPEY2ekx4zA6k7QqonUQm X-Received: by 2002:a92:360e:: with SMTP id d14mr13115017ila.106.1625551727152; Mon, 05 Jul 2021 23:08:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625551727; cv=none; d=google.com; s=arc-20160816; b=h33bM4UfU/c+LSKb0nvv/QJf+PcxIL0S3xOqQbCdV7oIWaESutK9/vWq7uVFZqkgR/ gEYSLSF6enCehLdQ9ZFbSJfOjpXWxbYvDikErlAdW+zCcnARN9xQRkk/i57TTrlUopek G1qoFK7umUCy2H3T/QHNMHsqQdjX6xkOtE6U31eVXWF5TkP/NhU/VE12UkQclCRyPfYy 6N0FqtqbZJ19YxkYSaNdj2bV1Py5cHNu9ZSDayp49oPwUVyEvD/4zDplF/FCDX4H7ZqI vLIsSeInQl3InRvjoCOUTeyudSolvG9CuOdEpQBunr0FJyKcBb+nf2cZsbaW1YEByI9T AksA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=BicthPpw23y2FsF1UbR3mzfkLh5Y7sZt9zqncg+I7ps=; b=nJhULokUAyDEGYwoHMWI9gP67oxl4nJhv1ejNAkgpAMtwbLZkZo46b6FzskTOMb2Nv 3wStopGx5Xyg+5XBe4c/nRaLKtvAV8jIIIwo5nceJu6RybtYK2jG0L+YRa/l7wtV0xWa yDk0Gt4cDTcG8GPJxC9+soo3niUTpl/wkMj59EtKCFTjMGXiRbTL1V5i/+VO5QRCANAz 2vGbW9kYHKm+/3gBWhl/OFlceCtamjRVcX4w4KaQuOTwfUw6eYJGB8l0/b6t8fc29U1Y hpmTFpv9CSpMVxHWEr3RWPXW65+EtFksVNfARjtvTArhkdl2HYMRP77QItRt6YgQdbeD 8xMA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=sVmzWWAz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m3si10543649ili.126.2021.07.05.23.08.34; Mon, 05 Jul 2021 23:08:47 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=sVmzWWAz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230081AbhGFGJL (ORCPT + 99 others); Tue, 6 Jul 2021 02:09:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59170 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230036AbhGFGJL (ORCPT ); Tue, 6 Jul 2021 02:09:11 -0400 Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2EDD0C061574; Mon, 5 Jul 2021 23:06:32 -0700 (PDT) Received: by mail-il1-x133.google.com with SMTP id b18so47775ilf.8; Mon, 05 Jul 2021 23:06:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=BicthPpw23y2FsF1UbR3mzfkLh5Y7sZt9zqncg+I7ps=; b=sVmzWWAzvnnLrxV6pwBJ7JMhtpIixamWBz1xFudMY62uK7EJSaI+5TNwuKaUsohDX7 030CmvMQsn7CCRraXAKGB9RkYiZUON6C2fFp6Bff49Hifd8mwey7Cag0kFwcI43Ajg3c rKiJxJIr6UGvaKA/u6Y+H0UC3ylveS3s4cc2qXdraJyudJqXPmdWmjDfQB0A+MUjc97B efPBZ7mTPNWqaEiiSMyCbmhHbCkWEYpLh0RAPpnzByBREgoC3x/0Lwi6Rh4KuhVIVKhC 1S9oOCc5ICDX9u9Gi1H0OsfS0AzikQsi3eqSoCIzI6/8dAkA+d5/AYwwgm0bUpYua9+V buCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=BicthPpw23y2FsF1UbR3mzfkLh5Y7sZt9zqncg+I7ps=; b=e23ltipYaz7vZ92+TI7PN8x/DGrp0ZlpzxI/yDU1QSOhQuuukfqLRg8FeP+JFbLlCB YUjzfIVeKEsapqGFB8rSK6UEJBuNOzAulj/KwgmY0439/JM6x2jruYlzP8JQCQdEcGeF v79Gi+YqTTtgUnhsE8bAW0dtzMhXPExiuZfpAcjFSv0WYzr5cw/xWbn8p9cUWZHPtYrU sVNXjW2lFzXkU8M3pTxD2F3UU33seXVju4ZCgEIj3ctUjz9AOlDBdWMih9MGu1sIqdvu q+MFkpLWePz6rZxFvz9yYl6tGutLmvlOeaVsu5GVr3xjFgzx+/DoDFsvOplErWht5sPU Pfvg== X-Gm-Message-State: AOAM532QVI9dZYDe4wFQlvvoUb5X36K98oNubMIbpJz79O0Jbmb26rjV X6kJY4V9uU4Po7QVPq+/Q+jsNrouKLQkXElcqJI= X-Received: by 2002:a92:d4d0:: with SMTP id o16mr10065139ilm.153.1625551591404; Mon, 05 Jul 2021 23:06:31 -0700 (PDT) MIME-Version: 1.0 References: <20210701154634.GA60743@bjorn-Precision-5520> <67a9e1fa.81a9.17a64c8e7f7.Coremail.chenhuacai@loongson.cn> In-Reply-To: From: Art Nikpal Date: Tue, 6 Jul 2021 14:06:19 +0800 Message-ID: Subject: Re: Re: [PATCH 0/4] PCI: replace dublicated MRRS limit quirks To: Huacai Chen Cc: =?UTF-8?B?6ZmI5Y2O5omN?= , Bjorn Helgaas , Neil Armstrong , Yue Wang , Kevin Hilman , Lorenzo Pieralisi , Rob Herring , Krzysztof Wilczynski , Jerome Brunet , Christian Hewitt , Martin Blumenstingl , PCI , linux-arm-kernel , "open list:ARM/Amlogic Meson..." , LKML , Artem Lapkin , Nick Xie , Gouwa Wang Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >But, Loongson platform has newer revision of hardware, and the MRRS > quirk has changed, please see: > https://patchwork.kernel.org/project/linux-pci/list/?series=3D509497 > Huacai OK! tnx for information ! maybe we can cooperate and make one universal quirk for all On Tue, Jul 6, 2021 at 9:36 AM Huacai Chen wrote: > > Hi, Art, > > On Mon, Jul 5, 2021 at 4:35 PM Art Nikpal wrote: > > > > > Does that means keystone and Loongson has the same MRRS problem? And = what should I do now? > > > > Look like yes ! and amlogic has the same problem. > > I think somebody need to rewrite it all to one common quirk for this pr= oblem. > > > > If no one has any objection, I can try to remake it again. > But, Loongson platform has newer revision of hardware, and the MRRS > quirk has changed, please see: > https://patchwork.kernel.org/project/linux-pci/list/?series=3D509497 > > Huacai > > > > On Fri, Jul 2, 2021 at 9:15 AM =E9=99=88=E5=8D=8E=E6=89=8D wrote: > > > > > > Hi, Bjorn, > > > > > > > -----=E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6----- > > > > =E5=8F=91=E4=BB=B6=E4=BA=BA: "Bjorn Helgaas" > > > > =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2021-07-01 23:46:34 (=E6= =98=9F=E6=9C=9F=E5=9B=9B) > > > > =E6=94=B6=E4=BB=B6=E4=BA=BA: "Artem Lapkin" > > > > =E6=8A=84=E9=80=81: narmstrong@baylibre.com, yue.wang@Amlogic.co= m, khilman@baylibre.com, lorenzo.pieralisi@arm.com, robh@kernel.org, kw@lin= ux.com, jbrunet@baylibre.com, christianshewitt@gmail.com, martin.blumenstin= gl@googlemail.com, linux-pci@vger.kernel.org, linux-arm-kernel@lists.infrad= ead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org, a= rt@khadas.com, nick@khadas.com, gouwa@khadas.com, "Huacai Chen" > > > > =E4=B8=BB=E9=A2=98: Re: [PATCH 0/4] PCI: replace dublicated MRRS= limit quirks > > > > > > > > [+cc Huacai] > > > > > > > > On Sat, Jun 19, 2021 at 02:39:48PM +0800, Artem Lapkin wrote: > > > > > Replace dublicated MRRS limit quirks by mrrs_limit_quirk fr= om core > > > > > * drivers/pci/controller/dwc/pci-keystone.c > > > > > * drivers/pci/controller/pci-loongson.c > > > > > > > > s/dublicated/duplicated/ (several occurrences) > > > > > > > > Capitalize subject lines. > > > > > > > > Use "git log --online" to learn conventions and follow them. > > > > > > > > Add "()" after function names. > > > > > > > > Capitalize acronyms appropriately (NVMe, MRRS, PCI, etc). > > > > > > > > End sentences with periods. > > > > > > > > A "move" patch must include both the removal and the addition an= d make > > > > no changes to the code itself. > > > > > > > > Amlogic appears without explanation in 2/4. Must be separate pa= tch to > > > > address only that specific issue. Should reference published er= ratum > > > > if possible. "Solves some issue" is not a compelling justificat= ion. > > > > > > > > The tree must be consistent and functionally the same or improve= d > > > > after every patch. > > > > > > > > Add to pci_ids.h only if symbol used more than one place. > > > > > > > > See > > > > https://lore.kernel.org/r/20210701074458.1809532-3-chenhuacai@lo= ongson.cn, > > > > which looks similar. Combine efforts if possible and cc Huacai = so > > > > you're both aware of overlapping work. > > > > > > > > More hints in case they're useful: > > > > https://lore.kernel.org/linux-pci/20171026223701.GA25649@bhelgaa= s-glaptop.roam.corp.google.com/ > > > > > > > > > Both ks_pcie_quirk loongson_mrrs_quirk was rewritten withou= t any > > > > > functionality changes by one mrrs_limit_quirk > > > Does that means keystone and Loongson has the same MRRS problem? And = what should I do now? > > > > > > Huacai > > > > > > > > > > Added DesignWare PCI controller which need same quirk for > > > > > * drivers/pci/controller/dwc/pci-meson.c (PCI_DEVICE_ID_SYN= OPSYS_HAPSUSB3) > > > > > > > > > > This quirk can solve some issue for Khadas VIM3/VIM3L(Amlog= ic) > > > > > with HDMI scrambled picture and nvme devices at intensive w= riting... > > > > > > > > > > come from: > > > > > * https://lore.kernel.org/linux-pci/20210618063821.1383357-= 1-art@khadas.com/ > > > > > > > > > > Artem Lapkin (4): > > > > > PCI: move Keystone and Loongson device IDs to pci_ids > > > > > PCI: core: quirks: add mrrs_limit_quirk > > > > > PCI: keystone move mrrs quirk to core > > > > > PCI: loongson move mrrs quirk to core > > > > > > > > > > -- > > > > > 2.25.1 > > > > > > > > > > > > > >