Message ID | 20230127093217.60818-1-krzysztof.kozlowski@linaro.org |
---|---|
Headers | show |
Series | dt-bindings: serial/mtd/mc/ata: use MC peripheral props | expand |
On Fri, Jan 27, 2023 at 10:32 AM Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > The re-usable serial.yaml schema matches every property with ".*" > pattern, thus any other schema referencing it will not report unknown > (unevaluated) properties. This hides several wrong properties. It is > a limitation of dtschema, thus provide a simple workaround: expect > children to be only of few names matching upstream usage (Bluetooth, > GNSS, GPS and MCU). > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Fair enough, Acked-by: Linus Walleij <linus.walleij@linaro.org> However I think V.35 WAN devices (high speed serial network links) should actually be using this? They are just some fancy serial port after all. Cf Documentation/devicetree/bindings/net/intel,ixp4xx-hss.yaml No big deal I guess since they are mostly an anarchronism and not on the table right now. Yours, Linus Walleij
On Fri, Jan 27, 2023 at 10:32:14AM +0100, Krzysztof Kozlowski wrote: > Hi, > > Dependencies > ============ > I think entire patchset should go via one tree (Rob's). Patch #2 depends on > patch #1. Patch #3 could go separate tree as long as others are in the > linux-next. However for simplicity let's push everything through Rob's DT > tree? No objection from me: Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>