From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
"richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
"sebastian.hesselbarth@gmail.com"
<sebastian.hesselbarth@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Vadym Kochan <vadym.kochan@plvision.eu>
Subject: Re: [PATCH v9 3/3] dt-bindings: mtd: marvell-nand: Convert to YAML DT scheme
Date: Fri, 16 Jun 2023 10:24:14 +0200 [thread overview]
Message-ID: <20230616102414.222dde21@xps-13> (raw)
In-Reply-To: <781c1db2-ecca-901a-4e11-7f7c68cf744d@linaro.org>
Hi Krzysztof,
krzysztof.kozlowski@linaro.org wrote on Fri, 16 Jun 2023 10:15:31 +0200:
> On 15/06/2023 23:06, Chris Packham wrote:
> >>
> >>> +
> >>> +properties:
> >>> + compatible:
> >>> + oneOf:
> >>> + - items:
> >>> + - const: marvell,armada-8k-nand-controller
> >>> + - const: marvell,armada370-nand-controller
> >>> + - enum:
> >>> + - marvell,armada-8k-nand-controller
> >> This is wrong. 8k cannot be both: compatible and not compatible with
> >> 370. It's not someone's cat to be in both states at the same time...
> >
> > The correct state (IMHO, Miquel correct me if I'm wrong) is `compatible
> > = "marvell,armada-8k-nand-controller";` as there are some 8K specific
> > requirements that aren't present on the 370 (specifically the
> > system-controller and the 2nd clock).
>
> Presence of specific requirements does not invalidate compatibility. Two
> devices are compatible if the 8k can bind and work with 370 compatible
> string, even if this means some lower performance or less features (e.g.
> subset of features).
Quoting myself from 2019 (comment in the driver):
"Some SoCs like A7k/A8k need to enable manually the NAND controller,
gated clocks and reset bits to avoid being bootloader dependent."
So can the 8k controller work using a 370 compatible : yes, if the
booloader enabled the NAND controller already, no otherwise. But in
practice it is the same controller.
Given this information I don't know whether it makes sense to qualify
the 8k controller compatible with the 370 compatible or not.
> Now whether they are really compatible or not - I don't know. I expect
> the answer from you (as plural you).
:-)
> > The only reason `compatible =
> > "marvell,armada-8k-nand-controller",
> > "marvell,armada370-nand-controller";` is supported is because that is
> > what is in use in the existing dtses.
>
> Fix the DTS, use here the correct combination and, if it is a deviation
> from old binding, mention this in commit msg.
Fine by me.
> Best regards,
> Krzysztof
>
Thanks,
Miquèl
next prev parent reply other threads:[~2023-06-16 8:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 4:04 [PATCH v9 0/3] dt-bindings: mtd: marvell-nand: Add YAML scheme Chris Packham
2023-06-15 4:04 ` [PATCH v9 1/3] arm64: dts: marvell: cp11x: Fix nand_controller node name according to YAML Chris Packham
2023-06-16 11:55 ` Gregory CLEMENT
2023-06-15 4:04 ` [PATCH v9 2/3] ARM: dts: mvebu: align MTD partition nodes to dtschema Chris Packham
2023-06-16 11:56 ` Gregory CLEMENT
2023-06-15 4:04 ` [PATCH v9 3/3] dt-bindings: mtd: marvell-nand: Convert to YAML DT scheme Chris Packham
2023-06-15 5:25 ` Rob Herring
2023-06-15 7:45 ` Krzysztof Kozlowski
2023-06-15 21:06 ` Chris Packham
2023-06-16 8:15 ` Krzysztof Kozlowski
2023-06-16 8:24 ` Miquel Raynal [this message]
2023-06-16 8:38 ` Krzysztof Kozlowski
2023-06-16 8:44 ` Miquel Raynal
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=20230616102414.222dde21@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=vadym.kochan@plvision.eu \
--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).