Received: by 2002:ac0:da4c:0:0:0:0:0 with SMTP id a12csp943488imi; Thu, 21 Jul 2022 14:04:21 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vZntFvEmYxJKZKYtP3SGQVHL1vvW9BmMQ39lQAePCn/4zsisCowqV81Hip2ZF1tYOmlLWV X-Received: by 2002:a17:907:6d99:b0:72f:4633:65 with SMTP id sb25-20020a1709076d9900b0072f46330065mr408661ejc.320.1658437460973; Thu, 21 Jul 2022 14:04:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658437460; cv=none; d=google.com; s=arc-20160816; b=v0opCP/+pl9o4UJbqa14+xniJE2S0dREebO0FraL6oxwK1b7z1P3SNyV7LHrFCJTLl TJ+m+MPUClGnzSB+q+M6LCcW8H3QZEye3o3FTqfikUAbNtQ64Fu+OcZ8daqQnOtnUBe6 Mocxow3FDvDyPl2EXAUju3vZSMS+dB15tZq3+vqn8x42/QMypCz4PSSiGbtptrT9TSvl MuX1htrrUaOARKAMNj61YwJGfC58ZqD/MTaTqLRjH8h43IDpUevS6yBus8V3jw7ywqMA mAIrF/8fbmWW0kqK3FZ8Ou4QlkAuwb6aBVYQ4t/J5oWuKQXUHtU/5H4F+szD2T6Zik/B R3Zg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :message-id:subject:cc:to:from:date:dkim-signature; bh=S/cO1QevdhlI0eRNfLUELt7vkeyRC3sYF7w6KaqYs/o=; b=iLRRYxpPbAVTTDZvNv01ibp9HwGnkqifl/hylG4DZVS/GcAwHXCsm5i6VyphM/r5ir BvfGkXKeAcpKKc83sCx3zTl7ejyBavavU8GBFGPm/E2Ok+AA0f+05RpdDKBWVWtgrKWr K4dfjSsJ6f+OpKozbYGvkom34om6uKJIxKCwBSoI4J/nGyubGkU0eWAyTf6/opCsv1lv /98L3c4OQmi4jgxjKf860F2pJQQHeNKthynUhPjO1Jn4TN9F3aCkcUSdrzwKW9q8joqK DTNQwTzGsJei3Qdjx8D4T0Hc5DZ9xDB52HkvdtaanzbcB+y4Y6o7bfkq6+yZLDkhy5A4 WPXA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=KLeVB7AB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id cr12-20020a170906d54c00b00711dd35ed99si4348593ejc.652.2022.07.21.14.03.55; Thu, 21 Jul 2022 14:04:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=KLeVB7AB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233284AbiGUU62 (ORCPT + 99 others); Thu, 21 Jul 2022 16:58:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48158 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233559AbiGUU6Y (ORCPT ); Thu, 21 Jul 2022 16:58:24 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A30BB904CA; Thu, 21 Jul 2022 13:58:22 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 3F04260AD8; Thu, 21 Jul 2022 20:58:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 71230C3411E; Thu, 21 Jul 2022 20:58:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1658437101; bh=H/aHhtlRLOeWCCQ5QG+qxA0GsTmdnIKgv+5n5V0Q6n8=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=KLeVB7ABm4ecgcmx0viupligXKNnNx1xb7evo72pn3Zlb4f9eDbW8miXjfzrZzyoE FRiZz2NHq5lMMXydznLM7Q7iz+GaZAz8bIarL8okiQT673X1g0Wj/itVgSQrKUVjZS Ww/Sd1cwfSQuLKvqe4oz5WZuRpcOyiOkRbRtp1aFR12hbBzDAvbGF6iN+4IAuJ0P18 xxyjw3TAuOlcTEOauJkLKoUVcL/AB3FBE6OCKZImLVtRjPmYzO6C64O4WgFgwzwgF6 daVATJG/L3yJWqYc4RcpjVzTk//ao+3Vun3a2HC7TXVVW/OAiSwydS/vidV7KXF892 ZUFONRMtOpNLg== Date: Thu, 21 Jul 2022 15:58:19 -0500 From: Bjorn Helgaas To: Krzysztof Kozlowski Cc: wangseok.lee@samsung.com, "robh+dt@kernel.org" , "krzk+dt@kernel.org" , "kishon@ti.com" , "vkoul@kernel.org" , "linux-kernel@vger.kernel.org" , "jesper.nilsson@axis.com" , "lars.persson@axis.com" , "bhelgaas@google.com" , "linux-phy@lists.infradead.org" , "linux-pci@vger.kernel.org" , "devicetree@vger.kernel.org" , "lorenzo.pieralisi@arm.com" , "kw@linux.com" , "linux-arm-kernel@axis.com" , "kernel@axis.com" , Moon-Ki Jun , Sang Min Kim , Dongjin Yang , Yeeun Kim Subject: Re: [PATCH v4 3/5] PCI: axis: Add ARTPEC-8 PCIe controller driver Message-ID: <20220721205819.GA1753070@bhelgaas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <226ac31e-2ac4-cb73-ab67-62f86d5e5783@linaro.org> X-Spam-Status: No, score=-7.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 21, 2022 at 11:04:00AM +0200, Krzysztof Kozlowski wrote: > On 20/07/2022 08:01, Wangseok Lee wrote: > > Add support Axis, ARTPEC-8 SoC. ARTPEC-8 is the SoC platform of Axis > > Communications. This is based on arm64 and support GEN4 & 2lane. This > > PCIe controller is based on DesignWare Hardware core and uses DesignWare > > core functions to implement the driver. "pcie-artpec6. c" supports artpec6 > > and artpec7 H/W. artpec8 can not be expanded because H/W configuration is > > completely different from artpec6/7. PHY and sub controller are different. > > > > Signed-off-by: Wangseok Lee > > Signed-off-by: Jaeho Cho > > --- > > v3->v4 : > > -Remove unnecessary enum type > > -Fix indentation > > > > Thanks for the changes. This starts to look good, however I am not going > to ack it. This is also not a strong NAK, as I would respect Bjorn and > other maintainers decision. > > I don't like the approach of creating only Artpec-8 specific driver. > Samsung heavily reuses its block in all Exynos devices. Now it re-uses > them for other designs as well. Therefore, even if merging with existing > Exynos PCIe driver is not feasible (we had such discussions), I expect > this to cover all Samsung Foundry PCIe devices. From all current designs > up to future licensed blocks, including some new Samsung Exynos SoC. Or > at least be ready for it. I would certainly prefer fewer drivers but I don't know enough about the underlying IP and the places it's integrated to to know what's practical. The only way I could figure that out would be by manually comparing the drivers for similarity. I assume/expect all driver authors are doing that. Bjorn