All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	"andrew@lunn.ch" <andrew@lunn.ch>,
	"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"sebastian.hesselbarth@gmail.com"
	<sebastian.hesselbarth@gmail.com>,
	"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"huziji@marvell.com" <huziji@marvell.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] dt-bindings: mmc: xenon: Convert to JSON schema
Date: Wed, 30 Mar 2022 09:40:27 -0500	[thread overview]
Message-ID: <YkRr22lQHKCZa5A2@robh.at.kernel.org> (raw)
In-Reply-To: <6e118704-3c63-929e-ebf0-9a78fbed5daa@alliedtelesis.co.nz>

On Tue, Mar 29, 2022 at 07:50:59PM +0000, Chris Packham wrote:
> 
> On 30/03/22 02:14, Krzysztof Kozlowski wrote:
> > On 29/03/2022 13:50, Rob Herring wrote:
> >> On Tue, 29 Mar 2022 13:02:31 +1300, Chris Packham wrote:
> >>> Convert the marvell,xenon-sdhci binding to JSON schema. Currently the
> >>> in-tree dts files don't validate because they use sdhci@ instead of mmc@
> >>> as required by the generic mmc-controller schema.
> >>>
> >>> The compatible "marvell,sdhci-xenon" was not documented in the old
> >>> binding but it accompanies the of "marvell,armada-3700-sdhci" in the
> >>> armada-37xx SoC dtsi so this combination is added to the new binding
> >>> document.
> >>>
> >>> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> >>> Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
> >>> ---
> >>>
> >>> Notes:
> >>>      Changes in v4:
> >>>      - Add review from Krzysztof
> >>>      - Squash in addition of marvell,sdhci-xenon with an explanation in the
> >>>        commit message
> >>>      Changes in v3:
> >>>      - Don't accept ap807 without ap806
> >>>      - Add ref: string for pad-type
> >>>      Changes in v2:
> >>>      - Update MAINTAINERS entry
> >>>      - Incorporate feedback from Krzysztof
> >>>
> >>>   .../bindings/mmc/marvell,xenon-sdhci.txt      | 173 -----------
> >>>   .../bindings/mmc/marvell,xenon-sdhci.yaml     | 275 ++++++++++++++++++
> >>>   MAINTAINERS                                   |   2 +-
> >>>   3 files changed, 276 insertions(+), 174 deletions(-)
> >>>   delete mode 100644 Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.txt
> >>>   create mode 100644 Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.yaml
> >>>
> >> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> >> on your patch (DT_CHECKER_FLAGS is new in v5.13):
> >>
> >> yamllint warnings/errors:
> >>
> >> dtschema/dtc warnings/errors:
> >> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.example.dt.yaml: mmc@aa0000: compatible: 'oneOf' conditional failed, one must be fixed:
> >> 	['marvell,armada-3700-sdhci'] is too short
> >> 	'marvell,armada-3700-sdhci' is not one of ['marvell,armada-cp110-sdhci', 'marvell,armada-ap806-sdhci']
> >> 	'marvell,armada-ap807-sdhci' was expected
> >> 	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.yaml
> >> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.example.dt.yaml: mmc@ab0000: compatible: 'oneOf' conditional failed, one must be fixed:
> >> 	['marvell,armada-3700-sdhci'] is too short
> >> 	'marvell,armada-3700-sdhci' is not one of ['marvell,armada-cp110-sdhci', 'marvell,armada-ap806-sdhci']
> >> 	'marvell,armada-ap807-sdhci' was expected
> >> 	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.yaml
> >>
> >> doc reference errors (make refcheckdocs):
> > Chris, your own dt binding does not pass it's check (example)...
> >
> > After updating the compatibles, you need to check the example. The
> > examples are anyway duplicating common stuff, so half of them could be
> > removed.
> 
> Yeah silly me. I started taking short cuts to run dt_binding_check 
> dtbs_check as one command but then the dt_bindings_check output scrolled 
> off the top of my terminal.
> 
> As for the examples themselves I want to leave what's there as a fairly 
> direct translation of the old binding. If we consider them unnecessary 
> removing them can be done as a follow-up.

The examples cannot have warnings/errors.

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	"andrew@lunn.ch" <andrew@lunn.ch>,
	"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"sebastian.hesselbarth@gmail.com"
	<sebastian.hesselbarth@gmail.com>,
	"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"huziji@marvell.com" <huziji@marvell.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] dt-bindings: mmc: xenon: Convert to JSON schema
Date: Wed, 30 Mar 2022 09:40:27 -0500	[thread overview]
Message-ID: <YkRr22lQHKCZa5A2@robh.at.kernel.org> (raw)
In-Reply-To: <6e118704-3c63-929e-ebf0-9a78fbed5daa@alliedtelesis.co.nz>

On Tue, Mar 29, 2022 at 07:50:59PM +0000, Chris Packham wrote:
> 
> On 30/03/22 02:14, Krzysztof Kozlowski wrote:
> > On 29/03/2022 13:50, Rob Herring wrote:
> >> On Tue, 29 Mar 2022 13:02:31 +1300, Chris Packham wrote:
> >>> Convert the marvell,xenon-sdhci binding to JSON schema. Currently the
> >>> in-tree dts files don't validate because they use sdhci@ instead of mmc@
> >>> as required by the generic mmc-controller schema.
> >>>
> >>> The compatible "marvell,sdhci-xenon" was not documented in the old
> >>> binding but it accompanies the of "marvell,armada-3700-sdhci" in the
> >>> armada-37xx SoC dtsi so this combination is added to the new binding
> >>> document.
> >>>
> >>> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> >>> Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
> >>> ---
> >>>
> >>> Notes:
> >>>      Changes in v4:
> >>>      - Add review from Krzysztof
> >>>      - Squash in addition of marvell,sdhci-xenon with an explanation in the
> >>>        commit message
> >>>      Changes in v3:
> >>>      - Don't accept ap807 without ap806
> >>>      - Add ref: string for pad-type
> >>>      Changes in v2:
> >>>      - Update MAINTAINERS entry
> >>>      - Incorporate feedback from Krzysztof
> >>>
> >>>   .../bindings/mmc/marvell,xenon-sdhci.txt      | 173 -----------
> >>>   .../bindings/mmc/marvell,xenon-sdhci.yaml     | 275 ++++++++++++++++++
> >>>   MAINTAINERS                                   |   2 +-
> >>>   3 files changed, 276 insertions(+), 174 deletions(-)
> >>>   delete mode 100644 Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.txt
> >>>   create mode 100644 Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.yaml
> >>>
> >> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> >> on your patch (DT_CHECKER_FLAGS is new in v5.13):
> >>
> >> yamllint warnings/errors:
> >>
> >> dtschema/dtc warnings/errors:
> >> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.example.dt.yaml: mmc@aa0000: compatible: 'oneOf' conditional failed, one must be fixed:
> >> 	['marvell,armada-3700-sdhci'] is too short
> >> 	'marvell,armada-3700-sdhci' is not one of ['marvell,armada-cp110-sdhci', 'marvell,armada-ap806-sdhci']
> >> 	'marvell,armada-ap807-sdhci' was expected
> >> 	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.yaml
> >> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.example.dt.yaml: mmc@ab0000: compatible: 'oneOf' conditional failed, one must be fixed:
> >> 	['marvell,armada-3700-sdhci'] is too short
> >> 	'marvell,armada-3700-sdhci' is not one of ['marvell,armada-cp110-sdhci', 'marvell,armada-ap806-sdhci']
> >> 	'marvell,armada-ap807-sdhci' was expected
> >> 	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.yaml
> >>
> >> doc reference errors (make refcheckdocs):
> > Chris, your own dt binding does not pass it's check (example)...
> >
> > After updating the compatibles, you need to check the example. The
> > examples are anyway duplicating common stuff, so half of them could be
> > removed.
> 
> Yeah silly me. I started taking short cuts to run dt_binding_check 
> dtbs_check as one command but then the dt_bindings_check output scrolled 
> off the top of my terminal.
> 
> As for the examples themselves I want to leave what's there as a fairly 
> direct translation of the old binding. If we consider them unnecessary 
> removing them can be done as a follow-up.

The examples cannot have warnings/errors.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-03-30 14:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29  0:02 [PATCH v4 0/2] mmc: xenon: Convert to JSON schema Chris Packham
2022-03-29  0:02 ` Chris Packham
2022-03-29  0:02 ` [PATCH v4 1/2] arm64: dts: marvell: Update sdhci node names to match schema Chris Packham
2022-03-29  0:02   ` Chris Packham
2022-03-29  0:02 ` [PATCH v4 2/2] dt-bindings: mmc: xenon: Convert to JSON schema Chris Packham
2022-03-29  0:02   ` Chris Packham
2022-03-29 11:50   ` Rob Herring
2022-03-29 11:50     ` Rob Herring
2022-03-29 13:14     ` Krzysztof Kozlowski
2022-03-29 13:14       ` Krzysztof Kozlowski
2022-03-29 19:50       ` Chris Packham
2022-03-29 19:50         ` Chris Packham
2022-03-30 14:40         ` Rob Herring [this message]
2022-03-30 14:40           ` Rob Herring
2022-03-31 20:09           ` Chris Packham
2022-03-31 20:09             ` Chris Packham

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=YkRr22lQHKCZa5A2@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=huziji@marvell.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=ulf.hansson@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.