From: "Gabriel L. Somlo" <gsomlo@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Karol Gugala <kgugala@antmicro.com>,
mdudek@internships.antmicro.com,
Randy Dunlap <rdunlap@infradead.org>,
Paul Mackerras <paulus@ozlabs.org>, Joel Stanley <joel@jms.id.au>,
david.abdurachmanov@sifive.com,
Florent Kermarrec <florent@enjoy-digital.fr>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Stafford Horne <shorne@gmail.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Kamil Rakoczy <krakoczy@antmicro.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Mateusz Holenko <mholenko@antmicro.com>
Subject: Re: [PATCH v3 2/3] dt-bindings: mmc: Add bindings for LiteSDCard
Date: Thu, 9 Dec 2021 13:25:01 -0500 [thread overview]
Message-ID: <YbJJ/UqCeFJa5HGF@errol.ini.cmu.edu> (raw)
In-Reply-To: <CAMuHMdVJZdzRMedn9L_Jb=0MYB_Bxs90v+iH7UaDBzup-qzp8A@mail.gmail.com>
On Thu, Dec 09, 2021 at 09:37:27AM +0100, Geert Uytterhoeven wrote:
> Hi Gabriel,
>
> On Thu, Dec 9, 2021 at 2:08 AM Gabriel L. Somlo <gsomlo@gmail.com> wrote:
> > ... which took care of the bulk of the error messages reported. However,
> > I'm still getting the one below, whether or not I leave the `maxItems 1`
> > line there under `clocks:`
> >
> > $ make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- dt_binding_check
> > LINT Documentation/devicetree/bindings
> > CHKDT Documentation/devicetree/bindings/processed-schema-examples.json
> > /home/somlo/linux/Documentation/devicetree/bindings/clock/litex,clock.yaml: properties:clock-output-names: {'description': 'List of strings of clock output signal names indexed by the first cell in the clock specifier.', 'minItems': 1, 'maxItems': 7, 'items': [{'const': 'CLKOUT0'}, {'const': 'CLKOUT1'}, {'const': 'CLKOUT2'}, {'const': 'CLKOUT3'}, {'const': 'CLKOUT4'}, {'const': 'CLKOUT5'}, {'const': 'CLKOUT6'}]} should not be valid under {'required': ['maxItems']}
> > hint: "maxItems" is not needed with an "items" list
> > from schema $id: http://devicetree.org/meta-schemas/items.yaml#
> > SCHEMA Documentation/devicetree/bindings/processed-schema-examples.json
> > /home/somlo/linux/Documentation/devicetree/bindings/clock/litex,clock.yaml: ignoring, error in schema: properties: clock-output-names
> > warning: no schema found in file: ./Documentation/devicetree/bindings/clock/litex,clock.yaml
> > DTEX Documentation/devicetree/bindings/mmc/litex,mmc.example.dts
> > DTEX Documentation/devicetree/bindings/media/renesas,imr.example.dts
> > ...
>
> --- a/Documentation/devicetree/bindings/clock/litex,clock.yaml
> +++ b/Documentation/devicetree/bindings/clock/litex,clock.yaml
> @@ -45,7 +45,6 @@ properties:
> List of strings of clock output signal names indexed
> by the first cell in the clock specifier.
> minItems: 1
> - maxItems: 7
> items:
> - const: CLKOUT0
> - const: CLKOUT1
>
> I have that in my local tree, but hadn't sent it to you yet, because
> litex,clock definitely need more work.
>
> > It appears as though `make dt_binding_check` is trying to read from
> > `Documentation/devicetree/bindings/clock/litex,clock.yaml`, which
> > does not exist. The clock reference I'm talking about could be *any*
>
> Oh, it does exist in your tree ;-)
> To check the examples, it has to apply all other binding files that
> might apply, hence some checks are always run.
>
> You can avoid some (but not all) such checks by adding
>
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/path/to/binding.yaml
>
> > clock elsewhere in the dts!
> >
> > This wasn't part of the originally reported errors, not sure why I'm
> > seeing it now. Also, not sure what (if anything) I still need to do
> > about it, any advice much appreciated!
>
> Of course, as Rob doesn't have that file in his tree.
Oh, I'm working on the `litex-rebase` branch, which does have the
litex,clock file. Running the check on the Linus master with litex_mmc
v4 on top now passes the check without any errors or warnings. I'll
incorporate the fixes pointed out by Rob when I publish v4.
Sorry for the misunderstanding, thanks Geert for pointing out the
source of my confusion -- I think all's well now on the dt-bindings
front w.r.t. litex_mmc... :)
Cheers,
--Gabriel
next prev parent reply other threads:[~2021-12-09 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 13:20 [PATCH v3 0/3] mmc: Add LiteSDCard mmc driver Gabriel Somlo
2021-12-08 13:20 ` [PATCH v3 1/3] MAINTAINERS: co-maintain LiteX platform Gabriel Somlo
2021-12-08 13:20 ` [PATCH v3 2/3] dt-bindings: mmc: Add bindings for LiteSDCard Gabriel Somlo
2021-12-08 23:06 ` Rob Herring
2021-12-09 1:08 ` Gabriel L. Somlo
2021-12-09 8:37 ` Geert Uytterhoeven
2021-12-09 18:25 ` Gabriel L. Somlo [this message]
2021-12-08 13:20 ` [PATCH v3 3/3] mmc: Add driver for LiteX's LiteSDCard interface Gabriel Somlo
2021-12-25 16:39 ` Andy Shevchenko
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=YbJJ/UqCeFJa5HGF@errol.ini.cmu.edu \
--to=gsomlo@gmail.com \
--cc=david.abdurachmanov@sifive.com \
--cc=devicetree@vger.kernel.org \
--cc=florent@enjoy-digital.fr \
--cc=geert@linux-m68k.org \
--cc=joel@jms.id.au \
--cc=kgugala@antmicro.com \
--cc=krakoczy@antmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mdudek@internships.antmicro.com \
--cc=mholenko@antmicro.com \
--cc=paulus@ozlabs.org \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=shorne@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®