Message ID | 20240221195058.1281973-3-charles.perry@savoirfairelinux.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel+bounces-75433-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:693c:2685:b0:108:e6aa:91d0 with SMTP id mn5csp1279215dyc; Wed, 21 Feb 2024 12:26:40 -0800 (PST) X-Forwarded-Encrypted: i=3; AJvYcCVKjYkVdS34ht6Ml8UX2lCz91Qo5hR9w+LNkYnUeRwDxJV0T8o8Fnl56P2qJhLsvkPtY7+B196WgvLFnK2zwmkyX6j9oQ== X-Google-Smtp-Source: AGHT+IGILH1l6imSsbVkhrGDtl+30L2FhoYGjTc0QWZZo60Fc0uRWR5t874ZqbvLoSd25UjFCiXm X-Received: by 2002:a17:90a:bd8e:b0:299:10a9:bbb with SMTP id z14-20020a17090abd8e00b0029910a90bbbmr13311603pjr.9.1708547199837; Wed, 21 Feb 2024 12:26:39 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1708547199; cv=pass; d=google.com; s=arc-20160816; b=YjxjLmRLeVIjIUqg3h+O/88yI3qr+9P1kZwD8XP1u+RYxcRE81P89YrH8/qPN7UH0R bFQXPTVfu9ROdm23CTae9z9K+HSdfrkBm+YaJ6dxatBLZFWqX9BtB178waZhCPK+oS6h agpUPXvJgBhiEbPoSPqGh1633MctH5MiqxHPiTWG/U9kHnRj3QWOD1+Kzx4DKih3tq+9 nTEzX88heyL5+tlU0pR6T91qh1BVB0X3uhblFmy8BFiprtNKiKLd2mlVHh8jt/DqfGAo CZ3EPOfh0MZjaxFIaVmKqLT7Ge2IyrHrMLKkYYzkAoEsFUA23YExAjSUJLuWuoWA2406 2UnA== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature:dkim-filter; bh=V0AloincpFNxqN8jxOVAcKyVY2ydGA1teB3GeWFAsDs=; fh=X4QAQfkJoHBoTjypDfqSMHAFutuwOQvRiEbCzpU4yFA=; b=lWKyFWrGiCOlLh3OYaxR5BG52o3nuleHiD8p5foxQxGwb2Czz3QURMe2kE0RqKdMS1 bz28tn3DxuHFBJTXJdU9ZWXMDengJmm+9R3pZPOpR65As9Up2eCuuPTTJnDWJU6nMdoO QIGun4ap9x9lwulnf3dKGzCdyPj/32v0ChlOZEbSvR2FbFHGw23+7xCZGSXwl0CuYpvd DV3MFoM2kd8sbKkwZMt6m8gr+o5R1je0y3WvQJVVA4vq+z7Thl6FSoWkqL4hkOFc8nB8 ja2PokWcKPvyMGcG6/ZusVeBNyPl3lchum051syxMJddXni1bvmYInP5VAU/PefRrhCi aNSg==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@savoirfairelinux.com header.s=DFC430D2-D198-11EC-948E-34200CB392D2 header.b="v/ihWQHy"; arc=pass (i=1 spf=pass spfdomain=savoirfairelinux.com dkim=pass dkdomain=savoirfairelinux.com); spf=pass (google.com: domain of linux-kernel+bounces-75433-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-75433-ouuuleilei=gmail.com@vger.kernel.org" Received: from sy.mirrors.kernel.org (sy.mirrors.kernel.org. [2604:1380:40f1:3f00::1]) by mx.google.com with ESMTPS id p5-20020a17090a868500b002935f38dcf1si2091917pjn.181.2024.02.21.12.26.39 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 Feb 2024 12:26:39 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-75433-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1; Authentication-Results: mx.google.com; dkim=pass header.i=@savoirfairelinux.com header.s=DFC430D2-D198-11EC-948E-34200CB392D2 header.b="v/ihWQHy"; arc=pass (i=1 spf=pass spfdomain=savoirfairelinux.com dkim=pass dkdomain=savoirfairelinux.com); spf=pass (google.com: domain of linux-kernel+bounces-75433-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-75433-ouuuleilei=gmail.com@vger.kernel.org" Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sy.mirrors.kernel.org (Postfix) with ESMTPS id A9D4DB241F8 for <ouuuleilei@gmail.com>; Wed, 21 Feb 2024 20:01:24 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 5EC001353FD; Wed, 21 Feb 2024 19:52:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=savoirfairelinux.com header.i=@savoirfairelinux.com header.b="v/ihWQHy" Received: from mail.savoirfairelinux.com (mail.savoirfairelinux.com [208.88.110.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BE108134723; Wed, 21 Feb 2024 19:52:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=208.88.110.44 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708545138; cv=none; b=XA28kC/44cuTzNHYnM9oNeEJU18rZR7ejPiBXgRdMLruULvyXtdRloDzGWnzuPsZ8aBYxetwTF2XjXPrLqBCiCZXpoRnKeIh8KwfnCQsbS6ZeBiCvOUqk7zczRR1TMzqHgSbPmvSapbyERKglj0O5o9dYaGN1s+rlQPiSYZevTA= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708545138; c=relaxed/simple; bh=LlqHcE0YwJZlGexpmnxq7XZsurHwrFWJoYOL08Ka9UE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=k3aaZMzf50nQtHvuyQjZGYFlY2q85tM+S5CTLaDM2BLV3eTpRRlDhEbftn3E/bF+3sGsGO6WkODqeD5StMJFRh5HRXPVFgWqHOC/sva2x/SOBrllSYYvi5bKSu+FWG7zAuiHSHdikKUBm2OliIYY0HzZoTaqU6jITMxTS1NvZ+Q= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=savoirfairelinux.com; spf=pass smtp.mailfrom=savoirfairelinux.com; dkim=pass (2048-bit key) header.d=savoirfairelinux.com header.i=@savoirfairelinux.com header.b=v/ihWQHy; arc=none smtp.client-ip=208.88.110.44 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=savoirfairelinux.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=savoirfairelinux.com Received: from localhost (localhost [127.0.0.1]) by mail.savoirfairelinux.com (Postfix) with ESMTP id 5CF1D9C4B59; Wed, 21 Feb 2024 14:52:10 -0500 (EST) Received: from mail.savoirfairelinux.com ([127.0.0.1]) by localhost (mail.savoirfairelinux.com [127.0.0.1]) (amavis, port 10032) with ESMTP id 1HRkwdxDnQeV; Wed, 21 Feb 2024 14:52:09 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.savoirfairelinux.com (Postfix) with ESMTP id 74C559C4BEA; Wed, 21 Feb 2024 14:52:09 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.savoirfairelinux.com 74C559C4BEA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=savoirfairelinux.com; s=DFC430D2-D198-11EC-948E-34200CB392D2; t=1708545129; bh=V0AloincpFNxqN8jxOVAcKyVY2ydGA1teB3GeWFAsDs=; h=From:To:Date:Message-ID:MIME-Version; b=v/ihWQHyJwFqRDMtxygel1LYabD9lGZMscCI8GwNTwWtL5RAixkb9KbDSUombzccV y299zfvVl9+wzPZJqYT3UUQdSKyz/Zdb6zm0S7xpb3DcTwW/3nYfCrrQ7eKMITj1wc DkA1seyufzumAlMEsh/A4X3DLUulQcxKMnyRueri/CB4vh2ohgtmk15gK217pz5UoW oIEDjjSN1YWqS90abXGCeksd7HWxTlJfE2k8C6JG4kTXLVCYB5FAz/bKg5Dtui1fGX Hut0BZ26g4q7NrXBEW2OV9C+2fHYqIIzafcayiw6umLcLBqHdHmXkyB/bEeB4lunNd l7+8fHW18nCMg== X-Virus-Scanned: amavis at mail.savoirfairelinux.com Received: from mail.savoirfairelinux.com ([127.0.0.1]) by localhost (mail.savoirfairelinux.com [127.0.0.1]) (amavis, port 10026) with ESMTP id inHxOnZgcdKg; Wed, 21 Feb 2024 14:52:09 -0500 (EST) Received: from pcperry.mtl.sfl (unknown [192.168.51.254]) by mail.savoirfairelinux.com (Postfix) with ESMTPSA id 503609C4B59; Wed, 21 Feb 2024 14:52:09 -0500 (EST) From: Charles Perry <charles.perry@savoirfairelinux.com> To: mdf@kernel.org Cc: avandiver@markem-imaje.com, bcody@markem-imaje.com, Charles Perry <charles.perry@savoirfairelinux.com>, Wu Hao <hao.wu@intel.com>, Xu Yilun <yilun.xu@intel.com>, Tom Rix <trix@redhat.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Michal Simek <michal.simek@amd.com>, linux-fpga@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH v4 2/3] dt-bindings: fpga: xlnx,fpga-selectmap: add DT schema Date: Wed, 21 Feb 2024 14:50:48 -0500 Message-ID: <20240221195058.1281973-3-charles.perry@savoirfairelinux.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240221195058.1281973-1-charles.perry@savoirfairelinux.com> References: <20240221195058.1281973-1-charles.perry@savoirfairelinux.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1791541588275568543 X-GMAIL-MSGID: 1791541588275568543 |
Series |
fpga: xilinx-selectmap: add new driver
|
|
Commit Message
Charles Perry
Feb. 21, 2024, 7:50 p.m. UTC
Document the SelectMAP interface of Xilinx 7 series FPGA.
Signed-off-by: Charles Perry <charles.perry@savoirfairelinux.com>
---
.../bindings/fpga/xlnx,fpga-selectmap.yaml | 86 +++++++++++++++++++
1 file changed, 86 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml
Comments
On 21/02/2024 20:50, Charles Perry wrote: > Document the SelectMAP interface of Xilinx 7 series FPGA. > > Signed-off-by: Charles Perry <charles.perry@savoirfairelinux.com> > --- > .../bindings/fpga/xlnx,fpga-selectmap.yaml | 86 +++++++++++++++++++ > 1 file changed, 86 insertions(+) > create mode 100644 Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml > > diff --git a/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml b/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml > new file mode 100644 > index 0000000000000..08a5e92781657 > --- /dev/null > +++ b/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml > @@ -0,0 +1,86 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/fpga/xlnx,fpga-selectmap.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Xilinx SelectMAP FPGA interface > + > +maintainers: > + - Charles Perry <charles.perry@savoirfairelinux.com> > + > +description: | > + Xilinx 7 Series FPGAs support a method of loading the bitstream over a > + parallel port named the SelectMAP interface in the documentation. Only > + the x8 mode is supported where data is loaded at one byte per rising edge of > + the clock, with the MSB of each byte presented to the D0 pin. > + > + Datasheets: > + https://www.xilinx.com/support/documentation/user_guides/ug470_7Series_Config.pdf > + > +allOf: > + - $ref: /schemas/memory-controllers/mc-peripheral-props.yaml# > + > +properties: > + compatible: > + enum: > + - xlnx,fpga-xc7s-selectmap > + - xlnx,fpga-xc7a-selectmap > + - xlnx,fpga-xc7k-selectmap > + - xlnx,fpga-xc7v-selectmap > + > + reg: > + description: > + At least 1 byte of memory mapped IO > + maxItems: 1 > + > + prog_b-gpios: I commented on this and still see underscore. Nothing in commit msg explains why this should have underscore. Changelog is also vague - describes that you brought back underscores, instead of explaining why you did it. So the same comments as usual: No underscores in names. Best regards, Krzysztof
On Feb 27, 2024, at 3:10 AM, Krzysztof Kozlowski krzysztof.kozlowski@linaro.org wrote: > On 21/02/2024 20:50, Charles Perry wrote: >> Document the SelectMAP interface of Xilinx 7 series FPGA. >> >> Signed-off-by: Charles Perry <charles.perry@savoirfairelinux.com> >> --- >> .../bindings/fpga/xlnx,fpga-selectmap.yaml | 86 +++++++++++++++++++ >> 1 file changed, 86 insertions(+) >> create mode 100644 >> Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >> >> diff --git a/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >> b/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >> new file mode 100644 >> index 0000000000000..08a5e92781657 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >> @@ -0,0 +1,86 @@ >> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) >> +%YAML 1.2 >> +--- >> +$id: http://devicetree.org/schemas/fpga/xlnx,fpga-selectmap.yaml# >> +$schema: http://devicetree.org/meta-schemas/core.yaml# >> + >> +title: Xilinx SelectMAP FPGA interface >> + >> +maintainers: >> + - Charles Perry <charles.perry@savoirfairelinux.com> >> + >> +description: | >> + Xilinx 7 Series FPGAs support a method of loading the bitstream over a >> + parallel port named the SelectMAP interface in the documentation. Only >> + the x8 mode is supported where data is loaded at one byte per rising edge of >> + the clock, with the MSB of each byte presented to the D0 pin. >> + >> + Datasheets: >> + >> https://www.xilinx.com/support/documentation/user_guides/ug470_7Series_Config.pdf >> + >> +allOf: >> + - $ref: /schemas/memory-controllers/mc-peripheral-props.yaml# >> + >> +properties: >> + compatible: >> + enum: >> + - xlnx,fpga-xc7s-selectmap >> + - xlnx,fpga-xc7a-selectmap >> + - xlnx,fpga-xc7k-selectmap >> + - xlnx,fpga-xc7v-selectmap >> + >> + reg: >> + description: >> + At least 1 byte of memory mapped IO >> + maxItems: 1 >> + >> + prog_b-gpios: > > I commented on this and still see underscore. Nothing in commit msg > explains why this should have underscore. Changelog is also vague - > describes that you brought back underscores, instead of explaining why > you did it. > > So the same comments as usual: > > No underscores in names. > > Best regards, > Krzysztof Hello Krzysztof, Yes, I've gone full circle on that issue. Here's what I tried so far: 1) Reuse the same gpio names: Duplicates errors of the past, Krzysztof doesn't like it. 2) Different gpio names for new driver only: Makes the driver code overly complicated, Yilun doesn't like it. 3) Change gpio names for both drivers, deprecate the old names: Makes the DT binding and the driver code overly complicated, Rob doesn't like it. I think that while the driver code shouldn't be the driving force for the DT spec, it can be a good indication that the spec is unpractical to implement. In this case, there are two interfaces on a chip that uses the same GPIO protocol, it would only make sense that they use the same names, this discards solution #2. That leaves us with #1 or #3, which is to ask if the added complexity to the driver code and DT binding is worth it for a gain in naming convention. There might also be another solution that I haven't seen. Regards, Charles
On 03/03/2024 18:21, Charles Perry wrote: > On Feb 27, 2024, at 3:10 AM, Krzysztof Kozlowski krzysztof.kozlowski@linaro.org wrote: > >> On 21/02/2024 20:50, Charles Perry wrote: >>> Document the SelectMAP interface of Xilinx 7 series FPGA. >>> >>> Signed-off-by: Charles Perry <charles.perry@savoirfairelinux.com> >>> --- >>> .../bindings/fpga/xlnx,fpga-selectmap.yaml | 86 +++++++++++++++++++ >>> 1 file changed, 86 insertions(+) >>> create mode 100644 >>> Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >>> >>> diff --git a/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >>> b/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >>> new file mode 100644 >>> index 0000000000000..08a5e92781657 >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >>> @@ -0,0 +1,86 @@ >>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) >>> +%YAML 1.2 >>> +--- >>> +$id: http://devicetree.org/schemas/fpga/xlnx,fpga-selectmap.yaml# >>> +$schema: http://devicetree.org/meta-schemas/core.yaml# >>> + >>> +title: Xilinx SelectMAP FPGA interface >>> + >>> +maintainers: >>> + - Charles Perry <charles.perry@savoirfairelinux.com> >>> + >>> +description: | >>> + Xilinx 7 Series FPGAs support a method of loading the bitstream over a >>> + parallel port named the SelectMAP interface in the documentation. Only >>> + the x8 mode is supported where data is loaded at one byte per rising edge of >>> + the clock, with the MSB of each byte presented to the D0 pin. >>> + >>> + Datasheets: >>> + >>> https://www.xilinx.com/support/documentation/user_guides/ug470_7Series_Config.pdf >>> + >>> +allOf: >>> + - $ref: /schemas/memory-controllers/mc-peripheral-props.yaml# >>> + >>> +properties: >>> + compatible: >>> + enum: >>> + - xlnx,fpga-xc7s-selectmap >>> + - xlnx,fpga-xc7a-selectmap >>> + - xlnx,fpga-xc7k-selectmap >>> + - xlnx,fpga-xc7v-selectmap >>> + >>> + reg: >>> + description: >>> + At least 1 byte of memory mapped IO >>> + maxItems: 1 >>> + >>> + prog_b-gpios: >> >> I commented on this and still see underscore. Nothing in commit msg >> explains why this should have underscore. Changelog is also vague - >> describes that you brought back underscores, instead of explaining why >> you did it. >> >> So the same comments as usual: >> >> No underscores in names. >> >> Best regards, >> Krzysztof > > Hello Krzysztof, > > Yes, I've gone full circle on that issue. Here's what I tried so far: And what part of the commit description allows me to understand this? > > 1) Reuse the same gpio names: Duplicates errors of the past, Krzysztof > doesn't like it. > 2) Different gpio names for new driver only: Makes the driver code > overly complicated, Yilun doesn't like it. That's a new driver, right? So what is complicated here? You have new code and you take prog-b or prog_b? > 3) Change gpio names for both drivers, deprecate the old names: Makes > the DT binding and the driver code overly complicated, Rob doesn't > like it. I don't think I proposed changing existing bindings. > > I think that while the driver code shouldn't be the driving force for > the DT spec, it can be a good indication that the spec is unpractical to > implement. What is impractical in implementing this? You just pass either A or B to function requesting GPIO. Just choose proper name. > > In this case, there are two interfaces on a chip that uses the same GPIO > protocol, it would only make sense that they use the same names, this > discards solution #2. I don't understand this. You have devm_gpiod_get() in your new code. Why is it difficult to use different name? Best regards, Krzysztof
On 04/03/2024 08:30, Krzysztof Kozlowski wrote: > On 03/03/2024 18:21, Charles Perry wrote: >> On Feb 27, 2024, at 3:10 AM, Krzysztof Kozlowski krzysztof.kozlowski@linaro.org wrote: >> >>> On 21/02/2024 20:50, Charles Perry wrote: >>>> Document the SelectMAP interface of Xilinx 7 series FPGA. >>>> >>>> Signed-off-by: Charles Perry <charles.perry@savoirfairelinux.com> >>>> --- >>>> .../bindings/fpga/xlnx,fpga-selectmap.yaml | 86 +++++++++++++++++++ >>>> 1 file changed, 86 insertions(+) >>>> create mode 100644 >>>> Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >>>> >>>> diff --git a/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >>>> b/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >>>> new file mode 100644 >>>> index 0000000000000..08a5e92781657 >>>> --- /dev/null >>>> +++ b/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml >>>> @@ -0,0 +1,86 @@ >>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) >>>> +%YAML 1.2 >>>> +--- >>>> +$id: http://devicetree.org/schemas/fpga/xlnx,fpga-selectmap.yaml# >>>> +$schema: http://devicetree.org/meta-schemas/core.yaml# >>>> + >>>> +title: Xilinx SelectMAP FPGA interface >>>> + >>>> +maintainers: >>>> + - Charles Perry <charles.perry@savoirfairelinux.com> >>>> + >>>> +description: | >>>> + Xilinx 7 Series FPGAs support a method of loading the bitstream over a >>>> + parallel port named the SelectMAP interface in the documentation. Only >>>> + the x8 mode is supported where data is loaded at one byte per rising edge of >>>> + the clock, with the MSB of each byte presented to the D0 pin. >>>> + >>>> + Datasheets: >>>> + >>>> https://www.xilinx.com/support/documentation/user_guides/ug470_7Series_Config.pdf >>>> + >>>> +allOf: >>>> + - $ref: /schemas/memory-controllers/mc-peripheral-props.yaml# >>>> + >>>> +properties: >>>> + compatible: >>>> + enum: >>>> + - xlnx,fpga-xc7s-selectmap >>>> + - xlnx,fpga-xc7a-selectmap >>>> + - xlnx,fpga-xc7k-selectmap >>>> + - xlnx,fpga-xc7v-selectmap >>>> + >>>> + reg: >>>> + description: >>>> + At least 1 byte of memory mapped IO >>>> + maxItems: 1 >>>> + >>>> + prog_b-gpios: >>> >>> I commented on this and still see underscore. Nothing in commit msg >>> explains why this should have underscore. Changelog is also vague - >>> describes that you brought back underscores, instead of explaining why >>> you did it. >>> >>> So the same comments as usual: >>> >>> No underscores in names. >>> >>> Best regards, >>> Krzysztof >> >> Hello Krzysztof, >> >> Yes, I've gone full circle on that issue. Here's what I tried so far: > > And what part of the commit description allows me to understand this? > >> >> 1) Reuse the same gpio names: Duplicates errors of the past, Krzysztof >> doesn't like it. >> 2) Different gpio names for new driver only: Makes the driver code >> overly complicated, Yilun doesn't like it. > > That's a new driver, right? So what is complicated here? You have new > code and you take prog-b or prog_b? > >> 3) Change gpio names for both drivers, deprecate the old names: Makes >> the DT binding and the driver code overly complicated, Rob doesn't >> like it. > > I don't think I proposed changing existing bindings. > >> >> I think that while the driver code shouldn't be the driving force for >> the DT spec, it can be a good indication that the spec is unpractical to >> implement. > > What is impractical in implementing this? You just pass either A or B to > function requesting GPIO. Just choose proper name. > >> >> In this case, there are two interfaces on a chip that uses the same GPIO >> protocol, it would only make sense that they use the same names, this >> discards solution #2. > > I don't understand this. You have devm_gpiod_get() in your new code. Why > is it difficult to use different name? And I forgot to emphasize: none of these is mentioned in commit msg, so for v5 you will get exactly the same complains. And for every other patch which repeats the same and does not clarify caveats or exceptions. Best regards, Krzysztof
diff --git a/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml b/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml new file mode 100644 index 0000000000000..08a5e92781657 --- /dev/null +++ b/Documentation/devicetree/bindings/fpga/xlnx,fpga-selectmap.yaml @@ -0,0 +1,86 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/fpga/xlnx,fpga-selectmap.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Xilinx SelectMAP FPGA interface + +maintainers: + - Charles Perry <charles.perry@savoirfairelinux.com> + +description: | + Xilinx 7 Series FPGAs support a method of loading the bitstream over a + parallel port named the SelectMAP interface in the documentation. Only + the x8 mode is supported where data is loaded at one byte per rising edge of + the clock, with the MSB of each byte presented to the D0 pin. + + Datasheets: + https://www.xilinx.com/support/documentation/user_guides/ug470_7Series_Config.pdf + +allOf: + - $ref: /schemas/memory-controllers/mc-peripheral-props.yaml# + +properties: + compatible: + enum: + - xlnx,fpga-xc7s-selectmap + - xlnx,fpga-xc7a-selectmap + - xlnx,fpga-xc7k-selectmap + - xlnx,fpga-xc7v-selectmap + + reg: + description: + At least 1 byte of memory mapped IO + maxItems: 1 + + prog_b-gpios: + description: + config pin (referred to as PROGRAM_B in the manual) + maxItems: 1 + + done-gpios: + description: + config status pin (referred to as DONE in the manual) + maxItems: 1 + + init-b-gpios: + description: + initialization status and configuration error pin + (referred to as INIT_B in the manual) + maxItems: 1 + + csi-gpios: + description: + chip select pin (referred to as CSI_B in the manual) + Optional gpio for if the bus controller does not provide a chip select. + maxItems: 1 + + rdwr-gpios: + description: + read/write select pin (referred to as RDWR_B in the manual) + Optional gpio for if the bus controller does not provide this pin. + maxItems: 1 + +required: + - compatible + - reg + - prog_b-gpios + - done-gpios + - init-b-gpios + +unevaluatedProperties: false + +examples: + - | + #include <dt-bindings/gpio/gpio.h> + fpga-mgr@8000000 { + compatible = "xlnx,fpga-xc7s-selectmap"; + reg = <0x8000000 0x4>; + prog_b-gpios = <&gpio5 5 GPIO_ACTIVE_LOW>; + init-b-gpios = <&gpio5 8 GPIO_ACTIVE_LOW>; + done-gpios = <&gpio2 30 GPIO_ACTIVE_HIGH>; + csi-gpios = <&gpio3 19 GPIO_ACTIVE_LOW>; + rdwr-gpios = <&gpio3 10 GPIO_ACTIVE_LOW>; + }; +...