Received: by 2002:ac0:aa62:0:0:0:0:0 with SMTP id w31-v6csp423862ima; Fri, 26 Oct 2018 00:02:24 -0700 (PDT) X-Google-Smtp-Source: AJdET5eGIlW9sK2cF+Hy/4HwblQqH97KK9Rtb40X+sgK4o0wqhsvmzoZ6wpHEDbEodFjWpbU0Qha X-Received: by 2002:a17:902:a503:: with SMTP id s3-v6mr2344946plq.35.1540537344755; Fri, 26 Oct 2018 00:02:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540537344; cv=none; d=google.com; s=arc-20160816; b=UJo26C9HZuo1bK3O/tLboZAOHS2k6cEXbYKcis9BOlC0ZJRsZKInQovqI/6lZg2fXK XhTNUZ8PJ7g5cUDIOY3cJ1Y1k5S4/ufPk0MDQsWHa3pwhTcMDy1NaW/rlDYfBa51K0Ex o3bolua5WyBX4XWh4QrDhGW5KhGzfUDfwajhZWhv4kR2Z7RevrhGiOkXEHf2mL6HfBEV 4lapZAIdG96OJxDzBRdySUTIO/hAuvxGvqKXtzUgNQytDxtPNCJzFNNOAQ5aDhMNxZER lJXHltJL45dUnJEjgmI7cTv+UEmkAdWbBxRjWZapYXWIzBSRxauH3P6N4UZ2HP72CqkG OkgQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature; bh=ygtCwwNpN9rX8xntHSLNe3Y94i+g9J6A4JU6Fak5aok=; b=j/9JOpATG6Lb3qMXixyfmhxVXCK/SGZt5YLi2qBh+t1ERCrbSkqcsd/ZPI5a0R7wRD Jmz3dfHEj26UDOgwxdFISR7fZev6N5qDa4YlqnbO9ftYZ+pWoUnJeBY1D5CxGUK695F3 otwMzthJ33NNIicli83RNSwTjv/fS/OwIi2PWKsbE6O1xhyOP1WNpS/Xx4PgqNKAylUV 0rQox9MzMm8BrWP1pGxIv/2pJuwRMUcInQMx3OzPUhlgApgpQOLiABKx6OIJGlN217vT EJwDJ7v2BT7E5LdyRjposb5iyi3imoOZGk639V1O57woZBeryOLELGUez7l8MaGhrsDO YA2Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=Ew9UJZX+; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o13-v6si11022445pgm.513.2018.10.26.00.01.54; Fri, 26 Oct 2018 00:02:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=Ew9UJZX+; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726078AbeJZPhH (ORCPT + 99 others); Fri, 26 Oct 2018 11:37:07 -0400 Received: from mail-qk1-f193.google.com ([209.85.222.193]:40919 "EHLO mail-qk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725876AbeJZPhH (ORCPT ); Fri, 26 Oct 2018 11:37:07 -0400 Received: by mail-qk1-f193.google.com with SMTP id f18-v6so64195qkm.7; Fri, 26 Oct 2018 00:01:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ygtCwwNpN9rX8xntHSLNe3Y94i+g9J6A4JU6Fak5aok=; b=Ew9UJZX+o7hzahXLJ/Qxd829ksNmWDMrBzMXCfWaW1qOgxP2HDNsJMH9ok+FMthYBz AtQtOscM4B4nymGyfUVa/uhTM7C488pdrptULDJuqLh1LUXrk2zsq/7Xn1SzrNbWF5eO xbL5GAmV/kJOWghSVRMWwLld3E7pcjIoQ8WCXxsTYNYGFzpwZIkxJJybjAn0vvtT3kav BwmX3h+Pi89O5q2jTEY/bA04IC5+n8hyhn9YgCm3jurn9O908EGhfTRcpaUeK0EqwhZZ cKk2GPPHmddvDtE8eFotr59fZqXdSw7OuuPWFeuMKqD9jkDr0TzBtL+B3uazWvwdcyJg L0og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ygtCwwNpN9rX8xntHSLNe3Y94i+g9J6A4JU6Fak5aok=; b=P3eN7XkD+oa/md4ocVFDjNMtr7kD9NQgo3gozBSuuSNMkzyZoz8gRsvSaW13VkTNzm F48dWLB+iwv9Mub72Qn6jnD2wxktgtQ+6sa17MaYCqLHhGvMwEUdR7Sma2FNS/M/BUo0 Cs0AFUjZe93sY3pvCCE+ab73iQ60XOosFXylA8YdSjDtyll/OzzqY144Z8YBOmmNuK8N 8CNGrZfhaDqpRJWhwXGTrdpeMOZO9tAE8l4uDIS77qab9rQiKt3DMVPKYQbVlB7QRfHP VvgP7uBWXIQS8wbLHTurz/r3mvfryeguI4F48TLV13yNuKr71xyYe7H+UvXW1H+2HjKS nqFA== X-Gm-Message-State: AGRZ1gI8BmDxwYAAXnNUFAj0aZeXTMVX9RcEmK0pGBi+tkkUdwWKHD9f K9aOcezawTkM1blkxcLialHi5UwybEKZfBmM1s4= X-Received: by 2002:a37:4116:: with SMTP id o22-v6mr1907286qka.107.1540537279997; Fri, 26 Oct 2018 00:01:19 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a0c:988d:0:0:0:0:0 with HTTP; Fri, 26 Oct 2018 00:01:19 -0700 (PDT) In-Reply-To: References: <20181025110901.5680-1-xiaowei.bao@nxp.com> <20181025110901.5680-3-xiaowei.bao@nxp.com> <20181025215246.GA14861@bogus> From: Arnd Bergmann Date: Fri, 26 Oct 2018 09:01:19 +0200 X-Google-Sender-Auth: 13NSssZsIICiZBH18QZjyKXH8-I Message-ID: Subject: Re: [PATCH 3/6] PCI: layerscape: Add the EP mode support To: Xiaowei Bao Cc: Rob Herring , "bhelgaas@google.com" , "mark.rutland@arm.com" , "shawnguo@kernel.org" , Leo Li , "kishon@ti.com" , "lorenzo.pieralisi@arm.com" , "gregkh@linuxfoundation.org" , "M.h. Lian" , Mingkai Hu , Roy Zang , "kstewart@linuxfoundation.org" , "cyrille.pitchen@free-electrons.com" , "pombredanne@nexb.com" , "shawn.lin@rock-chips.com" , "niklas.cassel@axis.com" , "linux-pci@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linuxppc-dev@lists.ozlabs.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/26/18, Xiaowei Bao wrote: > From: Rob Herring >> On Thu, Oct 25, 2018 at 07:08:58PM +0800, Xiaowei Bao wrote: >>> "fsl,ls2080a-pcie", "fsl,ls2085a-pcie", "snps,dw-pcie" >>> "fsl,ls2088a-pcie" >>> "fsl,ls1088a-pcie" >>> "fsl,ls1046a-pcie" >>> "fsl,ls1012a-pcie" >>> + EP mode: >>> + "fsl,ls-pcie-ep" >> > > You need SoC specific compatibles for the same reasons as the RC. > > [Xiaowei Bao] I want to contains all layerscape platform use one compatible > if the PCIe controller work in EP mode. Do you mean only one of the SoCs that support RC mode has EP mode? I think you still need a SoC specific compatible as Rob explained, in case there will be a second one in the future. If you want to ensure that you don't have to update the device driver for each new chip that comes in when the EP mode is compatible, the way this is handled is to list multiple values in the compatible property, listing the first SoC that introduced the specific version of that IP block as the most generic type, e.g. copatible = "fsl,ls2088a-pcie-ep", "fsl,ls1012a-pcie-ep", "snps,dw-pcie-ep"; For consistency, it probably is best to match each RC mode value with the corresponding EP mode string for each device that can support both (if there is more than one). Arnd