From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Charles Perry <charles.perry@savoirfairelinux.com>
Cc: mdf@kernel.org, hao wu <hao.wu@intel.com>,
yilun xu <yilun.xu@intel.com>,
trix@redhat.com,
krzysztof kozlowski+dt <krzysztof.kozlowski+dt@linaro.org>,
Brian CODY <bcody@markem-imaje.com>,
Allen VANDIVER <avandiver@markem-imaje.com>,
linux-fpga@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: fpga: xlnx,fpga-slave-selectmap: add DT schema
Date: Tue, 30 Jan 2024 17:05:06 +0100 [thread overview]
Message-ID: <32669bc7-90b5-48d9-8845-2e072a477c6e@linaro.org> (raw)
In-Reply-To: <1489222458.382780.1706629544559.JavaMail.zimbra@savoirfairelinux.com>
On 30/01/2024 16:45, Charles Perry wrote:
>
>>> +
>>> + reg:
>>> + description:
>>> + At least 1 byte of memory mapped IO
>>> + maxItems: 1
>>> +
>>> + prog_b-gpios:
>>
>>
>> No underscores in names.
>>
>
> This is heavily based on "xlnx,fpga-slave-serial.yaml" which uses an underscore.
> I can use a dash instead but that would make things inconsistent across the two schemas.
Inconsistency is not a problem. Duplicating technical debt is.
>
>>
>>> + 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:
>>
>> Is there init-a? Open other bindings and look how these are called there.
>>
>
> No, the "-b" is there to denote that the signal is active low. I think its shorthand
> for "bar" which is the overline (‾) that electronic engineer put on top of the name of the
> signal on schematics. It comes from the datasheet.
Then just "init-gpios"
...
>>> +required:
>>> + - compatible
>>> + - reg
>>> + - prog_b-gpios
>>> + - done-gpios
>>> + - init-b-gpios
>>> +
>>> +additionalProperties: true
>>
>> Nope, this cannot bue true.
>>
>
> Ok, I'll put this to false but I'm not quite sure I understand the implications.
>
> My reasoning behind assigning this to true was that the FPGA is an external
> device on a bus that needs to be configured by a bus controller. The bus controller
> would be the parent of the fpga DT node and the later would contain properties
> parsed by the bus controller driver.
Which bus controller? MMIO bus does not parse children properties.
Anyway, if that's the case you miss $ref to respective
peripheral-props.yaml matching your bus and then "unevaluatedProperties:
false".
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-30 16:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 22:56 [PATCH 1/3] fpga: xilinx-spi: extract a common driver core Charles Perry
2024-01-29 22:56 ` [PATCH 2/3] dt-bindings: fpga: xlnx,fpga-slave-selectmap: add DT schema Charles Perry
2024-01-30 0:21 ` Rob Herring
2024-01-30 7:52 ` Krzysztof Kozlowski
2024-01-30 7:53 ` Krzysztof Kozlowski
2024-01-30 15:45 ` Charles Perry
2024-01-30 16:05 ` Krzysztof Kozlowski [this message]
2024-01-30 17:05 ` Charles Perry
2024-01-30 17:58 ` Krzysztof Kozlowski
2024-01-30 23:32 ` Charles Perry
2024-01-30 16:09 ` Krzysztof Kozlowski
2024-01-31 11:03 ` Kris Chaplin
2024-02-04 8:30 ` Xu Yilun
2024-02-13 21:54 ` Charles Perry
2024-01-29 22:56 ` [PATCH 3/3] fpga: xilinx-selectmap: add new driver Charles Perry
2024-01-30 7:56 ` Krzysztof Kozlowski
2024-01-31 23:05 ` [PATCH 0/3] " Charles Perry
2024-01-31 23:05 ` [PATCH 1/3] fpga: xilinx-spi: extract a common driver core Charles Perry
2024-02-04 8:22 ` Xu Yilun
2024-02-06 15:39 ` Charles Perry
2024-01-31 23:05 ` [PATCH 2/3] dt-bindings: fpga: xlnx,fpga-slave-selectmap: add DT schema Charles Perry
2024-02-01 8:07 ` Krzysztof Kozlowski
2024-02-01 18:24 ` Charles Perry
2024-02-02 10:49 ` Krzysztof Kozlowski
2024-02-02 19:52 ` Charles Perry
2024-01-31 23:05 ` [PATCH 3/3] fpga: xilinx-selectmap: add new driver Charles Perry
2024-02-04 8:10 ` Xu Yilun
2024-02-06 15:48 ` Charles Perry
2024-02-02 20:16 ` [PATCH 0/3] " Rob Herring
2024-02-02 20:53 ` Charles Perry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32669bc7-90b5-48d9-8845-2e072a477c6e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=avandiver@markem-imaje.com \
--cc=bcody@markem-imaje.com \
--cc=charles.perry@savoirfairelinux.com \
--cc=devicetree@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).