From: Krzysztof Kozlowski <krzk@kernel.org>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v5 2/2] dt-bindings: mtd: davinci: convert to yaml
Date: Sat, 26 Oct 2024 20:16:28 +0200 [thread overview]
Message-ID: <2b89379a-4d21-450e-b273-b6986dcf5b7a@kernel.org> (raw)
In-Reply-To: <ZxImhhPhOWuYqSfK@gmail.com>
On 18/10/2024 11:12, Marcus Folkesson wrote:
>>> ```
>>>
>>>
>>> How do I set #address-cells in example-0 to 2?
>>> I guess that is the problem.
>>
>>
>>
>> You just set it... There are dozens/hundreds of schemas doing it, what
>> is exactly a problem here?
>
> I think I will solve the problem by including the parent nodes.
Just like everyone else or some other way?
> What do you think about this?
>
> examples:
> - |
> aemif: aemif@68000000 {
> compatible = "ti,da850-aemif";
> #address-cells = <2>;
> #size-cells = <1>;
>
> reg = <0x68000000 0x00008000>;
> ranges = <0 0 0x60000000 0x08000000
> 1 0 0x68000000 0x00008000>;
> clocks = <&psc0 3>;
> clock-names = "aemif";
> clock-ranges;
That's some other way, so no, drop unrelated properties. Look how all
other bindings are doing it - you need some wrapper node.
Best regards,
Krzysztof
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2024-10-26 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 7:02 [PATCH v5 0/2] Add support for "on-die" ECC on Davinci Marcus Folkesson
2024-10-08 7:02 ` [PATCH v5 1/2] mtd: nand: davinci: add support for on-die ECC engine type Marcus Folkesson
2024-10-08 7:02 ` [PATCH v5 2/2] dt-bindings: mtd: davinci: convert to yaml Marcus Folkesson
2024-10-08 8:10 ` Miquel Raynal
2024-10-08 13:28 ` Krzysztof Kozlowski
2024-10-14 12:04 ` Marcus Folkesson
2024-10-14 18:08 ` Krzysztof Kozlowski
2024-10-18 9:12 ` Marcus Folkesson
2024-10-26 18:16 ` Krzysztof Kozlowski [this message]
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=2b89379a-4d21-450e-b273-b6986dcf5b7a@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marcus.folkesson@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=vigneshr@ti.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).