Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp4256564pxv; Mon, 5 Jul 2021 18:41:11 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwvMK9Xi8KT9n5S5ITYDkCxbXgMeJ6YhEagiP5aSdUfkkP9CTwYXQ/cufkXG5cZWyWq9CYx X-Received: by 2002:a17:907:2d2a:: with SMTP id gs42mr10945174ejc.371.1625535671646; Mon, 05 Jul 2021 18:41:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625535671; cv=none; d=google.com; s=arc-20160816; b=OQ+92Pg/c1M7nhU88dw2TK7AM7Ftm0G10JbT1gAt5NiuxDOsKEpi2OnaT0WRj2GIrI 2ofqyqcqH15asNuX+hlHmqm1njpDgQs4ILslkNmHC+nJXtq1MbCdzoqIM9NcDuOgAyAT V40bi/XkzzZGJW7n4eIrbiuD2ICPyabvJKHTNet5HYwhb+tI31TQsONjp96phTEbDuNH aLtj4azj0gC+eYo78k6VvB8bA202B/5R9Xjuc6tICYjH18X+7899B7Df0SCU0kvJRMil K+V3f4s/wU9VHOnhJU8j3bo/bB14phxAhk11akigy4bdc0eclsg/F6d1Aw1KRq59vFVb eYpA== 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=B582vdrs46kitJpA3JaiMzIr2mncrXCNua47i7ErJFI=; b=uAaq3bBsdMHJ9Y0GlKwiVJvLuLhFH74WIF8QSQzdnkvaXSe2DnB7mucS81qGlr9gFH q/tmUNo2bX5sc3EWX6+C80phokZCGtZ7fgf/GWpVrCwLlp6f7k9sGKUWyDvqr9AkE+2L 2eMlR1N521MtZ6Okt5r85Ks1HmkkH4PCAHmcpPOt9Tfa+S9NgQsQiLmY4jAap/jsVhSe mIdS5ZiWf84tjPCx4rEX+7L0cKBjg1wAaFLN6b4+jyRhByq0FHQWDyLO5FqiBYbGh0V/ 7HOIdKGz3cmU9NUSWOrziGYRh32MTxEQ88xD3eIH0PfcqP1naKpHGOZwkf6H9SkXC0cp PzsQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=f+GfAJAA; 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 d7si5078314edx.316.2021.07.05.18.40.48; Mon, 05 Jul 2021 18:41:11 -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=f+GfAJAA; 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 S229733AbhGFBjT (ORCPT + 99 others); Mon, 5 Jul 2021 21:39:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57368 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229880AbhGFBjS (ORCPT ); Mon, 5 Jul 2021 21:39:18 -0400 Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C02FFC061574; Mon, 5 Jul 2021 18:36:40 -0700 (PDT) Received: by mail-il1-x130.google.com with SMTP id i13so18930958ilu.4; Mon, 05 Jul 2021 18:36:40 -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=B582vdrs46kitJpA3JaiMzIr2mncrXCNua47i7ErJFI=; b=f+GfAJAAKpgZuIxD67wH2PCJ1VkbUs8feFPpWpgdRr7htZIKUPG+8rxaSQOJoecrVU 6m4pG8SWFK/Kn/6nX2FtwzENX/6Q4LVwvXVTRSMBM6DtY4lsaGiXqBDRPKwm1ET2R7L1 GFfnOVpuvkdJA8VoqM+CsGbI+eH4mOajiQrWXTetHW6XmUU3EG77PqC263xKXspOKi4M vwuvngSNLXaU+5fC3sEMvi8Nj0AP+6hdGYddVt8TGGDQqxJXQT8SCu3IVCL2xaH/Xxj+ ZZACC0uWXxnDj5q3BHyRQyB4GnCLhMhR9n0UzmXTu4uKyuPuL27oX44UgrQIDem3IRwY V2Zg== 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=B582vdrs46kitJpA3JaiMzIr2mncrXCNua47i7ErJFI=; b=nKFquxsBrzG2cpUJ8Jwwh1c8f4DEmSID0hcrURtrF7Uj6+eD9VCxNvn6RWuphYVHrN I4HQvA7Dz8NMrAQfOUr1nYpQ1DS2+yiuIdqKQB8W8PfIo891QKIk04ty2uxSqQoJ3yWn rrZjB/+vcKUNBohW2yBY2zdz7CZ9BYx+7bgQHQQUFVRUW1PEe0eXYpYWXToFE2Va9Ztl cBVEvuukaqxWq4b7nrmdcGMR4DV50ParDOo6xHrcWfUqsmMCoX4yuD4RqV+diPZfdHDe u/nhAVMVdfgpT5kdRxeLmr7UjEkjFnmqmAUdh8XBsbyQ+doegE1niGunG1VZ/GL3hpDq 3hHw== X-Gm-Message-State: AOAM531tVLTo6glQ7ZlM+B3F++efJFSH93X5GXllt2ifruqS9oMeRDkq Yqr97bwdFg4pkbuvh5yD4mIQEqylXbWg1+99uL0= X-Received: by 2002:a05:6e02:1d12:: with SMTP id i18mr12892359ila.97.1625535400201; Mon, 05 Jul 2021 18:36:40 -0700 (PDT) MIME-Version: 1.0 References: <20210701154634.GA60743@bjorn-Precision-5520> <67a9e1fa.81a9.17a64c8e7f7.Coremail.chenhuacai@loongson.cn> In-Reply-To: From: Huacai Chen Date: Tue, 6 Jul 2021 09:36:28 +0800 Message-ID: Subject: Re: Re: [PATCH 0/4] PCI: replace dublicated MRRS limit quirks To: Art Nikpal 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 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 wh= at 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 prob= lem. > > 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.com,= khilman@baylibre.com, lorenzo.pieralisi@arm.com, robh@kernel.org, kw@linux= .com, jbrunet@baylibre.com, christianshewitt@gmail.com, martin.blumenstingl= @googlemail.com, linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradea= d.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org, art= @khadas.com, nick@khadas.com, gouwa@khadas.com, "Huacai Chen" > > > =E4=B8=BB=E9=A2=98: Re: [PATCH 0/4] PCI: replace dublicated MRRS l= imit 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 from= 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 and = make > > > no changes to the code itself. > > > > > > Amlogic appears without explanation in 2/4. Must be separate patc= h to > > > address only that specific issue. Should reference published erra= tum > > > if possible. "Solves some issue" is not a compelling justificatio= n. > > > > > > The tree must be consistent and functionally the same or improved > > > 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@loon= gson.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@bhelgaas-= glaptop.roam.corp.google.com/ > > > > > > > Both ks_pcie_quirk loongson_mrrs_quirk was rewritten without = any > > > > functionality changes by one mrrs_limit_quirk > > Does that means keystone and Loongson has the same MRRS problem? And wh= at should I do now? > > > > Huacai > > > > > > > > Added DesignWare PCI controller which need same quirk for > > > > * drivers/pci/controller/dwc/pci-meson.c (PCI_DEVICE_ID_SYNOP= SYS_HAPSUSB3) > > > > > > > > This quirk can solve some issue for Khadas VIM3/VIM3L(Amlogic= ) > > > > with HDMI scrambled picture and nvme devices at intensive wri= ting... > > > > > > > > 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 > > > > > > > > > >