From: Tomer Maimon <tmaimon77@gmail.com> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Cc: Mark Brown <broonie@kernel.org>, Avi Fishman <avifishman70@gmail.com>, Tali Perry <tali.perry1@gmail.com>, Joel Stanley <joel@jms.id.au>, Patrick Venture <venture@google.com>, Nancy Yuen <yuenn@google.com>, Benjamin Fair <benjaminfair@google.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, OpenBMC Maillist <openbmc@lists.ozlabs.org>, linux-spi@vger.kernel.org, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, devicetree <devicetree@vger.kernel.org> Subject: Re: [PATCH v2 2/2] spi: npcm-pspi: Add NPCM845 peripheral SPI support Date: Tue, 26 Jul 2022 22:32:56 +0300 [thread overview] Message-ID: <CAP6Zq1iHCL9Krjw-wYKrG1K_yzwj-_qNROYxhogvkDjk+gCL-g@mail.gmail.com> (raw) In-Reply-To: <20869b88-41f3-9e9c-347e-17c3d01baa5d@linaro.org> Hi Krzysztof, Thanks for your explanation. On Tue, 26 Jul 2022 at 12:47, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > > On 24/07/2022 10:44, Tomer Maimon wrote: > > Hi Mark and Krzysztof, > > > > Thanks for your reply, > > > > On Fri, 22 Jul 2022 at 21:57, Mark Brown <broonie@kernel.org> wrote: > >> > >> On Fri, Jul 22, 2022 at 08:47:24PM +0200, Krzysztof Kozlowski wrote: > >>> On 22/07/2022 20:43, Mark Brown wrote: > >> > >>>> ...with a fallback list required by the bindings so the driver actually > >>>> binds. Note that bindings are currently not in YAML format so there'd > >>>> be even less enforcement of that than normal, and as they're currently > >>>> written the bindings don't require fallback. > >> > >>> Yes, the bindings document should be rephrased but we were living like > >>> that for few years. :) > >> > >> The binding document as it stands only has one compatible, there's no > >> existing problem with it other than the YAML conversion. If we're > >> adding something new that requires a fallback we should be explicit > >> about that rather than have something that's actively misleading where > >> previously things were clear. I don't mind if we add the compatible to > >> the driver or document the requirement for the fallback but we should do > >> one of the two. > > > > is V2 good enough? adding the compatible to the driver and the document? > > Or should we use fallback? > > If fallback is choosen, can you explain how I should do it? > > I propose to use fallback. The preferred way is to convert it to DT > schema and then add new device support (so two commits). Other > acceptable way is to rephrase the TXT so it clearly states desired > compatibles - one for old device, two for new devices. There are plenty > of examples in current sources. Appreciate if you could clarify. in case we use DT-schema, we dont describe the fallback like we doing in txt document? I mean that in the yaml file we should describe the NPCM PSPI compatible property as follow: compatible: enum: - nuvoton,npcm750-pspi - nuvoton,npcm845-pspi If yes, how should the user know that he needs to use fallback incase is using nuvoton,npcm845-pspi? only from the device tree? > > > Best regards, > Krzysztof Best regards, Tomer
WARNING: multiple messages have this Message-ID (diff)
From: Tomer Maimon <tmaimon77@gmail.com> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Cc: devicetree <devicetree@vger.kernel.org>, Benjamin Fair <benjaminfair@google.com>, Avi Fishman <avifishman70@gmail.com>, Patrick Venture <venture@google.com>, OpenBMC Maillist <openbmc@lists.ozlabs.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>, Tali Perry <tali.perry1@gmail.com>, Mark Brown <broonie@kernel.org>, Joel Stanley <joel@jms.id.au>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, linux-spi@vger.kernel.org Subject: Re: [PATCH v2 2/2] spi: npcm-pspi: Add NPCM845 peripheral SPI support Date: Tue, 26 Jul 2022 22:32:56 +0300 [thread overview] Message-ID: <CAP6Zq1iHCL9Krjw-wYKrG1K_yzwj-_qNROYxhogvkDjk+gCL-g@mail.gmail.com> (raw) In-Reply-To: <20869b88-41f3-9e9c-347e-17c3d01baa5d@linaro.org> Hi Krzysztof, Thanks for your explanation. On Tue, 26 Jul 2022 at 12:47, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > > On 24/07/2022 10:44, Tomer Maimon wrote: > > Hi Mark and Krzysztof, > > > > Thanks for your reply, > > > > On Fri, 22 Jul 2022 at 21:57, Mark Brown <broonie@kernel.org> wrote: > >> > >> On Fri, Jul 22, 2022 at 08:47:24PM +0200, Krzysztof Kozlowski wrote: > >>> On 22/07/2022 20:43, Mark Brown wrote: > >> > >>>> ...with a fallback list required by the bindings so the driver actually > >>>> binds. Note that bindings are currently not in YAML format so there'd > >>>> be even less enforcement of that than normal, and as they're currently > >>>> written the bindings don't require fallback. > >> > >>> Yes, the bindings document should be rephrased but we were living like > >>> that for few years. :) > >> > >> The binding document as it stands only has one compatible, there's no > >> existing problem with it other than the YAML conversion. If we're > >> adding something new that requires a fallback we should be explicit > >> about that rather than have something that's actively misleading where > >> previously things were clear. I don't mind if we add the compatible to > >> the driver or document the requirement for the fallback but we should do > >> one of the two. > > > > is V2 good enough? adding the compatible to the driver and the document? > > Or should we use fallback? > > If fallback is choosen, can you explain how I should do it? > > I propose to use fallback. The preferred way is to convert it to DT > schema and then add new device support (so two commits). Other > acceptable way is to rephrase the TXT so it clearly states desired > compatibles - one for old device, two for new devices. There are plenty > of examples in current sources. Appreciate if you could clarify. in case we use DT-schema, we dont describe the fallback like we doing in txt document? I mean that in the yaml file we should describe the NPCM PSPI compatible property as follow: compatible: enum: - nuvoton,npcm750-pspi - nuvoton,npcm845-pspi If yes, how should the user know that he needs to use fallback incase is using nuvoton,npcm845-pspi? only from the device tree? > > > Best regards, > Krzysztof Best regards, Tomer
next prev parent reply other threads:[~2022-07-26 19:33 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-22 11:41 [PATCH v2 0/2] spi: npcm-pspi: add Arbel NPCM8XX support Tomer Maimon 2022-07-22 11:41 ` Tomer Maimon 2022-07-22 11:41 ` [PATCH v2 1/2] dt-binding: spi: npcm-pspi: Add npcm845 compatible Tomer Maimon 2022-07-22 11:41 ` Tomer Maimon 2022-07-25 22:56 ` Rob Herring 2022-07-25 22:56 ` Rob Herring 2022-07-26 9:30 ` Tomer Maimon 2022-07-26 9:30 ` Tomer Maimon 2022-07-26 9:57 ` Krzysztof Kozlowski 2022-07-22 11:41 ` [PATCH v2 2/2] spi: npcm-pspi: Add NPCM845 peripheral SPI support Tomer Maimon 2022-07-22 11:41 ` Tomer Maimon 2022-07-22 18:31 ` Krzysztof Kozlowski 2022-07-22 18:43 ` Mark Brown 2022-07-22 18:43 ` Mark Brown 2022-07-22 18:47 ` Krzysztof Kozlowski 2022-07-22 18:57 ` Mark Brown 2022-07-22 18:57 ` Mark Brown 2022-07-24 8:44 ` Tomer Maimon 2022-07-24 8:44 ` Tomer Maimon 2022-07-26 9:47 ` Krzysztof Kozlowski 2022-07-26 19:32 ` Tomer Maimon [this message] 2022-07-26 19:32 ` Tomer Maimon 2022-07-27 6:51 ` Krzysztof Kozlowski 2022-08-15 15:44 ` [PATCH v2 0/2] spi: npcm-pspi: add Arbel NPCM8XX support Mark Brown 2022-08-15 15:44 ` 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 \ --in-reply-to=CAP6Zq1iHCL9Krjw-wYKrG1K_yzwj-_qNROYxhogvkDjk+gCL-g@mail.gmail.com \ --to=tmaimon77@gmail.com \ --cc=avifishman70@gmail.com \ --cc=benjaminfair@google.com \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=joel@jms.id.au \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=krzysztof.kozlowski@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-spi@vger.kernel.org \ --cc=openbmc@lists.ozlabs.org \ --cc=robh+dt@kernel.org \ --cc=tali.perry1@gmail.com \ --cc=venture@google.com \ --cc=yuenn@google.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: linkBe 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.