From: "Rafał Miłecki" <firstname.lastname@example.org> To: Florian Fainelli <email@example.com> Cc: "Rafał Miłecki" <firstname.lastname@example.org>, "Mark Brown" <email@example.com>, "Rob Herring" <firstname.lastname@example.org>, "Kamal Dasu" <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Re: [PATCH] dt-bindings: spi: brcm,spi-bcm-qspi: convert to the json-schema Date: Fri, 16 Apr 2021 08:21:23 +0200 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On 2021-04-16 02:32, Florian Fainelli wrote: > On 4/15/2021 3:02 PM, Rafał Miłecki wrote: >> From: Rafał Miłecki <email@example.com> >> >> This helps validating DTS files. >> >> Changes that require mentioning: >> 1. reg-names >> "mspi_regs" and "bspi_regs" were renamed to "mspi" and "bspi" as >> that >> is what's used in DTS files and in Linux driver >> 2. interrupt-names >> Names were reordered. "mspi_done" has to go first as it's always >> required. >> 3. spi-rx-bus-width >> Property description was dropped as it's part of the >> spi-controller.yaml >> 4. Examples: >> * flash0@0 was a duplicated node and got dropped >> * regs and interrupts were formatted and reordered to match yaml >> * <0x1c> was replaced with <&gic> >> >> This rewritten binding validates cleanly using the >> "dt_binding_check". >> Some Linux stored DTS files will require reordering regs and >> interrupts >> to make dtbs_check happy. >> >> Signed-off-by: Rafał Miłecki <firstname.lastname@example.org> > > Thanks a lot for doing that, do you mind adding Kamal as a maintainer > for that binding if you have to send a v2? I wasn't sure if I can just add someone else like that. He's already maintainer according to the MAINTAINERS though, so I guess I'm safe to do that. Sending V2.
next prev parent reply index Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-15 22:02 Rafał Miłecki 2021-04-16 0:32 ` Florian Fainelli 2021-04-16 6:21 ` Rafał Miłecki [this message] 2021-04-16 6:23 ` [PATCH V2] " Rafał Miłecki 2021-04-16 19:27 ` Rob Herring 2021-04-16 19:47 ` [PATCH V3] " Rafał Miłecki 2021-04-20 16:21 ` Rob Herring 2021-04-20 18:35 ` Mark Brown
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
Linux-SPI Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-spi/0 linux-spi/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-spi linux-spi/ https://lore.kernel.org/linux-spi \ email@example.com public-inbox-index linux-spi Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-spi AGPL code for this site: git clone https://public-inbox.org/public-inbox.git