From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D0D68C433EF for ; Fri, 4 Feb 2022 16:07:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:References: List-Owner; bh=aDZ0Yu63tmWyg1euftd4YpJN8U/Pv1AJTxIt811uEu0=; b=eB3b/TWCywtdWT Wx1/wdNJSrjhpi7NXSlpp61Kb6TZxIm5Du8ldWzNwefUY/tiR9mynMC5TIBh0J5Hjm6Dtz7FBZJEd e0NycYb0spNDuXyYyGqFhdNZ6ojtRriAMwmQhlAQmonfOEIjlRU2XdQQ/AZbrl/dM4pZ1Ox1xKv85 IxCCBWYTWh+6wfUal18E8LZgerGBeoOYe2Q3yM8bkMmrogw7zZSYSwpzGvMbpWTkYGNk9p+yDbahi Coz1R52FkJI5Zzhy4MvQo9ituZAFyTpRUOXcu8Vp+w6tipX9MdHuI5khSAiuVffboqNArFGDWT4gQ awfptc5saUaRHcfPxCNA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nG16O-004tRC-Qj; Fri, 04 Feb 2022 16:06:24 +0000 Received: from ams.source.kernel.org ([2604:1380:4601:e00::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nG16M-004tQ9-2C for linux-arm-kernel@lists.infradead.org; Fri, 04 Feb 2022 16:06:23 +0000 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 ams.source.kernel.org (Postfix) with ESMTPS id 093DBB837D9; Fri, 4 Feb 2022 16:06:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 98CDBC004E1; Fri, 4 Feb 2022 16:06:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1643990778; bh=AwqDqSxat/pFIu3D+mTbSxknPJqAY3cma8RQiS/TFxA=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=BOiGHvQHl5FbfOGzdxE9R+bMyVdJbkW8ItZb3RvslFXarHGY5u3pgenjNG/FXGICl tfKe5x75vVYbwnXhhO/ySyEXC5fGtrjl5QiE/p5SQUAbFUyHdpIoKneKyEMoZpHJ3P HtYLXQgVemhFSoJoBA2I4A3VZ7oOPC9PrRJUMuVdDEvTYGUFeX1Ed8rdtOt+xiC2V+ 59UbTph+g/4E3JLx3IDrEfeB8uDE7X+9PT9b4FbvY5MkVJFTyIL5tdkSBYvrZoHQVw ZGzb8BWlTF8acCXBLwvbSGJS00DArIME7W50fxSiEcTPA1aTI8PbZ/DgjD25OOMPyX nLIlNvRdQgVow== Date: Fri, 4 Feb 2022 10:06:16 -0600 From: Bjorn Helgaas To: Kunihiko Hayashi Cc: Bjorn Helgaas , Rob Herring , Lorenzo Pieralisi , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Masami Hiramatsu , linux-pci@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/3] PCI: uniphier-ep: Add support for non-legacy SoC Message-ID: <20220204160616.GA183849@bhelgaas> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1643855786-23186-3-git-send-email-hayashi.kunihiko@socionext.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220204_080622_297875_41B77684 X-CRM114-Status: GOOD ( 11.43 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Feb 03, 2022 at 11:36:25AM +0900, Kunihiko Hayashi wrote: > Define SoC data that includes pci_epc_features and boolean 'is_legacy' > to distinguish between legacy SoC (ex. Pro5) and non-legacy SoC. I'm not a big fan of "legacy" as a description because it conveys very little information. You're adding support for a "non-legacy" SoC, so now there are "legacy" ones and "non-legacy" ones. Next year there will be another new SoC, and then there will be *two* kinds of "legacy" ones that must be distinguished plus the next "non-legacy" one. You mentioned "Pro5" as an example of "legacy," which is a good start. Are there any others? If Pro5 is the only one, you could just use "pro5" where you now use "legacy." Bjorn _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel