From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
linux-kernel@vger.kernel.org, Lubomir Rintel <lkundrak@v3.sk>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-input@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: input: ariel-pwrbutton: use spi-peripheral-props.yaml
Date: Thu, 11 Aug 2022 11:20:13 -0700 [thread overview]
Message-ID: <YvVIXdXEwIq7aKZh@google.com> (raw)
In-Reply-To: <219a875c-f46c-fde9-4370-4168d440e614@linaro.org>
On Thu, Aug 11, 2022 at 09:21:35AM +0300, Krzysztof Kozlowski wrote:
> On 11/08/2022 01:57, Dmitry Torokhov wrote:
> > On Thu, Jul 28, 2022 at 09:19:42AM -0600, Rob Herring wrote:
> >> On Wed, 27 Jul 2022 18:42:30 +0200, Krzysztof Kozlowski wrote:
> >>> Instead of listing directly properties typical for SPI peripherals,
> >>> reference the spi-peripheral-props.yaml schema. This allows using all
> >>> properties typical for SPI-connected devices, even these which device
> >>> bindings author did not tried yet.
> >>>
> >>> Remove the spi-* properties which now come via spi-peripheral-props.yaml
> >>> schema, except for the cases when device schema adds some constraints
> >>> like maximum frequency.
> >>>
> >>> While changing additionalProperties->unevaluatedProperties, put it in
> >>> typical place, just before example DTS.a
> >>>
> >>> The binding references also input.yaml and lists explicitly allowed
> >>> properties, thus here reference only spi-peripheral-props.yaml for
> >>> purpose of documenting the SPI slave device and bringing
> >>> spi-max-frequency type validation.
> >>>
> >>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> >>>
> >>> ---
> >>>
> >>> Technically, this depends on [1] merged to SPI tree, if we want to
> >>> preserve existing behavior of not allowing SPI CPHA and CPOL in each of
> >>> schemas in this patch.
> >
> > Could we merge this through SPI tree as well?
> >
> >>>
> >>> If this patch comes independently via different tree, the SPI CPHA and
> >>> CPOL will be allowed for brief period of time, before [1] is merged.
> >>> This will not have negative impact, just DT schema checks will be
> >>> loosened for that period.
> >>>
> >>> [1] https://lore.kernel.org/all/20220722191539.90641-2-krzysztof.kozlowski@linaro.org/
> >>> ---
> >>> Documentation/devicetree/bindings/input/ariel-pwrbutton.yaml | 1 +
> >>> 1 file changed, 1 insertion(+)
> >>>
> >>
> >> Acked-by: Rob Herring <robh@kernel.org>
> >
> > Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> >
>
> There is no dependency anymore (and actually that time it was not really
> dependency), so you can take it freely for next cycle.
Hm, it turns out I already applied it and even included in pull request
for Linus. But for some reason my "applied" email was not bcc-ed to me
and so I got terribly confused.
--
Dmitry
next prev parent reply other threads:[~2022-08-11 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 16:42 [PATCH] dt-bindings: input: ariel-pwrbutton: use spi-peripheral-props.yaml Krzysztof Kozlowski
2022-07-28 15:19 ` Rob Herring
2022-08-10 22:57 ` Dmitry Torokhov
2022-08-11 6:21 ` Krzysztof Kozlowski
2022-08-11 18:20 ` Dmitry Torokhov [this message]
2022-07-28 20:16 ` Dmitry Torokhov
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=YvVIXdXEwIq7aKZh@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).